Asset CleanUp lets editors and developers unload CSS and JS assets globally and per-page. Per-page rules live in _wpacu_no_load_* postmeta keys on each post, global rules and settings live in the wpacu_settings option. The plugin's admin shows a per-page checklist of detected assets plus a global rule editor, but it does not provide a site-wide list of every rule with the asset handle, the source plugin and the scope.

SleekView reads the postmeta keys and the wpacu_settings option as flat rows and renders the data as a real table view. Asset handle, source plugin, asset type, scope (per-page or global), target page and last edit become first-class columns with sort, filter and inline action. An engineer can scope the table to one source plugin in a click, an editor can audit unloads on the pages they own.

Asset CleanUp continues to control which assets actually load on the front-end. SleekView is read-only against the postmeta and options, so the unload behavior stays authoritative.

Asset CleanUp solves a real problem: WordPress plugins enqueue assets on every page by default, and a serious performance practice means turning that off per-page or globally. The plugin's admin is excellent at the per-page step, but it leaves the site-wide questions unanswered: how many rules exist in total, which plugins contribute the most asset bloat, which editors have been active. SleekView reads the wpacu postmeta and the wpacu_settings option and renders every rule as a row with handle, source and scope columns.

The plugin keeps controlling what loads on the front-end; SleekView gives the team a shared screen to audit the rule set, scoped per role and embeddable on the frontend.