Kazuto Takeshita

The <code>wp_options</code> table accumulates leftovers from plugins and themes that have been deactivated or deleted but never cleaned up. Those rows bloat the autoload payload on every page load and there is no built-in way to decide which ones are safe to remove.
Orpharion observes which options are actually read at runtime, attributes each read to the plugin or theme that caused it, and surfaces the raw signals (accessor, autoload flag, size, last-read timestamp) so administrators can decide what to remove:
<ol>
<li>Observe — the tracker records when and by whom each option is read, using the live PHP backtrace to identify the real caller.</li>
<li>Quarantine — rename the option temporarily so WordPress and the accessing plugin can no longer see it; confirm nothing breaks.</li>
<li>Delete — the row is removed from both <code>wp_options</code> and the tracking table. Use the Export selected bulk action first if you want a restore copy; Orpharion never writes option_value content to the server filesystem on your behalf (option_value can contain API keys, SMTP credentials, and other secrets that should not leak into backups of <code>wp-content/</code>).</li>
</ol>
Core WordPress options are locked out of destructive operations, on both the deletion and the import side.
The full PHP source ships uncompiled with the plugin; the non-compiled source of the compiled admin bundle (<code>build/index.js</code>, <code>build/index.css</code>) is published at https://github.com/mt8/orpharion — see the Source code section below for the exact build steps.
<h3>Source code</h3>
The published plugin ships with the compiled admin bundle in <code>build/</code> (<code>build/index.js</code>, <code>build/index.css</code>, <code>build/index.asset.php</code>). The non-compiled source for that bundle lives in <code>src/</code> in the public GitHub repository:
<ul>
<li>Repository: https://github.com/mt8/orpharion</li>
<li>Build tool: <a href="https://www.npmjs.com/package/@wordpress/scripts" rel="nofollow ugc">@wordpress/scripts</a> (uses webpack + Babel under the hood).</li>
<li>
Reproduce the bundle:
<ol>
<li>Clone the repository.</li>
<li>Install dependencies: <code>npm install</code> (Node.js version compatible with <code>@wordpress/scripts</code> is required).</li>
<li>Build: <code>npm run build</code> — produces the same <code>build/</code> files that are shipped with the plugin.</li>
<li>Watch mode for development: <code>npm run start</code>.</li>
</ol>
</li>
</ul>
PHP code is shipped uncompiled and is the same in the published ZIP and in the repository.
<h3>Features</h3>
<ul>
<li>Per-option read tracking via dynamically registered <code>option_{$name}</code> filters, so every <code>get_option()</code> call is attributed to the real plugin or theme on the call stack.</li>
<li>Accessor inference (live tracker data → slug prefix → curated core list) with an active / inactive flag so you can filter down to options whose owner is no longer present.</li>
<li>Sortable options table with individual columns for accessor, autoload, size, and last-read timestamp — no opaque composite score.</li>
<li>Quarantine mode with automatic expiry (restore / delete / keep) and a manifest table that flags options that are still being accessed.</li>
<li>No server-side backup: JSON exports are browser downloads (or explicit CLI <code>--output</code>), never written to disk on the server — so option_value content does not leak into <code>wp-content/</code> snapshots.</li>
<li>REST API under <code>/wp-json/orpharion/v1/*</code> (requires <code>manage_options</code>).</li>
<li>WP-CLI commands for scripted pipelines, including <code>--accessor-type</code> / <code>--inactive-only</code> filters on <code>list</code>, <code>export</code>, and <code>clean</code> (<code>clean</code> requires an explicit <code>--i-have-a-backup</code> acknowledgment).</li>
</ul>
<h3>License</h3>
This plugin is licensed under the GPL, version 2 or later.

Orpharion

Track which plugin or theme accesses each wp_options row, then quarantine or clean orphans.

Siby P Varkey

Is your WordPress website loading slowly? The culprit is often hidden in plain sight: a bloated <code>wp_options</code> table.
Every time a visitor opens any page on your site, WordPress automatically loads all “Autoload” data from your database. Over time, as you install and uninstall plugins, this table fills up with “orphaned” data—leftovers that are no longer needed but continue to slow down every single page load. This increases your Time to First Byte (TTFB) and negatively impacts your SEO rankings.
Autoload Cleaner & Analyser is a professional-grade diagnostic platform designed to help you visualize, analyze, and safely remove this hidden bloat. Unlike simple scripts that can be dangerous, our plugin uses a forensic approach to database health.
Using a crowdsourced signature database, the plugin identifies the “owner” of almost every option (plugins, themes, or WordPress core). This gives you the confidence to delete data belonging to plugins you removed years ago, without the risk of breaking your current site.
<h3>🚀 Key Features</h3>
<ul>
<li>Visual Command Center: Stop guessing. The dashboard provides an instant snapshot of your database health, highlighting your “Top 5 Memory Hogs” and calculating your total “Cleanup Potential.”</li>
<li>Smart Analysis Engine: Our engine automatically cross-references your options against 780+ known signatures. It categorizes rows as “Core,” “Active,” or “Orphaned” so you know exactly what you are looking at.</li>
<li>The “Transient Killer”: WordPress transients are temporary cache files. Many plugins fail to clean them up, leading to thousands of useless rows. Our one-click tool purges expired transients safely.</li>
<li>Forensic Trash System: Safety is our priority. Deleted items are moved to a custom “Trash” table first. You can Undo or Restore any option instantly if you realize it was still needed.</li>
<li>Global Bulk Actions: Select hundreds or thousands of rows at once. Toggle autoload status or move items to trash in seconds with our optimized bulk-processing logic.</li>
<li>Developer Console: A hidden powerhouse for advanced users. Inspect raw database values, manage the JSON signature file, and toggle “Deep Clean” mode for a thorough audit.</li>
</ul>
<h3>🛡️ Safety & Reliability Protocols</h3>
We believe a performance tool must be the safest plugin on your server: 
1. Trash-First Workflow: We never perform “hard deletes” on the first step. Data is always recoverable until you manually empty the trash. 
2. Core Protection: Essential WordPress system options are hard-coded as “Protected” and cannot be deleted by the plugin. 
3. Backup Integration: The system encourages best practices by detecting and alerting you to your backup status before performing major operations.
For a complete walkthrough, advanced tutorials, and detailed troubleshooting, please visit our <a href="https://www.zetozone.com/autoload-cleaner-docs.html" rel="nofollow ugc">Official Documentation</a>.

Autoload Cleaner & Analyser

Professional database analyzer. Detect hidden memory hogs, clean the wp_options table, and boost site performance safely.

Orpharion vs Autoload Cleaner & Analyser