WP Rocket coordinates a small set of moving parts to deliver performance. Page caches sit on disk under wp-content/cache/wp-rocket/, the preload queue lives in wp_wpr_rocket_cache, used CSS rows land in wp_wpr_rucss_used_css, and the prewarmup job for above-the-fold CSS writes to wp_wpr_above_the_fold. Each table carries a status, a last_accessed, and a job_id column. The default Settings screen exposes a Clear Cache button and a counter, which works for everyday operation and hides every interesting detail the moment something goes wrong on a large site.

SleekView Kanban reads the same WP Rocket tables the Settings screen aggregates. Pick a derived rocket_state field that buckets URLs by cache presence, preload queue membership, used CSS status, and last access time and every URL becomes a card grouped under Uncached, Preloading, Cached, or Stale. Card fronts can show the URL path, the cache size on disk, the last accessed timestamp, the used CSS status, and the prewarmup job state so a developer can spot bottlenecks without leaving the board.

Dragging a card between columns calls the WP Rocket helper API. A move from Stale back to Uncached purges the relevant cache files and re-queues the URL for the next preload run. A move from Preloading back to Uncached cancels the in-flight preload job cleanly. WP Rocket's own automatic purge keeps running on post edits, so a manual board action never collides with the plugin's normal cache invalidation flow.

WP Rocket is famously easy to set up and famously hard to inspect. The Settings screen surfaces a single Clear Cache button and a counter, which is enough for a healthy small site and a blunt instrument the moment a large site starts behaving strangely. Stuck preloads sit in the queue for days.

Stale cache files quietly accumulate until disk usage alerts fire. Used CSS jobs stall on a single URL and nobody notices until a customer reports an unstyled page. By the time the developer has reconciled the Settings screen, the diagnostics panel, and the file system on disk, the moment has already passed and the team is reaching for a global purge that wastes work.

A kanban view that reads and writes the same WP Rocket tables and helper methods as the Settings screen keeps every moving part visible. Uncached, Preloading, Cached, and Stale all live on one board. The team can act on individual URLs instead of guessing whether one more global purge will fix everything.