ALTOS speeds up the WordPress admin by giving you per-screen control over which active plugins are actually loaded. Most WordPress sites accumulate dozens of plugins over time, but only a few are needed on any given admin screen. Loading them all on every page wastes memory, time, and database queries.
ALTOS operates at the WordPress core level via the MU-plugins mechanism, intercepting the loading pipeline before WordPress fully initialises. It cleanly skips heavy code paths on screens where they aren’t needed — while preserving admin menus, dependency relationships, and safety guards.
Key features
<ul>
<li>Per-screen control — Set rules for each admin screen (Dashboard, Posts, Pages, Settings, WooCommerce, Custom Post Types, …).</li>
<li>Three states per rule — Enabled (always load), Disabled (never load), Defer (load after the main page).</li>
<li>Smart menu preservation — Admin menu entries stay accessible for blocked/deferred items via an automatic snapshot system.</li>
<li>Hierarchical rules — Global → group → screen, with intelligent inheritance.</li>
<li>Automatic mode with suggestions — Confidence-scored recommendations from real performance samples; you review and apply manually.</li>
<li>Dependency cascade detection — Catches dependent items when a parent is blocked.</li>
<li>Request-type optimisation — Separate rules for AJAX, REST API, WP-Cron, and WP-CLI.</li>
<li>Update Optimizer — Three strategies to reduce update-check overhead without breaking badge counts.</li>
<li>Per-plugin performance metrics — Real-time load time, DB queries, memory.</li>
<li>Developer tools — Admin drawer, admin-bar integration, REST endpoints, extensive filters/actions.</li>
<li>Built-in translations — Czech, Slovak, Polish, German, French, Spanish.</li>
</ul>
Typical impact
<ul>
<li>30–50 % faster admin pages.</li>
<li>20–40 fewer database queries per admin page.</li>
<li>1–5 MB less memory per blocked item.</li>
</ul>
Safety by default
<ul>
<li>Manual mode requires explicit rules — nothing is changed without your action.</li>
<li>Automatic mode only suggests — never applies on its own.</li>
<li>The loader protects itself from being blocked.</li>
<li>Page-builder bypass for Elementor, Bricks, Divi, Beaver Builder during active editing sessions.</li>
<li>Emergency recovery URL for one-click bypass if a misconfiguration breaks the admin.</li>
</ul>
<h3>External Services</h3>
This plugin does not contact any external services. It does not send analytics, telemetry, license checks, or any other network requests. All rules, samples, snapshots, and configuration are stored exclusively in your own WordPress database.
The “Update Optimizer” feature exclusively throttles the standard WordPress update-check HTTP requests to <code>api.wordpress.org</code> — it never adds new endpoints and never sends additional data.
<h3>Privacy</h3>
ALTOS stores all of its data in your own WordPress installation:
<ul>
<li>Rules and configuration are stored in the WordPress options table.</li>
<li>Performance sampling data is stored in a plugin-owned custom table (<code>{prefix}sapm_sampling_data</code>) with 30-day retention.</li>
<li>No personal data about visitors or administrators is collected.</li>
</ul>
The plugin does not transmit any data to external services and does not contact any external endpoints other than throttling WordPress’s existing <code>api.wordpress.org</code> update checks when the (opt-in) Update Optimizer is enabled.

ALTOS

Intelligent admin-side loading control — choose which plugins load on which admin screen, with automatic data-driven suggestions.

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.

ALTOS vs AssetPilot – Granular control over frontend assets