Sandipsinh Chauhan

DashClean is a modular WordPress admin optimization plugin built for developers, agencies, and site owners who need a cleaner, faster, and more professional wp-admin experience.
Version 2.0.0 introduces a service-layer architecture with administrator protection, schema-aware settings migration, runtime discovery caching, and scalable user targeting — designed for client deployments and large WordPress installations.
<h4>Core Capabilities</h4>
<ul>
<li>Menu Cleaner — Hide admin menu and submenu items by role or user.</li>
<li>Dashboard Widget Manager — Remove all or specific dashboard widgets.</li>
<li>Admin Bar Cleaner — Hide toolbar nodes for targeted users.</li>
<li>Notice Cleaner — Suppress admin notices while optionally keeping critical errors.</li>
<li>Performance Optimization Tools — Disable emojis, jQuery Migrate, header junk, and selectively dequeue frontend assets.</li>
<li>Role-Based Visibility Controls — Apply cleaning rules to selected roles.</li>
<li>User-Specific Targeting — Fine-tune restrictions to individual user accounts.</li>
<li>Preset Management System — Apply Client or Developer templates; save custom snapshots.</li>
<li>Import / Export Settings — Move configurations between sites with JSON backups.</li>
<li>Schema-Aware Settings Migration — Automatic compatibility for legacy export files.</li>
<li>Runtime Discovery Cache System — Reliable widget, admin bar, and asset inventories.</li>
<li>Safe Administrator Protection Layer — Users with <code>manage_options</code> are never restricted.</li>
<li>AJAX User Search & Scalability — Paginated user search for large sites (no bulk loading).</li>
<li>Multisite-Aware Cleanup Support — Uninstall removes data across network sites.</li>
<li>Translation Ready — Full text domain support with POT catalog included.</li>
</ul>
<h4>Why DashClean</h4>
Unlike heavy white-label plugins, DashClean uses a performance-first modular design. Optional modules load only when enabled. Settings are stored in a single option with schema versioning for safe upgrades.
Administrators always retain full access. Presets merge into existing configuration rather than wiping unrelated module settings.

DashClean

A WordPress admin optimization plugin. Clean the dashboard, control menus, optimize performance, and manage client experiences safely.

Joost de Valk

Ari Stathopoulos

Progress Planner

Filip Ilić

This plugin tracks which of the autoloaded options are used on a page, and stores that data at the end of page render. It keeps an array of options that it has seen as being used. On the admin page, it compares all the autoloaded options to the array of stored options, and shows the autoloaded options that have not been used as you were browsing the site. If you’ve been to every page on your site, or you’ve kept the plugin around for a week or so, this means that those options probably don’t need to be autoloaded.
<h3>How to use this plugin</h3>
Install this plugin, and go through your entire site. Best is to use it normally for a couple of days, or to visit every page on your site and in your admin manually. Then go to the plugin’s settings screen, and go through the unused options. You can either decide to remove an unused option (they might for instance be for plugins you no longer use), or to set it to not autoload. The latter action is much less destructive: it’ll still be there, but it just won’t be autoloaded.

AAA Option Optimizer

And I love the speed in which improvements are made :)

Great tool to minimize autoloaded data size


I wonder how on earth a plugin tha promises to optimize the wp_options tables, stores 25MB of data in the option_value !!!! Maybe the guy who developed it does not understand the fundamentals of the internal database optimizers but such a huge deviation, totally ruins MariaDBs/MySQL internal optimizer. You see optimizers work on the assumption that in a table, the fields have somewhat related sizes. For more details please go to MariaDB Jira and check for cases MDEV-34097 and MDEV 32663If you add records with huge sizes (say > 100k) in wp_options table where each option is usually less than 30Bytes, then you have an issue. In our case the issue was caused by the very plugin that we used to monitor our options (that are by and large incorrect). Avoid it at all costs.


A joke!!!

Plugin that tracks autoloaded options usage and allows the user to optimize them.

DashClean vs AAA Option Optimizer