Asset CleanUp lets an admin selectively stop specific CSS/JS files from loading on specific pages, plus basic minify and combine — all decided at render time. Whichever assets are actually left enabled for a given page is exactly what Static Shield's crawler captures as that page's final static output, the same as any other page. It has no page cache of its own, so there's no second caching layer to worry about.
Asset CleanUp's real payoff under Static Shield shifts from reducing per-request PHP/DB overhead — already eliminated once a page is static — to simply shipping less: whatever CSS/JS a page's rules leave disabled never makes it into that page's static output at all.
No single mode applies — Asset CleanUp doesn't influence which serving mode a site should use; see the notes below for what it actually does.
Whatever CSS/JS files are left enabled for a page — after Asset CleanUp's own per-page rules run — are captured into the static release exactly as they'd render live.
None — Asset CleanUp declares no public routes, AJAX actions, or REST endpoints of its own; its rule editor is an admin-only screen.
None needed — Asset CleanUp declares no public routes of its own.
No special setup — detected automatically once active, free or premium.
This hasn't been behaviorally validated against a live install — there's no test license available for the premium build, and the free build wasn't confirmed live in this environment, so confidence is capped lower than plugins tested directly. A misconfigured per-page rule (unloading a script or stylesheet a page actually needs) gets captured into the static build exactly as it would affect a normal dynamic page — not a risk Static Shield introduces, but worth a quick Shield Preview check on a few representative pages after setting up per-page rules.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp