Autoloaded options could affect performance? Find the rows
WordPress loads these rows into memory on every request, before anything else happens. Once they pass a megabyte, every page on the store pays for it.
The symptom
The whole site is slow, not one page. The admin feels sluggish, the cart is slow even though it is excluded from caching, and time-to-first-byte is poor on pages that should be trivial to serve. Nothing in particular looks wrong, and every fix you try helps a little and not enough.
Since WordPress 6.6, Tools → Site Health says it out loud: Autoloaded options could affect
performance, listed as a critical issue once autoloaded data reaches 800,000 bytes. Plugins can
move that threshold with the site_status_autoloaded_options_size_limit filter.
What it costs
WordPress reads every option marked for autoload into memory on every request, in one query, before it knows what page it is about to render. That is by design, and it is fast when the data is small.
A WooCommerce store is unusually good at making it not small:
- Plugins that store a whole configuration blob, a license payload or a cached API response as one autoloaded option.
- Plugins you deleted long ago. Many leave their options in the database when you delete them.
- Transients saved without an expiry date. WordPress loads them on every request and never cleans them up.
The effect is worst precisely where it hurts most. Cart, checkout and account pages are excluded from page caching by design, so they pay the full cost of that query on every load, for every customer, at the exact moment they are deciding to pay you.
Merchlint reports anything above 1 MB. For context, a lean store sits in the low hundreds of kilobytes.
Worth knowing: WordPress 6.6 stopped autoloading very large new options by default, so a fresh install is less prone to this. Rows that already existed keep the setting they were given, which is why older stores are the ones that find something here.
How to check it yourself
The total, first:
wp db query "SELECT ROUND(SUM(LENGTH(option_value))/1024/1024, 2) AS mb, COUNT(*) AS rows_
FROM wp_options WHERE autoload IN ('yes','on','auto-on','auto')"
Then the offenders, which is where the answer actually is:
wp db query "SELECT option_name, ROUND(LENGTH(option_value)/1024, 1) AS kb
FROM wp_options WHERE autoload IN ('yes','on','auto-on','auto')
ORDER BY LENGTH(option_value) DESC LIMIT 25"
Replace wp_ with your table prefix. All four values mean “load on every request” since WordPress
6.6. Checking only yes and on misses part of the total. For the same reason,
wp option list --autoload=on shows only some of these rows.
Almost always, three or four rows account for most of the total. This is not a problem you solve by trimming everything.
How to fix it
-
Identify the owner of each large row before touching it. The option name usually names its plugin. If the plugin is still installed, the row may be needed—just not on every request.
-
Turn off autoload rather than deleting, where the data is still wanted:
wp option set-autoload some_big_option offThe option stays; WordPress just stops loading it before every page. The command needs WP-CLI 2.8 or newer.
-
Delete leftovers from plugins you no longer have. Those are the safest wins and often the biggest ones. Take a database backup first, because this one cannot be undone.
-
Delete large transients. Rows whose name starts with
_transient_are temporary copies, and the plugin that made them rebuilds them when it needs them. Pass the name without that prefix:wp transient delete some_transient_name -
Re-run the total. If it did not move, you removed the wrong rows.
When it’s a false alarm
- A single large option a plugin genuinely needs on every request. Rare, but real—some page builders and multilingual plugins do this deliberately. Nothing to fix beyond knowing.
- A store on a host with generous memory and object caching, where a megabyte is loaded from Redis rather than MySQL and costs far less. The number is still worth watching, since it tends to grow.
- A threshold that does not fit your store. A large installation may run fine above 1 MB. The
free plugin has no setting for the threshold, but a developer can change it with the
merchlint_scan_settingsfilter (thed2_max_byteskey). Otherwise, hide the finding if you have checked the rows and they are needed.
How Merchlint finds it
Merchlint adds up the size of every option marked for autoload, counting all four values WordPress uses for it, and compares the total with 1 MB. The finding shows the total, the threshold and the five largest options by name and size, because a total on its own tells you there is a problem and gives you nowhere to start.
Confidence: F—fact from the database. A sum of stored lengths compared with a number.
This check reads wp_options and nothing else. It changes no rows, deletes no transients and turns
off no autoload flags. The fixes under “How to fix it” are yours to run, deliberately, with a backup.
That is how the whole plugin works: it tells you exactly which rows are the problem, and it does not
touch them.
Doesn't match what you see in your store? Email us—we read every message. contact@merchlint.com