WP Rocket writes static cache files under wp-content/cache/wp-rocket/ per host and per URL, and stores per-page data such as Used CSS and Critical CSS in wp_wpr_rocket_cache and the wpr_used_css tables. Preload progress lives in wp_wpr_rocket_preload with status flags (pending, in progress, completed, failed). The default WP Rocket admin shows all of this as toggle screens and global progress bars: there is no per-URL queue you can sort or filter when only some pages are misbehaving.

SleekView reads the WP Rocket tables and the matching post rows so you get a single workspace built around URLs. One row per URL can show its cache state, preload status, last cache refresh, Used CSS status, and the post type or template behind it. Sort by last refresh to find pages that have not been regenerated since a deploy, filter to Used CSS failed only, or group by post type to see which templates are responsible for the bulk of preload errors.

Because SleekView is read-only against the cache tables, WP Rocket keeps managing files and preload exactly as before. Inline actions go through WP Rocket's own functions when available (clear cache for a row, regenerate Used CSS) so the plugin remains the source of truth. Saved views like Failed preload last 24h or Pages without Used CSS can be scoped per role, useful for handing performance triage to a developer without giving them access to WP Rocket's settings.

WP Rocket succeeds by being mostly invisible. Toggle the right options, the cache fills, the preload runs, and the front end serves static files. The trouble starts when something quietly does not work: Used CSS fails on a few templates, preload stalls on a handful of URLs, or a deploy invalidates pages that never regenerate.

The default admin tells you the global percentage and surfaces the most recent issue, but it does not let you read the queue. Most teams find out about a stuck URL when a stakeholder reports a slow page, then dig through the file system or run SQL by hand to confirm the cache state. SleekView reframes WP Rocket's data as exactly what it already is: a list of URLs with attached metadata.

Cache state, preload progress, Used CSS results, and last refresh become columns instead of toggles. Failures sort to the top, regressions show as stale timestamps, and triage stops requiring root access to the server. The plugin keeps doing what it does best; SleekView just lets the team responsible for performance read the queue.