All Modules LITE & PRO

Autoload Governor

Identifies the autoloaded WordPress options silently consuming PHP memory on every single page request — and exactly which plugins are responsible.

  • 800 KB Critical Threshold
  • 0 Database Writes
  • Read-Only Architecture

What This Module Does

Every autoloaded option in WordPress's options table is loaded into memory on every page request — before a single line of your theme or plugin code runs. Most plugins autoload everything by default. Over time this payload grows until it becomes a significant, invisible tax on every WordPress page load. The Autoload Governor measures the total payload, ranks the worst offenders by size, and attributes each item to the plugin responsible.

Features at a Glance

Total Autoload Payload with Thresholds

Displays total WordPress autoload size with tiered thresholds: warning at 500 KB, critical at 800 KB. This single number directly correlates with memory consumption and time-to-first-byte on every single page load.

Plugin Attribution by Prefix

Groups autoloaded options by their WordPress option name prefix to identify which plugin is responsible for the most autoload weight. Immediately answers "which plugin is causing this?" without manual investigation.

Full Sorted Offender List

A complete, size-sorted table of every autoloaded option with its name, value size, and a "How to Disable" button that shows the exact code needed to disable autoloading for that specific option.

Per-Item Disable Guidance

For each identified offender, the module explains how a developer can disable WordPress autoloading — through plugin settings, a filter, or wp_update_autoload_option() in WordPress 6.4+.

Critical Warning at 800 KB

When the total WordPress autoload payload exceeds 800 KB, a critical notice explains the performance impact and recommends immediate review. At this level, autoloaded data can add 20–80ms to every page request.

Why It Matters

  • Understand exactly why your WordPress site's time-to-first-byte is higher than it should be
  • Identify which newly-installed plugin caused an autoload performance regression in WordPress
  • Build a concrete case for plugin removal or replacement with hard autoload size data
  • Provide clients with a clear, non-technical explanation of hidden WordPress performance overhead
  • Prioritise WordPress database optimisation work based on actual measured impact, not guesswork

Frequently Asked Questions

Why are autoloaded WordPress options a performance problem?

WordPress calls wp_load_alloptions() on every request, loading all autoloaded options into memory at once. A 2 MB autoload payload means 2 MB is deserialized and held in PHP memory before your theme runs — even if 95% of it is never used on that page.

Can WP Health Inspector disable autoloading for me?

No. The plugin is strictly read-only. It identifies the offenders and provides guidance, but all remediation is performed by a developer. This keeps the plugin completely safe to run on production WordPress sites.

What's the difference between Lite and Pro for the WordPress Autoload Governor?

Lite shows the total autoload payload, the critical threshold warning, and the full sorted list of individual autoloaded options. Pro adds complete per-plugin attribution grouping and the tiered 500 KB warning threshold.

What is a normal WordPress autoload payload size?

A fresh WordPress installation autoloads approximately 50–100 KB. Sites with 20–30 active plugins commonly see 400–600 KB. Above 800 KB is where measurable page load degradation consistently appears.

Find the Silent WordPress Performance Killer

The Autoload Governor reveals exactly what's loading into PHP memory on every WordPress request — and which plugin is responsible.

Get Full Pro Access

Pro adds complete per-plugin attribution grouping with prefix-level breakdowns and the tiered 500 KB warning threshold.

Get Pro Now

Try the Free Lite Version

Lite shows the full sorted offender list with per-item sizes and disable guidance — completely free.

Download Lite — Free