The Silent Killer of WordPress Performance
Every time a page loads, WordPress executes a query to load all options in `wp_options` where `autoload = ‘yes’`. Over time, deactivated plugins and persistent transients accumulate, swelling autoloaded data to several megabytes and crippling server response times.
Auditing Autoload Size
A healthy WordPress site should keep autoloaded options below 800 KB. Auditing and removing abandoned plugin settings and converting transient caches to an in-memory object cache (Redis or Memcached) dramatically reduces database load.
FAQ
Frequently Asked Questions
Ideal autoloaded options size is under 800 KB. Sites with autoload data exceeding 2 MB frequently experience elevated TTFB and database strain.
Expired transients that fail to delete bloat the `wp_options` table, slowing down query indexing and table scans.
Yes. Removing old post revisions is safe and can reduce database table sizes by 30% to 60% on content-rich websites.
WP-CLI command `wp option list –autoload=on` or database inspection plugins like Query Monitor allow rapid diagnosis of large option keys.
An external object cache like Redis moves transient and query storage into fast RAM, reducing repeated queries against MySQL.
