Skip Navigation

[Resolved] Speeding up website with lot of views per page

This support ticket is created 6 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Our next available supporter will start replying to tickets in about 2.32 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 9 replies, has 2 voices.

Last updated by martinH-10 6 years ago.

Assisted by: Christian Cox.

Author
Posts
#1136753
scripting.png

Hello, my website is so slow with toolset. I am using PHP7, PHP memory 256MB, Astra theme.

All website I made with this combination were fast, also with woocommerce. This one is slow as hell. And it shows that it is loading 1,6MB of Scripts?!..

I am using only some BIG must have plugins:
Relevansii
Toolset plugins
W3TC
WPML
The SEO Framework
QuadMenu

But I am using lot of views, because one of my post type is for call to actions, which I use at pages.

Can you help me, make the site faster?

#1136981
Screen Shot 2018-10-30 at 2.55.36 PM.png

Hi, are you talking about this page?
hidden link

With cache disabled, I can see that the largest script resource is base.js, a JavaScript file loaded by the YouTube players. Next is from embed.tawk.to, and the following one is a smartchat script. See the attached screenshot. Out of the top 15 script resources by size, only 1 is a Toolset file, so I can't help lower the total size of scripts in any significant way.

Here's a performance test we can review:
hidden link

Runs 5 and 9 show that the time to first byte was 10 - 12 seconds, but other runs show time to first byte lower than 1 second. So I'm curious why the performance is so different. Is it possible to turn off caching temporarily to run some tests? If so, please install the Query Monitor plugin and temporarily disable caching. Then reload the page and watch Query Monitor results to see if any warnings appear. Inspect the queries. If any single Toolset query takes longer than 5ms, we should investigate that in more detail. I can help if you're not familiar with Query Monitor.

#1137545
_slow.png
_PHP.png

Looks like the slowest thing is WPML,. right?

#1137753

Yes, it looks like one WPML query was flagged. Can you click the "Queries by caller" tab and sort by duration? I'd like to see if any Toolset queries were slow but not flagged.

#1140373
second.png
by caller.png

Of course, here it is

#1140585

Okay thank you. I see a few Toolset queries running longer than 0.5ms. I can ask my 2nd tier team to take a closer look at those individual queries, and see if there's anything we can do to speed those up. I'll need to create a clone of your site so I can run tests locally. If that's okay with you, please provide login credentials in the private reply fields here.

#1142327

Thanks, I was able to install the backup locally and replicate some slow queries. I'll forward this information to my 2nd tier support team for additional investigation, and let you know if they are able to find any ways to optimize the Toolset query performance.

#1142512

Thanks

#1143069

Okay after discussion with the team, it turns out I was incorrect about the query speed standards. I was under the impression the standard is 0.0005 seconds, or 0.5 milliseconds. This is not correct. The standard is 0.05 seconds, or 50 milliseconds. With that in mind, my 2nd tier support team has informed me that none of these Toolset queries seem to be performing slower than the acceptable range. WPML may have different standards for their queries, the support forum at WPML.org would be best qualified to answer that.

#1144885

OK, I will contact WPML support then,