How to optimise WordPress autoloaded options

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.

Step 1: Check total autoload weight

Run this in phpMyAdmin or your database tool:

sql

SELECT SUM(LENGTH(option_value)) AS autoload_bytes
FROM wp_options
WHERE autoload = 'yes';

Step 2: 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;

Step 3: Set autoload to no safely

For plugin cache blobs that should not load globally, run in phpMyAdmin after backup:

sql

UPDATE wp_options
SET autoload = 'no'
WHERE option_name = 'example_plugin_cache_blob';

Step 4: Use WP-CLI when available

The commands below need SSH access and will not work inside File Manager:

bash

wp option list --autoload=on --format=table
wp option update my_large_option 'value' --autoload=no

Step 5: Prevent 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.

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 at a confirmed price without hourly billing surprises.

Questions answered

WordPress autoloaded options FAQs

Answers about measuring autoload size, identifying owners, removing stale options, protecting active settings, and confirming performance improvements.

What is a healthy autoload size?

Under 1 MB total is a practical target. Many fast sites stay under 300 KB.

Can autoload slow WooCommerce checkout?

Yes. Checkout loads the full options table early. Large autoload rows add latency to every AJAX request.

Should transients autoload?

No. Expired transients should be cleaned. Active transients should use autoload = 'no'.

Will object cache hide autoload problems?

Partially. First request after cache flush still pays the full autoload cost in PHP memory.

What are WordPress autoloaded options?

They are rows in the options table that WordPress loads together near the start of many requests, even when a page does not use every value.

How do I measure WordPress autoloaded option size?

Use Site Health, WP-CLI, or a read-only database query to total autoloaded values and list the largest option names without printing sensitive contents.

How do I identify which plugin owns an autoloaded option?

Match the option-name prefix with active and removed plugins, search vendor documentation and code, and confirm usage on staging before changing it.

Is it safe to delete large WordPress autoloaded options?

Not based on size alone. Active plugins and themes may require them. Back up first and remove only data confirmed to be stale or safely recreated.

Can I change an option from autoload yes to no?

Sometimes, when the value is large and rarely used, but the owning code may expect it to be available early. Test the exact feature and cache behaviour.

How do I verify autoload optimisation helped WordPress?

Compare autoload bytes, database query time, uncached server response time, wp-admin behaviour, and error logs under the same test conditions.

Keep troubleshooting

Learn how to optimize WordPress autoloaded options.