wp_options Autoload Bloat: Find and Fix the Options Slowing WordPress

wp_options Autoload Bloat: Find and Fix the Options Slowing WordPress

The wp_options table loads every row marked autoload=yes on every single page request, so bloated autoloaded data quietly taxes your whole site. If your WordPress install feels sluggish for no obvious reason, the culprit is often a few oversized options dragging down each load. Here is how to find them and clean up safely.

Why autoloaded options matter

On every request, WordPress reads all autoload=yes rows from wp_options into memory at once. That is fine when the data is small. The problem is that plugins and themes often dump large values there, and leftover data lingers long after a plugin is gone.

Common offenders include:

  • Orphaned plugin data: settings and caches from plugins you removed but never cleaned up.
  • Runaway transients: expired or stale transients that should have been cleared.
  • Oversized option blobs: serialized arrays, logs, or license data weighing in at hundreds of KB.

A handful of these can push your autoloaded total into the megabytes, and that cost is paid on every page view by every visitor.

Find the biggest autoloaded options

You do not have to guess. Paste your query output into the wp_options Autoload Analyzer and it surfaces the largest autoloaded options so you can see exactly what is eating your load budget. It runs entirely in your browser, so the data you paste never leaves your device.

To pull that data, run this read-only SQL against your database (via phpMyAdmin, Adminer, or WP-CLI):

SELECT option_name, ROUND(LENGTH(option_value) / 1024, 2) AS size_kb
FROM wp_options
WHERE autoload = 'yes'
ORDER BY LENGTH(option_value) DESC
LIMIT 30;

Adjust the table prefix if yours is not wp_. Copy the result and feed it to the analyzer for a ranked, readable breakdown.

Clean up safely in four steps

  1. Run the SQL above and paste the output into the wp_options Autoload Analyzer.
  2. Identify rows that are clearly orphaned: data from plugins you no longer run, or obvious transient junk.
  3. Back up your database first. Always. A single bad delete can break a live site.
  4. Remove or set autoload=no for the safe candidates, then retest your page load times.

Be careful here. Deleting an option that an active plugin still needs can cause errors or reset settings. When in doubt, set autoload to no rather than deleting outright, and confirm the site still works before moving on.

Find the heavy options, back up, trim the dead weight, and every page on your site gets faster.

← All posts