What It Does
WordPress loads every autoloaded option into memory on every single request. Over time, options from deactivated plugins, oversized cached data, and tracker bloat accumulate — wasting memory and slowing requests. This module scans your wp_options table, classifies each autoloaded option by source (core, active plugin, inactive plugin, oversized, or bloat pattern), and lets you safely disable autoload on the ones that do not need to be loaded every time. Optimization never deletes data — it only changes the autoload flag. A separate per-option Delete action exists for options you explicitly want removed.
Features
- Health check that classifies all autoloaded options into six categories: safe (core), active plugin, inactive plugin, oversized (>10KB), bloat patterns, and unrecognized
- Plugin detection using both folder name and TextDomain metadata from plugin headers — far fewer false positives than folder-name-only matching
- Inactive-plugin options are flagged as candidates; active-plugin options stay autoloaded unless oversized (>10KB) or matching a bloat pattern
- Known bloat pattern detection for common offenders: action_scheduler_, wc_tracks_, woocommerce_tracker_, _elementor_, jetpack_, wpseo_, rank_math_, aioseo_, wp_rocket_, litespeed_, w3tc_, autoptimize_
- Oversized option detection — flags individual options larger than 10KB that are loaded on every request
- Unrecognized options shown for information only — never automatically optimized (safety first)
- Full backup created before any optimization — stored in database for one-click restore
- One-click restore to revert all autoload changes
- Learning mode: temporarily un-autoloads all non-core options, tracks which are actually accessed, then re-autoloads the ones real traffic uses
- Learning mode tracks admin vs frontend access patterns separately
- Usage percentage thresholds (high/medium/low) for learning mode optimization decisions
- Supports WordPress 6.6+ autoload values (on/off/auto) and pre-6.6 values (yes/no)
- Individual option toggle — enable/disable autoload for any specific option
- Edit and delete individual options from the admin UI
- Developer filter hook: wpmultitool_autoload_candidates to exempt specific options from optimization
- Admin notice when significant optimization opportunities are detected
- DataStar SSE-powered UI for real-time progress during analysis and optimization
How to Use
-
Run the Health Check
Go to WP Multitool > Autoload Optimizer and click "Analyze". The module scans all autoloaded options and categorizes them. This is read-only — nothing changes yet.
-
Review the results
Look at the categorized breakdown. "Inactive Plugin" options are the safest to optimize. "Oversized" and "Bloat Patterns" are also good candidates. "Unrecognized" options require manual investigation.
-
Quick Optimize (recommended)
Click "Optimize" to disable autoload on all identified candidates (inactive plugin options, oversized options, and bloat patterns). A backup is created automatically before any changes.
-
Or use Learning Mode (advanced)
For a more data-driven approach, start Learning Mode. This disables autoload on all non-safe options and tracks which ones are actually accessed over time. Run it for 24-48 hours minimum, then stop it to apply optimizations based on real usage data.
-
Verify your site
After optimizing, test your site thoroughly — check critical pages, forms, checkout (if WooCommerce), and admin functionality. If anything breaks, use the one-click restore.
Settings
| Setting | Default | Description |
|---|---|---|
| Oversized Threshold | 10KB (fixed) |
Options larger than 10KB are flagged as "oversized". This limit is fixed and not configurable. |
| Learning Mode | Off |
When enabled, tracks which options are actually accessed per request. Provides usage percentage data for informed optimization decisions. |
| High Threshold | 90% |
Options accessed on 90%+ of requests are re-autoloaded when learning mode stops. This is the only threshold that drives optimization. |
| Medium Threshold | 50% |
Display band only — colors the usage column in the results table. Does not affect optimization. |
| Low Threshold | 10% |
Display band only — colors the usage column in the results table. Does not affect optimization. |
FAQ
Will this break my site?
It is very unlikely. Optimization only changes the autoload flag — no data is deleted. When a plugin requests an option that is no longer autoloaded, WordPress loads it on demand with a separate query. A full backup is created before changes, and you can restore with one click.
How much space and memory can I save?
It depends on your plugin history. Typical sites save 100-300KB per request. WooCommerce sites with many extensions often save 500KB-2MB per request. Use the Health Check to see your exact numbers before optimizing.
How long should Learning Mode run?
24-48 hours minimum. The longer it runs, the more accurate the usage data. Learning Mode adds slight overhead because it tracks every option access, so do not run it indefinitely.
What happens if I reactivate a deactivated plugin?
The plugin works normally. WordPress loads its options on demand instead of preloading them. The tiny per-request cost of loading them individually is negligible. To restore autoloading, use the Restore Backup feature.
Why are some options listed as "Unrecognized"?
These are options that do not match any installed plugin prefix, WordPress core, or known bloat pattern. They might come from your active theme, must-use plugins, deleted plugins, or custom code. The module never automatically optimizes these to avoid breaking unknown functionality.
Ready to optimize your WordPress site?
Join developers using WP Multitool to debug, optimize, and maintain WordPress.
Get WP Multitool