✨ 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 for WP Rocket Pro: per-URL cache & preload queues as tables

WP Rocket Pro tracks cache files, preload jobs, and Used CSS generation across its own custom tables. SleekView turns that scattered queue data into one workspace where you can sort by failure, filter by post type, and triage stale URLs.

♾️ Lifetime License available

SleekView table view for WP Rocket Pro

Stop guessing which URLs WP Rocket Pro still has not preloaded

WP Rocket Pro keeps its per-URL state in three custom tables. Cache rows live in wp_wpr_rocket_cache, preload jobs queue up in wp_wpr_rocket_preload with status flags like pending, in-progress, completed, and failed, and Used CSS bodies live in wp_wpr_used_css. The native admin reports global counters and progress bars, but there is no per-URL list you can sort, filter, or scope by post type when only some pages misbehave.

SleekView reads those tables and joins them to wp_posts so one row represents one URL. Columns can include cache state, preload status, Used CSS status, last refresh time, post type, and the responsible template. Sort by last refresh to find pages stale since a deploy, filter to Used CSS failed, or group by post type to expose which templates account for most preload errors.

Inline actions route through WP Rocket Pro's own functions where they exist, so clearing a single URL's cache or rebuilding its Used CSS uses the plugin's APIs rather than direct DELETEs. Saved views like Preload failed last 24h or Pages without Used CSS can be scoped per role, useful when performance triage is delegated to a developer without granting full WP Rocket settings access.

Workflow

How to build a WP Rocket Pro view in SleekView

1

Pick the source

Choose wp_wpr_rocket_cache as the base table and join wp_wpr_rocket_preload and wp_wpr_used_css on URL or post id.
2

Compose columns

Add cache status, preload status, Used CSS status, post type, and last_modified. Convert raw status strings to coloured spans.
3

Save and scope

Save Failed preload last 24h and Pages without Used CSS as views, then scope each view to the performance role.
4

Edit inline or bulk

Add row actions for clear cache and regenerate Used CSS. Bulk select a filtered subset and run the same action across all selected rows.

Sample columns

A typical WP Rocket Pro cache and preload view

Per-URL rows joining wp_wpr_rocket_cache, wp_wpr_rocket_preload, and wp_wpr_used_css.
Source: wp_wpr_rocket_cache + wp_wpr_rocket_preload + wp_wpr_used_css
URL Cache Preload Used CSS Post type Last refresh
/ Cached Completed OK page 8m ago
/pricing/ Cached In progress Pending page 1h ago
/blog/case-study/ Stale Pending Failed post 2d ago
/shop/widget-a/ Missing Failed Failed product 5d ago

Comparison

Default WP Rocket Pro admin vs SleekView

Default WP Rocket Pro admin

  • No per-URL list. The dashboard reports a global preload progress bar with no way to drill into which URLs are pending or failed.
  • Used CSS errors surface only as a banner. There is no sortable view over wp_wpr_used_css rows showing which posts failed generation.
  • Cache clearing happens by post or by all, with no way to bulk clear a filtered subset like all posts of one type updated in the last 24h.
  • Preload status from wp_wpr_rocket_preload is not exposed as a queue. Operators cannot see job order, age, or per-URL retries.
  • Configuration is locked behind the full WP Rocket settings screen, so delegating cache triage requires manage_options.

SleekView

  • One URL per row joining wp_wpr_rocket_cache, wp_wpr_rocket_preload, and post data, so cache, preload, and Used CSS state read together.
  • Filter by failure: scope to rows where status=failed in preload or Used CSS to find triage targets without scanning logs.
  • Inline clear calls rocket_clean_post() for a single row instead of forcing a sitewide purge.
  • Saved views per role let a developer own a Stale pages view without granting access to license keys or global toggles.
  • Bulk regenerate Used CSS over a filtered set, e.g. all posts of one template touched since a deploy.

Features

What SleekView gives you for WP Rocket Pro

Cache and preload filters together

Stack filters on wp_wpr_rocket_cache.status and wp_wpr_rocket_preload.status so one query returns URLs that are cached but failed preload, or missing but queued.

Kanban by preload status

Switch the same view to columns of pending, in-progress, completed, and failed to read the queue as a board.

Bulk clear without sitewide purge

Select a filtered subset and call rocket_clean_post() per row, keeping the rest of the cache warm.

Audience

Who uses SleekView for WP Rocket Pro

Performance developers

They live in a Used CSS failed view filtered to high-traffic post types, fix the offending templates, and bulk regenerate from there.

Support engineers

When a customer reports a stale page, they search by URL in the cache table, confirm the wp_wpr_rocket_cache.last_modified timestamp, and clear that single row.

Site reliability owners

They watch a saved view of preload failures in the last 24h grouped by post type to spot template regressions early.

The bigger picture

Why a WP Rocket Pro queue view matters at scale

WP Rocket Pro scales well at the rendering layer because every cached URL becomes a static file served before WordPress boots. The operational layer, however, was designed for one site owner clicking through a settings page. Once a site has tens of thousands of URLs across products, posts, and taxonomies, the global counters in the dashboard no longer help anyone find the URLs that actually failed.

Performance teams end up tailing logs or running ad hoc SQL just to answer questions like which templates fail Used CSS most often. That work belongs in a queryable view, not a terminal. SleekView turns the existing wp_wpr_rocket tables into a queue you can sort and filter the same way you would treat orders or form entries.

It does not replace WP Rocket Pro, it just makes the data the plugin already keeps legible to the humans responsible for keeping the cache healthy.

Questions

Common questions about SleekView for WP Rocket Pro

No. WP Rocket Pro continues to own configuration, cache clearing schedules, and preload triggers. SleekView only reads its tables and calls its existing functions for row level actions.

 

Primarily wp_wpr_rocket_cache, wp_wpr_rocket_preload, and wp_wpr_used_css, joined to wp_posts for human readable context like post title and type.

 

No. Cache contents and Used CSS bodies are generated by WP Rocket Pro itself. SleekView triggers regenerate or clear actions but does not edit the cached HTML or CSS directly.

 

Views run paginated SQL with indexes on the WP Rocket Pro tables, and saved views can carry a default filter so the first load is always scoped. Row counts in the hundreds of thousands stay snappy.

 

Yes. Bulk actions can route through WP Rocket's own REST endpoints when available, otherwise they call the same PHP functions the plugin uses internally.

 

Yes. Any post meta WP Rocket Pro writes (such as _rocket_exclude_lazyload or _rocket_exclude_async_js) can be added as a column or filter.

 

Queries are paginated and indexed. SleekView reads the same tables WP Rocket already reads on the front end. No write amplification occurs for read only views.

 

It covers what WP Rocket Pro stores locally. RocketCDN status flags written to wp_options appear as a column, but CDN edge metrics are not pulled from third party APIs.

 

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