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.

ensemblebd

<h3>Deprecated</h3>
This plugin is deprecated and will be removed in the future. 
It was coded back in 2019 when WpRocket did not have asynchronous support for CSS. 
Although this plugin operates at a lower level (main php buffer), which helps apply loadsCSS to ALL styles regardless of whether they conform to wp_enqueue or not, we recommend instead using WpRocket’s system: <a href="https://docs.wp-rocket.me/article/1266-load-css-asynchronously" rel="nofollow ugc">Load CSS Asynchronously</a>.
<h3>Description</h3>
Simple high performance plugin to enhance WP Rocket’s css output to use the loadCSS preload polyfill. 
This will ensure any css being loaded via the page output is deferred, and utilizing a preload [rel] attribute. 
Note: This will not affect admin pages. It’s designed only to process front-end pages.
It is recommended to enable the WP Rocket setting for “Optimize CSS”, which will provide your pages with inline Critical-CSS. 
That way an unstyled flash is not seen on page load (if properly configured of course).
This plugin will boost your <a href="https://developers.google.com/web/tools/lighthouse/" rel="nofollow ugc">Lighthouse</a> and <a href="https://developers.google.com/speed/pagespeed/insights/" rel="nofollow ugc">PageSpeed Insight</a> scores.
<h3>Plugin Mission</h3>
We hope that <a href="https://wp-rocket.me/" rel="nofollow ugc">WP Rocket</a> will implement this as a feature of their plugin. 
The existing <a href="https://docs.wp-rocket.me/article/1266-load-css-asynchronously" rel="nofollow ugc">Load CSS Asynchronously</a> only works for supported wp_enqueue styles, which not all plugins/themes properly utilize. 
For normal users, we recommend using WP Rocket’s system instead of this plugin.
<h3>Requirements:</h3>
<ul>
<li>If you intend for logged-in users to see the effect, you must enable WP-Rocket’s setting called “caching for Logged-In Users”</li>
<li>Alternatively, you can run the plugin without WP-Rocket, despite it’s intended purpose. (>^.^)></li>
</ul>
<h3>Features:</h3>
<ul>
<li><a href="https://github.com/filamentgroup/loadCSS/tree/v2.0.1" rel="nofollow ugc">FilamentGroup’s LoadCSS(v2.0.1)</a> inline injector 
(optional – see settings page next to WP Rocket), triggered via wp_head </li>
<li>High performance Regular Expression approach to process WP Rocket’s (php’s) output buffer, to replace stylesheets with the appropriate loadCSS syntax </li>
<li>Option to enable the buffer processor when you don’t have WP Rocket installed. 
** This will respect AMP pages, and Yoast Sitemap output (by not executing). No other considerations have been implemented. </li>
</ul>
No fluff. Just a robust loadCSS implementation.
You can see how it works, & measure the performance, with this(via repl.it): <a href="https://repl.it/@ensemblebd/WPRocketLoadCSSMeasurement" rel="nofollow ugc">Run the Plugin’s code</a> 
Just paste your own page’s url or html into the appropriate variable @ the top.
And you can test this plugin’s regex as well: <a href="https://regex101.com/r/xsugT7/1/" rel="nofollow ugc">WordPress.com html – links filtered by regex</a>
Github link is here: <a href="https://github.com/ensemblebd/wp-rocket-loadcss" rel="nofollow ugc">Click</a>
<h3>Last tested with:</h3>
<ul>
<li>WP Rocket 3.13.x</li>
<li>WordPress 6.2.x</li>
</ul>
<h3>Dependencies</h3>
<ul>
<li>WP Rocket (optional via settings) </li>
<li>file_get_contents() php function (if included loadCSS lib is used via options — default = yes)</li>
</ul>

AssetPilot – Granular control over frontend assets vs WP Rocket | Simple LoadCSS Preloader