✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for Asset CleanUp

SleekView Kanban reads Asset CleanUp per-page rules from the WordPress post meta, groups CSS and JS handles into lanes like loaded, unloaded, deferred, and async, and lets your team drag handles between lanes to flip load behavior without leaving wp-admin.

♾️ Lifetime License available

SleekView Kanban board for Asset CleanUp

Why Asset CleanUp rules fit a kanban

Asset CleanUp is the WordPress plugin for per-page CSS and JS asset control. For each page, it stores rules in post meta under the _assetcleanup_rules key with the handle names of every script and style WordPress enqueues, plus a state per handle that swings between loaded, unloaded, deferred, async, and conditionally loaded depending on what the site owner has decided for that specific page.

The default Asset CleanUp admin shows these rules as a long checklist of handles per page, which works for a one-page tweak but breaks down once a site has dozens of pages with custom asset rules and a performance lead needs to audit the rules across the whole site. SleekView Kanban reads the same per-page rules and groups handles by the state field, which is the natural pipeline lane for an asset load audit. Each card surfaces the handle name, the originating plugin, the file size, and the affected page.

Dragging a card from loaded to unloaded writes the new state back to the Asset CleanUp rule for that handle on that page, so the next request stops enqueuing the script or style. Bulk drags can unload a curated set of handles in one transaction after a performance audit, which is exactly how a performance lead wants to ship a Core Web Vitals improvement instead of clicking through a checklist.

Workflow

From asset checklist to per-page board

1

Point at Asset CleanUp

Install SleekView next to Asset CleanUp. Pick the per-page rules in post meta as the source. SleekView reads every handle, every plugin source, every state, and every page rule that the plugin admin already exposes.
2

Pick load state as the lane

Set the group-by field to the asset state column. SleekView reads every value Asset CleanUp uses, including loaded, unloaded, deferred, and async, and renders each as a lane with a live count and color per state.
3

Choose card fields

Pick which handle fields appear on each card. Most performance leads pick handle name, originating plugin, file size in KB, and the affected page URL. Full handle dependencies open in a side panel below.
4

Enable rule flip drops

Flip the drag-and-drop switch and SleekView writes the new asset state to the Asset CleanUp rule on drop. Capabilities decide who can unload handles, so juniors flip staging rules while seniors flip production rules.

Sample board

Sample Asset CleanUp per-page board

A live SleekView Kanban grouping Asset CleanUp handles by load state, with cards showing handle name, originating plugin, file size in kilobytes, and the affected page URL.
Loaded
1240
wc-cart-fragments handle for cart updates
plugin wc, size 4KB JS file
jquery-core handle WordPress ships by core
plugin core, size 28KB
wp-emoji-release handle for emoji rendering
plugin core, size 12KB
Unloaded
284
gutenberg-styles handle stripped on landing
plugin core, on /landing
contact-form-7 styles stripped on home page
plugin cf7, on / home
wp-embed handle stripped on blog index page
plugin core, on /blog
Deferred
92
recaptcha handle deferred on contact page
plugin grecaptcha, defer
analytics handle deferred on landing pages
plugin ga, defer attribute
chatbot handle deferred across the home page
plugin chat, defer attr
Async
47
optimizely handle marked async for fast load
plugin opt, async attr
hotjar handle marked async for fast page load
plugin hj, async attr
fonts handle marked async for swap rendering
plugin font, async attr

Comparison

Default checklist vs SleekView Kanban

Default asset checklist

  • Long per-page checklist of handles ordered alphabetically with no state grouping
  • No instant view of how many handles are unloaded versus deferred across the site
  • Bulk flipping handles across many pages means clicking each checkbox separately
  • No audit trail of who flipped which handle on which page during a perf audit
  • Mobile admin view shows the same dense checklist that desktop performance leads see

SleekView Kanban

  • Groups Asset CleanUp handles by the asset state field with live counts per lane
  • Drag from loaded to unloaded to update the Asset CleanUp rule on the affected page
  • Card fronts show handle name, originating plugin, file size, and affected page URL
  • Async and deferred handles sit in their own lanes separated from loaded handles
  • Capability gates restrict production rule flips to senior performance lead roles

Features

What SleekView Kanban gives you for Asset CleanUp

Audit assets by state

Asset CleanUp ships a per-page checklist of handles, but the default admin orders them alphabetically with no state grouping. The kanban flips that and groups by load state, so a perf lead spots unloaded and deferred at a glance.

Flip rules in bulk

After a Core Web Vitals audit, select every row in the loaded lane filtered to a slow third-party script and drag to deferred or unloaded in one move. The rule updates for every selected page in one database transaction.

Filter by plugin or page

A filter bar narrows lanes by plugin, page URL pattern, file size, or handle name. Saved filters are per-user, so a perf lead chasing third-party scripts keeps a focused board while another watches WordPress core handles.

Audience

Three teams using the Asset CleanUp kanban

Performance engineers

Performance engineers run a Core Web Vitals audit, identify slow third-party scripts, and drag those handles into deferred or unloaded across every affected page from one board.

Front-end developers

Front-end developers filter the board to the pages they own, confirm Asset CleanUp is unloading legacy plugin handles correctly, and ship a perf fix without clicking the checklist.

Theme builders shipping

Theme builders use the kanban to audit how their theme styles interact with other plugin handles across the whole site and to flip rules cleanly between staging and production.

The bigger picture

Why a kanban beats a checklist for assets

Asset performance is a per-page problem. Asset CleanUp gives WordPress site owners full per-page control over which CSS and JS handles load, defer, or unload entirely. The default admin presents that control as a long per-page checklist ordered alphabetically by handle name, which works for tweaking a single page but breaks down once a site has dozens of pages with custom rules and a performance lead has to audit Core Web Vitals across the whole site.

A kanban board fixes that shape. Lanes give performance leads an instant count of handles in loaded, unloaded, deferred, and async across the whole site, drag-and-drop turns a rule flip into a single gesture that updates the Asset CleanUp rule on the affected page, and filters let each lead scope the board to the handles or pages they actually own. The same per-page rules power a different mental model that matches how performance teams really audit assets across a busy WordPress site.

Questions

Common questions about SleekView Kanban for Asset CleanUp

Both versions of Asset CleanUp store per-page rules in the same post meta key, and SleekView reads that key directly. The kanban renders the same way regardless of which version you run, and Pro adds more rule types like load by user role that show up as additional lanes on the board.

 

Yes. The drag handler writes the new state to the Asset CleanUp rule in post meta for the affected page. On the next request, Asset CleanUp reads the rule and skips the enqueue for that handle, which means the script or style stops appearing in the rendered HTML for that page.

 

Yes. Asset CleanUp rules are simple per-handle state flags, so dragging the card from unloaded back to loaded restores the original enqueue behavior. No script or style is permanently removed, and the WordPress core enqueue is restored to its default state for that page request.

 

Yes. SleekView views are configuration only, so you can build one board filtered to landing pages and another to blog pages from the same Asset CleanUp rule set. Each lead picks a default board, and admins pin shared boards into the sidebar for the whole performance team.

 

SleekView reads the rule set on every page load, so a new handle from a freshly installed plugin shows up automatically as a card in the loaded lane with no rule applied yet. You can drag it into unloaded, deferred, or async to apply the rule immediately across pages.

 

Each handle card opens a side panel showing the handle name, the originating plugin, the file path, the file size, the dependencies the handle requires, and the page URL. Performance leads audit dependencies without leaving the kanban for the Asset CleanUp admin checklist.

 

Yes. SleekView respects WordPress capabilities, so you can require a senior performance lead capability before a card lands in the unloaded lane for production-tagged pages. Juniors can flip staging rules freely, but only seniors flip production rules with full audit.

 

SleekView reads and writes the existing Asset CleanUp rule post meta without adding shadow tables for asset rules. View configuration sits in its own small options row, so uninstalling SleekView leaves every per-page asset rule exactly where Asset CleanUp wrote it.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView