Updating site to get rid of WooCommerce style errors made the site extremly slow

[stefaneklund]

Hi

Regarding the web site: https://natrud.no

I noticed when using Query Monitor that it mentioned two missing WooCommerce files:
woocommerce-layout
and
woocommerce-general

I updated Theme X from 8.3.2 ( I believe) to 8.3.3 and updated Cornerstone to 5.3.3.
Cleared the Cache, Purged the URL, Purged the OPcache and Preloaded Cache. Logged out and then in again.
On the backend Query monitor report looked good, but on the frontend the error was still seen. I switched themes from X theme child theme to the default Twenty Twenty One.
I also noticed that the backend was now extremly slow. It was not that slow before the latest update of Theme X.

After some more refreshing the WooCommerce style errors showed up in the backend as well. At the same time there were multiple slow errors reported in Query Monitor. After a few more times refreshing it seems that the errors come and go in the backend but they are still seen in the frontend.

Conclusion: Updating to newest ThemeX made the backend and frontend extremly slow (for logged in users) and the WooCommerce style errors are still seen.

This is a very active site, and I have already reset the web site once. This time I need to get this error fixed.

[ruenel]

Hello @stefaneklund,

I have logged in and checked your site. I am not seeing any errors. This is what I’ve got:

Please do install the WP-Optimize plugin and run the optimization. You can remove it later on. What this plugin does is, it will remove orphaned data that was used by the previous version of the theme. The orphaned usually adds up query time and running the plugin makes the query faster.

Kindly let us know how it goes.

[stefaneklund]

Hi

Here are a few additional things I have done.
I cleared out the old IThemes Security log files. Then reset the Stream plugin records.
Cleaned up the database with WP Rocket. Even activated and ran WP Optimize again.

I turned off all the plugins and turned them on one by one. At the end I noticed it was Query Monitor itself that made the backend and frontend very slow for users who are logged in.

So one recommendation for anyone who comes across this thread. Turn off Query Monitor, do a hard refresh and then check the backend and frontend and see if the site is faster.
Only use Query Monitor to check the site, and after having checked deactivate it.

Thank you @ruenel Rue for your reply!

[ruenel]

You are most welcome @stefaneklund.