What this problem looks like
Autoload yes means WordPress loads the option on every request. Transients should use autoload no. Some migration and SEO plugins accidentally autoload huge serialized arrays.
Total autoload under 800 KB is healthy on most sites. Above 2 MB warrants immediate investigation.
Do not flip autoload on core WordPress options without knowing their role. Backup database before UPDATE queries on wp_options.
Check total autoload weight
sql
SELECT SUM(LENGTH(option_value)) AS autoload_bytes
FROM wp_options
WHERE autoload = 'yes';Find the largest rows
Match option_name prefixes to plugins: _transient_, woocommerce_, rank_math_, elementor_, wpseo_.
sql
SELECT option_name,
LENGTH(option_value) AS size_bytes,
autoload
FROM wp_options
ORDER BY size_bytes DESC
LIMIT 30;Set autoload to no safely
For plugin cache blobs that should not load globally:
sql
UPDATE wp_options
SET autoload = 'no'
WHERE option_name = 'example_plugin_cache_blob';Use WP-CLI when available
bash
wp option list --autoload=on --format=table
wp option update my_large_option 'value' --autoload=noPrevent recurrence
After plugin updates, recheck autoload size monthly on busy sites. Object cache reduces repeated option queries but does not fix loading megabytes into PHP memory on cache miss.
Plugins like Autoload Optimizer can help audit, but manual review prevents breaking critical options.
When to stop DIY and hire help
Autoload bloat combined with multisite or custom option tables needs developer review. BugShield fixes runaway wp_options on production stores.