[Resolved] Performance issues on multisite with Toolset Blocks

[Author]

Posts

[nicolaT-2]

Hi, we're currently facing some performance issues on a multisite project using Toolset Blocks (the multisite ahs two websites: hidden link and hidden link). Our hosting provider, Flywheel, has identified a significant number of slow requests generated by Toolset Blocks, which are leading to PHP worker exhaustion on the server. These requests appear to be contributing to the overall performance issues we are experiencing.

Could you please advise if there are any optimizations or specific settings we should adjust to reduce the load caused by Toolset Blocks and improve the site's overall performance? Additionally, do you have any recommendations for us or for our hosting provider to help configure the environment in the most optimal way? We need to resolve this issue as soon as possible.

Thank you for your assistance, and we look forward to your guidance.

Best regards,
Nicola

[Minesh]

Hello. Thank you for contacting the Toolset support.

In general, performance of your site depends on what size of images you load and how you are loading those. Also, it depends also on your server configuration (memory, cashing, server processing capacity, internet speed) as well as number of other factors such as how complex your data structure is like how much content you have with your post types, taxonomies and custom fields and post-relationship.

- Please make sure to have enough memory for your WP Site.
- Please make sure all Plugins and theme and WordPress is updated to latest version.

Please consult your hosting provider for optimal settings of WordPress installs and these requirements:
- https://toolset.com/toolset-requirements/

To check if there are any possible errors or conflict:

Edit your wp-config.php file on the server and look for define(‘WP_DEBUG’, false);. Change it to:

define('WP_DEBUG', true);

Then add these lines, just before it says 'stop editing here':

ini_set('log_errors',TRUE);
ini_set('error_reporting', E_ALL);
ini_set('error_log', dirname(__FILE__) . '/error_log.txt');

Now attempt to reload the member search page that has been failing. If any server-side errors are generated, this will create an error_log.txt file in your site's root directory (you may need to refresh if you're using FTP). Please send me its contents. Once that is done, you can revert the updates you made to wp-config.php.

More info:
- https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/

Please make sure to use cache or cache plugins where applicable:

On large websites it would be best to employ the use of caching but your view shouldn't load any slower:
- https://toolset.com/documentation/user-guides/views/front-page-filters/how-to-use-views-parametric-search-on-large-sites/

Please check how to use optimization/cache plugins with Toolset:
- https://toolset.com/faq/how-to-use-optimization-plugins-with-toolset/

You should check with any optimization plugin. Please check the following article:
- hidden link

Please check the following related tickets where few tips and mentioned if that might help you:
- https://toolset.com/forums/topic/very-slow-performance-slow-filtering/#post-2175165
- https://toolset.com/forums/topic/very-slow-performance/#post-2126099

[nicolaT-2]

Hi Minesh, thank you for your suggestions.

Currently, the memory allocated is set to 256MB, which should be sufficient for this project. We’ve also enabled WP_DEBUG, but no significant errors have been logged so far. We’re still investigating why no errors are showing and whether there might be an issue with how WP_DEBUG is capturing the logs.

Additionally, I wanted to share what our hosting provider, Flywheel, has mentioned regarding the performance issues. Here’s their reply:

--- START OF FLYWHEEL RESPONSE ---

In regards to the Toolset Blocks plugin, we seem to be seeing the same recurring slow log mentioned below (see attached file slow-log.jpg)

Slow log events are PHP processes that take more than 5 seconds to process. This is significant because PHP processes typically happen almost instantly, so 5 seconds is substantial. We read them from the bottom (where the process starts) to the top (where the process stalled).

We are seeing this logged on nearly every uncached request to diagnosticariviera.it. I’d recommend reaching out to the plugin developer to see if they are aware of this and have a possible solution - based on the above it seems to be an interaction between Avada and the plugin.

--- END OF FLYWHEEL RESPONSE ---

According to Flywheel, almost every uncached request triggers a noticeable delay, and they believe this could be due to an interaction between Toolset Blocks and the Avada theme.

Do you have any insights or recommendations regarding potential compatibility issues between Toolset Blocks and Avada that we should explore?

We are using the latest versions of WordPress, all plugins, and the theme. Any further guidance you can provide on optimizing Toolset Blocks to reduce the load or improve performance in this context would be greatly appreciated.

Thanks again for your help.

Best regards,
Nicola

[Minesh]

As you are using Toolset blocks, it also depends on how many blocks you added where the page is slow. Obviously displaying two blocks will take less time compare to displaying twenty blocks.

I already shared all the suggestion but here is a related ticket again that you may follow:
- https://toolset.com/forums/topic/optimizing-page-load-speed/#post-2208715

You may also check and try to dequeue the unwanted CSS and JS files that might be useful to you as well to boost performance a bit.