You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After experiencing performance problems with my site(s), I’ve tracked the problem down to this plugin. When active in a website running the Site Editor, it runs around 500 additional database queries on the search page.
A regular call to the search page without the plugin active runs around 60-70 database queries. When the plugin is active, it varies between 550-600 queries. Using Query Monitor to analyse them, it seems that these additional queries are almost all to WP_Term_Query->get_terms(), which is called (on average) 393 times.
The page I need help with: [log in to see the link]
Any updates on this @ZafarKamal123? I've done my own analysis to find that Editor's Kit creates by far the most database queries performing 466 queries and taking about 0.2s total. It's a useful plugin though it adds an extra 30% on total page load time which is a lot for a plugin that is often used for small changes.
It seems that the plugin already supports enabling/disabling features in the settings, why not use this to only perform queries for features that are in use? I'd imagine this could massively improve performance for those that care enough about performance to disable unused features
Support
After experiencing performance problems with my site(s), I’ve tracked the problem down to this plugin. When active in a website running the Site Editor, it runs around 500 additional database queries on the search page.
A regular call to the search page without the plugin active runs around 60-70 database queries. When the plugin is active, it varies between 550-600 queries. Using Query Monitor to analyse them, it seems that these additional queries are almost all to
WP_Term_Query->get_terms()
, which is called (on average) 393 times.The page I need help with: [log in to see the link]
Details
Note: This support issue is created automatically via GitHub action.
The text was updated successfully, but these errors were encountered: