| 开发者 |
joostdevalk
aristath filipi progressplanner |
|---|---|
| 更新时间 | 2026年11月2日 20:17 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-3.0-or-later |
| 版权网址: | 版权信息 |
wp_options table on every single page request. Many of
those options belong to plugins you removed long ago, or simply don't need
to be autoloaded. The result: a bigger database query, slower page loads,
and wasted server resources.
AAA Autoload Optimizer tracks which autoloaded options your site actually
uses, then shows you the ones it doesn't — so you can safely remove them
or turn off autoloading.
/wp-content/plugins/aaa-option-optimizer/ via FTP.The safest action — disabling autoload — is non-destructive. The option remains in your database and can still be loaded on demand. Deleting an option is permanent, so only do that for options you're confident are no longer needed (e.g., from plugins you've already removed). Always back up your database before making bulk changes.
Disabling autoload can be reversed from the "All Options" tab. Deleting an option is permanent. If you need it back, you'll need to restore from a database backup.
A few days of normal browsing is usually enough. If you have a lot of visitors, a few hours might even suffice. The goal is to visit every major page on your site (front end and admin) so the plugin can record which options are actually used. If you're thorough, you can start optimizing sooner.
The plugin currently targets single-site installations. Multisite compatibility has not been officially tested.
The plugin identifies the source of each option (which plugin, theme, or WordPress core). If an option belongs to a plugin you've already deactivated and removed, it's generally safe to delete. When in doubt, disable autoloading instead of deleting — it's the safer choice.
Yes, always back up your database before optimizing. Disabling autoload is safe and reversible, but deleting options is permanent.
Names that can't be real options are ignored: empty names and names longer
than 191 characters. Developers can exclude more names with the
aaa_option_optimizer_is_trackable_option_name filter, which receives
whether the name should be tracked and the option name. Keep in mind that
an autoloaded option excluded this way will be listed as unused. The 191
character limit can't be changed.
Please use the GitHub repository for bug reports and code suggestions. The WordPress.org support forum works too for general questions.
Through the Patchstack Vulnerability Disclosure Program. The Patchstack team validates, triages, and handles all security reports. Report a security vulnerability here.
Submit a pull request on GitHub to known-plugins.json.
aaa_option_optimizer_is_trackable_option_name filter to
exclude option names from tracking.known-plugins.json.known-plugins.json.false when it's being loaded but doesn't exist.
1.1
The plugin now recognizes plugins from which the options came (thanks to
a great pull by
Rogier Lankhorst).
If you're a plugin developer and want your plugin's options properly
recognized, please do a pull request on
this file.
Small enhancements:
KB to the table heading, so
that you can now properly sort numbers.popover, as suggested with a great
pull request by
@rogierlankhorst.