AssetPilot - Granular control over frontend assets

开发者	amrelarabi
更新时间	2026年6月5日 02:27
PHP版本:	8.1 及以上
WordPress版本:	7.0
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.0.0

详情介绍:

AssetPilot helps you speed up WordPress by controlling which scripts and styles load on which pages — without guessing handle names in functions.php. 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. Why AssetPilot instead of a simple “unload” plugin?

See before you change — scan a URL and browse assets with origin, size, and usage hints.
Rules, not one-off hacks — reusable conditions (page type, archive, WooCommerce views, device, auth, URL).
Bulk actions — one rule for many handles (e.g. a plugin’s scripts everywhere except checkout).
Safer changes — conflict checks, impact preview, optional verification, automatic runtime pause after repeated errors.
Stay in control — dependency graph, recommendations, debug logs, and Safe Mode.

What you can do

Disable scripts and styles you do not need on specific views
Defer or async JavaScript to reduce render-blocking work
Preload critical scripts, styles, fonts, and images
Set fetchpriority on images and preloads
Target by singular page, post type, archive, URL fragment, query string, device, login state, user role, WooCommerce page type, and scan URL
Create bulk rules from the asset list
Review optimization recommendations from scan data
Explore asset dependencies in a visual graph
Keep scan history and compare what changed over time

Typical use cases

Stop a plugin’s CSS/JS on pages where it is not used (blog posts, landing pages, archives)
Defer non-critical scripts on catalog pages while keeping checkout intact
Preload hero fonts or LCP images on key templates only
Audit what Elementor, WooCommerce, or form plugins actually enqueue before tightening rules

How it works

Open AssetPilot → Assets and scan a page (your homepage, a product page, a form page, etc.).
Pick an asset (or select several for a bulk rule).
Choose an action and conditions (where the rule applies).
Review validation and impact, then save.
Visit the front end — use Safe Mode anytime you need to disable all runtime rules instantly.

The block editor includes an AssetPilot sidebar on supported setups so you can jump from a post to asset management with context. Requirements

WordPress 6.2+
PHP 8.1+
Administrator access to configure rules

Frontend runtime changes apply to public site views, not the WordPress admin dashboard.

安装:

Install and activate AssetPilot from the Plugins screen (or upload the assetpilot folder to /wp-content/plugins/).
In the admin menu, open AssetPilot.
Go to Assets, enter a page URL, and run a scan.
Create your first rule from any row in the results table.

No command-line build is required for normal use on WordPress.org installs.

屏幕截图:

升级注意事项:

1.0.0 First public release. Scan a page, create a narrow rule, and test before applying site-wide conditions.

常见问题:

Will this break my site?

Any plugin that changes how assets load can break layouts or checkout if rules are too aggressive. AssetPilot reduces risk with validation messages, dependency information, Safe Mode, and automatic runtime pause after errors. Start with narrow conditions (one URL or one page type), test, then expand.

Will AssetPilot improve my PageSpeed or Core Web Vitals score?

It can help by removing or deferring assets that should not run on a given view. Results depend on your theme, hosting, caching, and which plugins enqueue heavy scripts. AssetPilot shows what is loaded so you can make informed cuts — it is not a full-page cache or image optimizer.

How is this different from “Asset CleanUp” or “unload” plugins?

Those tools focus on unloading assets per page. AssetPilot emphasizes conditional rules, bulk targeting, scan history, dependency graph, recommendations, validation, and verification workflows in one admin app — aimed at repeatable, auditable performance work.

Does it work with WooCommerce?

Yes. Conditions can target shop, product, cart, checkout, and account views so you can keep payment scripts where they are needed.

Does it work with Elementor and page builders?

Yes. Scan Elementor-built pages to see builder assets, then create rules with page-level conditions. Test carefully on editor and preview URLs; use Safe Mode if a template looks wrong.

Does it work with Contact Form 7 and other plugins?

Scan pages with and without the form (or feature). Disable or defer that plugin’s handles only on views where the shortcode or block is not present.

Does AssetPilot change the WordPress admin?

No. Rules target frontend delivery for visitors (subject to your conditions). Admin and block editor tooling are for configuration only.

Do I need to edit code?

No. Everything is configured in the AssetPilot admin UI. Developers can extend behavior via documented PHP hooks (see Development).

Where is the source code?

https://github.com/amrelarabi/assetpilot

更新日志: