Skip to content

Analyser

Autoloaded options analyser

WordPress loads every autoloaded option early in each request. Paste the list from WP-CLI and see the total, the largest rows and the prefixes they share, before you decide what to change.

Run this with WP-CLI on the site (or staging) and paste what it prints. The article's SQL query works too.

wp option list --autoload=on --fields=option_name,size_bytes --format=csv
If the list has no header, its sizes are in

Nothing you paste leaves this page: the analysis runs in your browser.

The report appears here.

What to do with the result

  1. Back up the database and work on staging.
  2. Find the plugin or theme that owns each large option, and where it is read.
  3. Change the autoload flag through WordPress rather than a direct SQL update: wp_set_option_autoload_values() (WordPress 6.4+) also invalidates the caches it should.
  4. Measure peak memory and uncached TTFB again, and test the owner's admin and front-end flows.

Measuring and reviewing autoloaded options explains each step and the WordPress 6.6 changes.

Not sure what owns an option?

Send me the largest rows and I will say which ones I would look at first, and how to change them safely.

Start a conversationWordPress performance optimizationMore free tools