Question

Autoloaded Data

  • 19 September 2021
  • 0 replies
  • 62 views

 My site has high DB Autoloaded data, and Elementor seems to be the cause of it.

In WordPress, the database holds many of my site’s settings. These settings can include a list of active plugins, your active theme, your site’s URL, theme settings, plugin settings, and more. The wp_options table in your database is where these settings are stored. Sometimes themes and plugins like to store extra items there, like Transients, long lists of redirect rules, and other lengthy settings. In this table there is a column labeled “autoload” which generally tells WordPress: does this setting need to be loaded on every page by default? If the answer is “yes” for some of these extremely lengthy settings, that’s extra data and bytes that WordPress has to load on your pages. Too much content set to “autoload” will lead to high Time to First Byte, and slow query performance in general.

I ran report on your site specifically regarding Autoloaded Data, and here are the findings. The database has 388 of 504 rows set set to Autoload = yes in the wp_options table, which is very good. However, the maximum recommended number in bytes of autoloaded data is 800,000 and of course, the lower the better. It seems your site is using 755,180 bytes, which is under the threshold, but could be better. Here is a break down of the top 20 options that load on every single page load and how many bytes they use up.

+----------------------+--------------------------------------------------+
| LENGTH(option_value) | option_name |
+----------------------+--------------------------------------------------+
| 127712 | elementor_pro_remote_info_api_data_3.2.1 |
| 127391 | elementor_pro_remote_info_api_data_2.5.8 |
| 76173 | ad47b1c423907501a2c250dfb97a9949 |
| 74595 | edd_api_request_ad47b1c423907501a2c250dfb97a9949 |
| 72535 | 9eed5cbf9882a8e5fbafd9d46132f098 |
| 42897 | redux_builder_amp |
| 35893 | elementor_pro_remote_info_api_data_3.3.4 |
| 27848 | elementor_pro_remote_info_api_data_3.3.3 |
| 27646 | elementor_pro_remote_info_api_data_3.3.2 |
| 26796 | elementor_pro_remote_info_api_data_3.3.1 |
| 26286 | elementor_pro_remote_info_api_data_3.3.0 |
| 24605 | elementor_pro_remote_info_api_data_3.2.2 |
| 8525 | rewrite_rules |
| 5612 | seopress_pro_option_name |
| 4433 | wp_rocket_settings |
| 4250 | wp_user_roles |
| 3565 | wpseo_titles |
| 3342 | cron |
| 2607 | wphb_settings |
| 2576 | seopress_google_analytics_option_name |
+----------------------+--------------------------------------------------+

So it seems the elementor_pro_remote_info_api_data system seems to want to store a lot of data. I was able to trace that back to the /elementor-pro/ Plugin. It may be best to reach out to the author of that plugin to see if all that data is really necessary to "autoload" or if there could be a bug in the system that the author might be able to fix. Also, sometimes there are settings or configurations you might be able to adjust that might help reduce the bytes loaded.


0 replies

Be the first to reply!

Reply