maxpressy

Booster Sweeper helps you to optimize the Website speed further over the common caching and code minification plugins. <a href="https://maxpressy.com/booster-sweeper/asset-cleanup-wordpress-plugin-manager/?mtm_campaign=wpPluginPage&mtm_kwd=boostersweeper&mtm_placement=top" rel="nofollow ugc">Booster Sweeper</a> allows you to dequeue assets, i.e. unload the unused CSS or JavaScript files. These are the files that aren’t necessary for certain page.
You see, with the most of the WordPress plugins or even themes, most of the assets are loaded over the whole site, while usually you do not need those resources for certain pages. By unloading those files that aren’t necessary you are reducing the overall size of the page and at the same time decreasing the number of http requests. This results in a better performance for the pages and, even if other things are configured well, in a better SEO score for your site.
The most obvious using scenario would be when you have a contact form only on a Contact page. Another example is when you have an e-commerce plugin, e.g. Woocommerce, which loads its files over the whole site, while you may esencially need those files just on product pages. In both these cases, with Booster Sweeper you can stop these assets to appear on the pages that it’s not necessary to have them. Of course, you can imagine that you can do the same with other custom post types or plugins that are producing the same issue.
<h3>How Booster Sweeper can be of help?</h3>
<ul>
<li>Improve the site’s speed</li>
<li>Further get better SEO foundation</li>
<li>Bypass loosing customers due to the slow loading Website</li>
<li>By reducing the pages size, save in CDN costs</li>
</ul>
<h3>Booster Sweeper is simple to use</h3>
On each page or post of your WordPress site, from the sidebar settings, you’ll be able to notice a Booster Sweeper section. Here, our plugin is automatically detecting the assets that are loaded on the page. CSS and JS files are split in separate sections and when you select a file name, it will be prevented from loading on that page.
<h3>Go Premium</h3>
Premium Version of Booster Sweeper allows you to:
<ul>
<li>Dequeue assets for bulk pages, i.e. from the plugin global settings. Instead of doing it individually per page/post, you can select the pages and posts for which you wish certain CSS and JavaScript files that should be prevented from loading.</li>
<li>Disable the Booster Sweeper’s meta box section per post and page, so everything is managed from the global settings (bypass confusion)</li>
</ul>
But that’s not all, Pro version gives you ability to control the appearance of the assets based on many conditions:
<ul>
<li>Post types, e.g. Woocommerce’s products</li>
<li>Archives, i.e. categories, tags or even custom post types specific archive</li>
<li>Specific pages, like media files, search pages, 404</li>
<li>By RegEx</li>
</ul>
To go further, with Booster Sweeper Pro, you can also:
<ul>
<li>Manage the assets on the back-end side of the site. This may be specially important and beneficial for the membership sites</li>
</ul>
Visit <a href="https://maxpressy.com/booster-sweeper/asset-cleanup-wordpress-plugin-manager/?mtm_campaign=wpPluginPage&mtm_kwd=boostersweeper&mtm_placement=bottom" rel="nofollow ugc">Booster Sweeper Pro page</a> on our site to see all the benefits of the premium version.

Booster Sweeper: WordPress Asset Cleanup

Boost the Website speed by sweeping assets your pages do not need!

Amr Abdelkarem

AssetPilot helps you speed up WordPress by controlling which scripts and styles load on which pages — without guessing handle names in <code>functions.php</code>.
Scan a real page URL, see every enqueued asset (and many from the HTML), then create rules to disable, defer, async, preload, or set fetch priority — only where your conditions match (homepage, shop, mobile, logged-in users, specific URLs, and more).
Built for site owners who want measurable wins and for developers who want conditional dequeue with guardrails: validation warnings, dependency insight, scan history, and Safe Mode if something breaks.
<h4>Why AssetPilot instead of a simple “unload” plugin?</h4>
<ul>
<li>See before you change — scan a URL and browse assets with origin, size, and usage hints.</li>
<li>Rules, not one-off hacks — reusable conditions (page type, archive, WooCommerce views, device, auth, URL).</li>
<li>Bulk actions — one rule for many handles (e.g. a plugin’s scripts everywhere except checkout).</li>
<li>Safer changes — conflict checks, impact preview, optional verification, automatic runtime pause after repeated errors.</li>
<li>Stay in control — dependency graph, recommendations, debug logs, and Safe Mode.</li>
</ul>
<h4>What you can do</h4>
<ul>
<li>Disable scripts and styles you do not need on specific views</li>
<li>Defer or async JavaScript to reduce render-blocking work</li>
<li>Preload critical scripts, styles, fonts, and images</li>
<li>Set <code>fetchpriority</code> on images and preloads</li>
<li>Target by singular page, post type, archive, URL fragment, query string, device, login state, user role, WooCommerce page type, and scan URL</li>
<li>Create bulk rules from the asset list</li>
<li>Review optimization recommendations from scan data</li>
<li>Explore asset dependencies in a visual graph</li>
<li>Keep scan history and compare what changed over time</li>
</ul>
<h4>Typical use cases</h4>
<ul>
<li>Stop a plugin’s CSS/JS on pages where it is not used (blog posts, landing pages, archives)</li>
<li>Defer non-critical scripts on catalog pages while keeping checkout intact</li>
<li>Preload hero fonts or LCP images on key templates only</li>
<li>Audit what Elementor, WooCommerce, or form plugins actually enqueue before tightening rules</li>
</ul>
<h4>How it works</h4>
<ol>
<li>Open AssetPilot → Assets and scan a page (your homepage, a product page, a form page, etc.).</li>
<li>Pick an asset (or select several for a bulk rule).</li>
<li>Choose an action and conditions (where the rule applies).</li>
<li>Review validation and impact, then save.</li>
<li>Visit the front end — use Safe Mode anytime you need to disable all runtime rules instantly.</li>
</ol>
The block editor includes an AssetPilot sidebar on supported setups so you can jump from a post to asset management with context.
<h4>Requirements</h4>
<ul>
<li>WordPress 6.2+</li>
<li>PHP 8.1+</li>
<li>Administrator access to configure rules</li>
</ul>
Frontend runtime changes apply to public site views, not the WordPress admin dashboard.
<h3>Getting started</h3>
First rule in a few minutes
<ol>
<li>Assets → enter your site homepage URL → scan.</li>
<li>Find a script or style from a plugin you suspect is unnecessary on the homepage.</li>
<li>Click to create a rule → choose Disable (or Defer for scripts).</li>
<li>Set a condition such as “this scan URL only” or “non-WooCommerce pages” if you are testing carefully.</li>
<li>Save, open the homepage in a private window, and confirm the site still works.</li>
</ol>
Use Recommendations after a few scans for ideas (duplicate libraries, large files, low usage patterns).
Create Rule is opened from assets or recommendations — it is the guided wizard for actions, conditions, validation, and review.
<h3>Safe Mode</h3>
If the site looks wrong after applying rules, enable Safe Mode while logged in as an administrator:
<pre><code>/wp-admin/?assetpilot-safe-mode=1
</code></pre>
Safe Mode turns off all frontend runtime rule changes for the whole site. The admin UI, REST API, scanning, and rule editing still work. Clear any page cache after enabling if changes seem to stick.
If repeated frontend fatals occur, AssetPilot pauses runtime rules for 30 minutes automatically. Resume early from Settings or:
<pre><code>/wp-admin/admin.php?page=assetpilot-settings&assetpilot-resume-runtime=1<h3>Development</h3>
</code></pre>
Source repository: https://github.com/amrelarabi/assetpilot
Human-readable UI source is in <code>assets/src/</code>. Production bundles in <code>assets/build/</code> are built with <a href="https://www.npmjs.com/package/@wordpress/scripts" rel="nofollow ugc">@wordpress/scripts</a>.
Build (contributors only):
<ol>
<li><code>npm install</code></li>
<li><code>npm run build</code></li>
</ol>
PHP lives under <code>includes/</code> (Composer PSR-4, <code>AssetControl\</code> namespace).
Third-party frontend libraries: <code>@xyflow/react</code> (dependency graph), <code>react-select</code> (rule builder fields).
Extension hooks: <code>assetpilot_rest_register</code>, <code>assetpilot_admin_localize</code>, <code>assetpilot_admin_menu_pages</code>, <code>assetpilot_scan_saved</code>, <code>assetpilot_condition_handlers</code>, <code>assetpilot_site_key_scan_urls</code>, <code>assetpilot_site_key_scan_max_urls</code>, <code>assetpilot_key_pages_scan_complete</code>

AssetPilot – Granular control over frontend assets

Conditionally disable, defer, and preload scripts and styles — with page scans, safety checks, and Safe Mode.

Booster Sweeper: WordPress Asset Cleanup vs AssetPilot – Granular control over frontend assets