|
simonmarek
|
April 6, 2017 at 9:39 pm
Hello,
Wondering if you can help analyse a problem with event page load times.
There is a long (6-8 seconds) delay every time an event page is loaded. This seems consistent across all our event pages.
It seems to come immediately before the ticket selector loads.
I have run some tests and can see that browser CPU and memory is staying low, and that there are no particularly large files being loaded.
Let me know if you have any ideas.
Kind regards,
Simon
|
|
simonmarek
|
April 6, 2017 at 9:40 pm
Hello,
Wondering if you can help analyse a problem with event page load times.
There is a long (6-8 seconds) delay every time an event page is loaded. This seems consistent across all our event pages.
It seems to come immediately before the ticket selector loads:
https://www.aogp.com.au/events/case-based-discussion-study-group/
I have run some tests and can see that browser CPU and memory is staying low, and that there are no particularly large files being loaded.
Let me know if you have any ideas.
Kind regards,
Simon
|
|
Josh
|
April 6, 2017 at 10:15 pm
Hi Simon,
You might try removing the part of the page that has the “Related Events”. That may be an expensive query, and it’s the whole right side column that it’s part of where there’s the delay.
Also, anything that you’re hiding with CSS is requiring PHP to process and output html and JavaScript. So if you look through the page source you’ll see things like social share buttons that use JavaScript, that are being hid with CSS. Instead of hiding unwanted things from the display, it’s best to remove them and the page will load faster. Every little bit will help.
Finally, there’s some heavy JavaScript being loaded, which is a separate http request for each file, so those would be best concatenated and minified. There are WP plugins that can be used like Better WP minify, which compress and condense those down to one file.
|
|
simonmarek
|
April 6, 2017 at 10:33 pm
Josh, you are a wizard! Thank you. The related events was indeed the culprit.
I will follow up your other suggestions as well.
|
