However, there are a number of autoloaded options on the site (e.g. elementor_pro_remote_info_api_data_3.2.1) that all seem to relate to the Elementor page builder, which I stopped using 3 years ago. I would like to disable autoloading of these options as they account for about 250Kb of data. However, when I try to do this from Tools->Site Health, the response is “The option does not exist” and the option is not removed.
Can anyone suggest how to disable these options?
Thanks.
]]>Thanks,
]]>My web host said that I’m getting a massive problems with autoloads from the plugin and suggested I reach out for assistance. Here is a screenshot of the issue. Thank you.
My site has a large number of autoloads and it appears that some of the largest ones are coming from the gallery per my web host provider:
The high number and large size of autoloaded options in your WordPress database can significantly slow down your site. Here are the largest autoloaded options in your application:
Is it possible to provide me with some methods to fix the issue on my end? Thank you.
]]>On LiteSpeed caching plugin’s database details shows ‘timetable_google_fonts’ option being significantly bigger than all other options (see the attached screenshot).
Timetable plugin is set to use the ‘Developer Mode’. Could you suggest something to fix this issue as this is something we’ve not seen before on any of our sites?
Thanks and regards,
In a recent database audit our developer noticed that there are many autoloaded options from your plugin. Such as ‘woosw_list_HI2MOD’ and the biggest is 163.84 KB and others are at least 60 KB. We have concerns how this is affecting performance.
Why are these autoloaded? Would it be possible to not have them autoloaded, especially when the wishlist functionality is disabled for “unauthenticated users”?
]]>It seems that having many autoloaded options, especially big ones, slows the loading of all pages of a site.
It seems to impact the TTFB (time to first byte), and it can be signaled as a problem in the health check.
Is it true ?
I disabled the autoload of many options with the plugin SweepPress, and it improved some Core web vitals.
How is this problem related to the PHP server memory ? Shouldn’t a big memory (like 64mo) be far enough when the wp options reaches something 2 mo ?
And, when I use an object cache on the server, like Redis Cache, does it store all the data that are NOT autoloaded, replacing the autoload function a better way ?
What are exactly the consequences of disabling some autoloaded options ? A non-autoloaded option will cause a call to the database, and take more loading time than if it was autoloaded ?
If someone could explain how those things are related – autoloaded options, server memory, object cache – I would make better choices in optimizing my sites and my customers’s sites !
Thanks in advanced to anybody willing to get me out of this technical fog !
]]>