wp_options Autoload Analyzer
Paste a wp_options dump to find the largest autoloaded options slowing down WordPress. Parsing runs in your browser; nothing is uploaded.
SELECT option_name, option_value, autoload, LENGTH(option_value) AS size_bytes FROM wp_options ORDER BY size_bytes DESC LIMIT 200;
| Option name | Size | Autoload | Flag | Value preview |
|---|
About the wp_options Autoload Analyzer
The wp_options Autoload Analyzer helps you find the autoloaded options that load on every WordPress request and slow your site down. WordPress loads all options marked autoload=yes into memory on every page view, so a few oversized rows can add real overhead. Paste the result of a short SQL query and the tool shows your total autoload size, ranks the largest options, and flags likely problems such as bloated transients and abandoned plugin data. It is built for WordPress developers, agencies, and store owners auditing performance. Parsing runs entirely in your browser, so option names and values never leave your machine.
How it works
- Run the provided SQL query in phpMyAdmin, Adminer, TablePlus, or any MySQL client, then copy the result. The query returns each option with its name, value, autoload flag, and size in bytes.
- Paste the rows into the CSV / Tab-separated box, or use Manual entry to paste simple name, size, autoload rows.
- Click Analyze. The summary cards show total options, autoloaded count and size, total data size, and how many autoloaded transients exist.
- Sort and filter the table to review the largest rows. Flagged options point to oversized autoloaded data and transients you can move to autoload=no or clean up.
Features
- Total autoload size and a ranked table of the largest autoloaded options.
- Automatic flags for autoloaded options over 100KB, rows over 10KB, and transients that should not autoload.
- Accepts phpMyAdmin tab-separated exports, comma-separated values, or manual rows; columns can be in any order.
- Search, autoload filter, flagged-only view, and sorting by size or name, with pagination for large dumps.
- Copy-ready SQL query so you can pull the exact data the tool expects in one step.
Frequently asked questions
What is autoload and why does it matter?
Every WordPress option has an autoload flag. Options with autoload=yes are loaded into memory in a single query on every request, whether or not the page uses them. When the autoloaded data grows into hundreds of kilobytes or more, it adds memory use and slows down every page load, including the admin.
What SQL query should I run?
Use: SELECT option_name, option_value, autoload, LENGTH(option_value) AS size_bytes FROM wp_options ORDER BY size_bytes DESC LIMIT 200; Replace wp_ with your real table prefix if it differs. The tool shows this query with a copy button. Running it in phpMyAdmin or a MySQL client and pasting the result is all that is needed.
Is my database data uploaded anywhere?
No. All parsing and analysis happen in your browser. The tool does not connect to your site or database and does not send the pasted rows to any server. Nothing is uploaded or logged.
What gets flagged and what should I do about it?
The tool flags autoloaded options over 100KB and autoloaded transients over 1KB as Critical, and autoloaded rows over 10KB or any autoloaded transient as Review. Transients should generally not autoload, and large rows from removed plugins are common offenders. Investigate each flagged row, then set its autoload to no or delete stale data after confirming it is safe.
How do I change an option to not autoload?
On modern WordPress you can use WP-CLI, for example: wp option set option_name value --autoload=no, or update the autoload column directly in the database for known-safe rows. Always back up first and test on staging. This tool only reports the data; it does not modify your database.