Huge plugin initialization issue
-
I have noticed that Getwid runs 50+ SQL queries on every single administration page, regardless of what that page is, every single page loads! All queries look like this:
SELECT option_value FROM wp_options WHERE option_name = 'getwid/icon::disabled' LIMIT 1
It seems that the plugin checks each block individually if it is disabled or not, and each one has its own option in the options table, and for each one ‘autoload’ is not used, ending in running quite a lot of SQL queries. Why do you need to run these queries outside of the editor pages in the first place? Can you please change how this part of the plugin works, and store these settings in a more optimal way? Right now your plugin accounts for 40% of all SQL queries run on the admin side on my website, it is really terrible method you used here for the otherwise excellent plugin.
Regards,
Milan
- The topic ‘Huge plugin initialization issue’ is closed to new replies.