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.

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>

ALTOS vs WP Rocket | Simple LoadCSS Preloader