Asset CleanUp Lite earns its place by stacking small rules: unload a script on a single page, dequeue a stylesheet across a post type, or stop a handle where it is not used. The trouble is that those rules live in many places. Site-wide entries sit in wpassetcleanup_global_data, per-page exceptions go into _wpassetcleanup_load_exceptions postmeta, and explicit blocks live in _wpassetcleanup_no_load. The Lite admin lists each rule individually with no visual sense of which post type or handle carries the bulk of the cleanup.

SleekView Charts reads the same wpacu data as a normal source and renders it as cards. A Number KPI counts total active unload rules across the site, a Donut splits unloads by handle source so theme, plugin, and core entries appear at a glance, a Horizontal Bar ranks the post types that carry the most page-level exceptions, and a Gradient Area traces when the rules were added so a noisy cleanup sprint stands out at a look.

Asset CleanUp Lite keeps writing rules where it always has. Charts query the same postmeta keys and the same global option, and saved dashboards can be scoped per role so a performance lead reads the production view while a support agent reads only the per-post exceptions. No second store, no rebuilt registry.

Asset CleanUp Lite succeeds by collecting many small rules, which is also why those rules get hard to reason about over time. A site can hold thousands of per-page exceptions plus a global block list, and the Lite admin lists them individually with no visual sense of how the load looks across templates. The data needed to spot drift already exists in a single option key and a pair of postmeta keys that wpacu maintains carefully.

Visualising those keys as Number, Pie, Bar, and Area cards costs nothing on the writing side and reframes the same rules as a dashboard. The cadence of cleanup review shifts from a quarterly scramble to a daily glance, and the rules stay exactly where the Lite plugin put them.