font-display:swap, and preloading local fonts, to prevent font loading from blocking rendering.async or defer if loaded.
The interface is user-friendly: for example, the screenshot below shows Contact Form 7’s CSS/JS with options to disable them.
In the page editor, Asset CleanUp adds a meta-box listing all loaded CSS/JS. Each asset (e.g. Contact Form 7 styles/scripts above) can be disabled on that page or site-wide, and attributes like async/defer applied.
The plugin’s Settings page (in WP-Admin under Asset CleanUp) has tabs for general preferences, CSS/JS Load Manager, Bulk Unloads, Tools, etc.
Here you choose whether to “Manage in Dashboard” (show the asset list in the editor) or “Manage in Front-end” (show it on the actual page for logged-in admins).
You can also enable Test Mode (so changes only affect admins) and set up file minification/combination rules. The screenshots below illustrate these UI sections.
Asset CleanUp’s settings dashboard includes toggles (e.g. to show asset lists in the editor vs front-end) and options like minification/combining of files. The “Plugin Usage Preferences” screen above sets how assets are retrieved and displayed.
Installation and basic setup are quick. The plugin is actively maintained (tested up to WP 6.7.2 as of 2025) and works on multisite. It’s suitable for any site owner who needs faster pages: beginners can use the intuitive checkboxes to trim assets, while developers can leverage the advanced rules (regex unloads, screen-size conditions, etc.).
The free version alone is powerful; the Pro upgrade is appealing mainly to agencies or power-users managing multiple pages/sites with complex needs.
<body>) to defer render-blocking CSS, which is an uncommon feature in most plugins. Overall, the Asset Manager in Pro is a powerful “script manager” rivaling those in paid plugins. The trade-off is complexity: beginners should use it carefully (perhaps with the built-in guidance and test mode), while developers will appreciate the fine-grained control.
async, and given font-display:swap so text is visible sooner. It can preload fonts.gstatic.com and preconnect to font domains to speed fetching. Local fonts can be added as <link rel=preload> and have font-display toggled. These font options are similar to what WP Rocket and other optimizers do, and they help CLS (layout shifts) as well.
ReferenceError: ElementorProFrontendConfig is not defined. This suggests that certain dynamic builders (Elementor, possibly others) may break if key scripts are unloaded. In such cases, the fix is to only unload safely (or use Test Mode to catch issues first). Generally, compatibility is good, but always test after major builder or PHP updates. (On that note, the plugin historically tested only up to PHP 7.3/7.4; most users now run PHP 8, so one should verify that any errors are resolved in the latest version.)
Regarding caching: Asset CleanUp complements caching plugins. WP Rocket’s docs explicitly note they are compatible – just clear Rocket’s cache after changing Asset CleanUp settings. In fact, the workflow is to use Asset CleanUp to disable assets, then let WP Rocket (or another cache) handle combining/minifying of the remaining files. You should avoid duplicating features (e.g. don’t minify with both Asset CleanUp and WP Rocket simultaneously). Similarly, LiteSpeed Cache users have warned that overlapping optimizations may conflict, so the rule is “don’t enable the same feature in both plugins”. In short, Asset CleanUp works fine with major caches (WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.), as long as you disable redundant settings on one side.
<body> (asynchronously),async/defer attributes to individual scripts,