Site Health Status – autoloaded options could affect performance

  • Resolved ongaku99

    (@ongaku99)


    3 months, 1 week ago

    Under Site Health Status, some users are now being warned that autoloaded options could affect performance. For example, “Your site has xxx autoloaded options (size: x KB/MB) in the options table, which could cause your site to be slow.” Do you have any suggestions on how to address this issue within Optimizations or Tables? My database shows an Overhead of 1.26 MB in wp_options. Would converting from MyISAM to InnoDB help, or would it make little difference? Any input would be appreciated!

    Thanks.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wpmansour

    (@wpmansour)

    To address the Site Health warning about autoloaded options affecting performance, you can take a few steps to optimize your database. First, use WP-Optimize to clean up unnecessary data like post revisions, spam comments, and transient options, which will help reduce the size of your database. You should also remove the 1.26 MB overhead in your wp_options table using WP-Optimize. Converting your tables from MyISAM to InnoDB can improve performance, especially if your site handles a lot of read/write operations, but it won’t directly reduce the number of autoloaded options. Lastly, consider manually reviewing and managing large autoloaded options using a tool like “Query Monitor” to ensure none are unnecessarily bloated. These steps should help mitigate the impact on your site’s performance.

    Angel Aparicio

    (@angel_aparicio_gomez)

    Ignore this, sorry

    @wpmansour when you say “remove the 1.26 MB overhead in your?wp_options?table using WP-Optimize”, how? My wp_options table appears fairly small, but the Site Health tool is saying I have 2MB of autoloaded content. My host (SiteGround) directed me to WP Optimize to address this but I’m having a hard time figuring out how to identify and address autoloaded content within the plugin documentation…

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.