SleekView for Swift Performance Pro Cache: per-URL cache tables
Swift Performance Pro Cache tracks per-URL cache state and warmup activity through its own option keys and cache files. SleekView turns those scattered records into one workspace for triaging stale and uncached URLs.
♾️ Lifetime License available
See every Swift Performance Pro Cache URL in one queue
Swift Performance Pro Cache writes per-URL state to wp_options keys prefixed with swift_performance_ and stores generated assets under wp-content/cache/swift-performance/. The warmup engine queues jobs and tracks their status in option transients and an internal warmup table created on first install. Exclusions live in swift_performance_settings alongside CDN, lazy load, and database tweak toggles.
The default Swift Performance Pro Cache admin reports global counters and progress bars. There is no per-URL list you can sort by warmup status or filter by post type when only some pages fail. Operators end up tailing the cache directory listing or guessing from front end testing. The plugin's value (one URL per cache row) sits behind a UI that aggregates everything.
SleekView reads the cache directory index plus the relevant options and presents one row per URL. Columns can include cache state, warmup status, post type, last cache time, and the responsible template. Inline actions route through Swift Performance Pro Cache's own functions where they exist, so single URL clears use the plugin's APIs rather than direct deletes. Saved views like Uncached pages or Warmup failed can be scoped per role.
Workflow
How to build a Swift Performance Pro Cache view
Pick the source
swift_performance_settings for exclusions and to wp_posts for titles and types.
Compose columns
Save and scope
Edit inline or bulk
Sample columns
A typical Swift Performance Pro Cache view
swift_performance_settings.
wp_options (swift_performance_*) + wp-content/cache/swift-performance/ directory index
| URL | Cache | Warmup | Post type | Size | Last cache |
|---|---|---|---|---|---|
| / | Cached | Done | page | 128 KB | 5m ago |
| /about/ | Cached | Pending | page | 96 KB | 1h ago |
| /blog/post-a/ | Stale | Pending | post | 180 KB | 3d ago |
| /shop/widget-a/ | Missing | Failed | product | 0 KB | Never |
Comparison
Default Swift Performance Pro Cache admin vs SleekView
Default Swift Performance Pro Cache admin
- No per-URL list. The dashboard reports aggregate counters with no drilldown to missing or stale URLs.
- Warmup queue progress is global. Per-URL failure reasons in the warmup table are not exposed.
-
Exclusion rules in
swift_performance_settingsare buried in a long settings screen with no list view. - Cache clearing is per post or sitewide. No way to bulk clear a filtered subset like blog posts older than 7 days.
- Configuration sits behind one capability. Delegating cache triage requires manage_options in full.
SleekView
- One row per URL joining the cache directory index with the warmup status from option transients.
- Filter by failure: scope to rows where warmup status equals failed for fast triage.
- Inline clear calls Swift Performance Pro Cache's clear function for a single row, no sitewide purge required.
- Saved views per role: a developer can own a Missing cache view without holding license keys.
- Bulk warmup retry across a filtered subset, e.g. all posts of one template touched recently.
Features
What SleekView gives you for Swift Performance Pro Cache
Cache and warmup filters together
Stack filters on cache state and warmup status to find URLs cached but stuck in warmup, or missing but queued.
Kanban by warmup status
Switch the same data to a board grouped by warmup status to read the queue progress at a glance.
Bulk retry without sitewide purge
Select a filtered set of failed warmups and rerun the warmup function per row using Swift Performance Pro Cache's APIs.
Audience
Who uses SleekView for Swift Performance Pro Cache
Performance developers
They live in a Missing cache view filtered to high traffic post types, fix the offending templates, and trigger targeted warmup.
Support engineers
When a customer reports a stale page, they search by URL, confirm the cache timestamp, and clear that single row inline.
SRE owners
They watch a saved view of warmup failures last 24h grouped by template to spot regressions before a release lands.
The bigger picture
Why a Swift Performance Pro Cache queue view matters
Swift Performance Pro Cache scales the rendering layer the way every full page cache plugin does: each URL becomes a static file served before WordPress boots. The operational layer was never built for visibility at scale. Once a site has tens of thousands of URLs, the global counters tell you almost nothing useful about which pages are actually missing or stale.
Performance teams end up reading the cache directory by hand or running ad hoc SQL against option transients just to answer simple questions. That work belongs in a queryable view, not a terminal. SleekView reads the cache directory and the relevant option keys, presents one row per URL, and lets the responsible humans triage at the same level the plugin operates.
The plugin keeps owning runtime behaviour; SleekView just makes the state legible.
Questions
Common questions about SleekView for Swift Performance Pro Cache
No. The plugin keeps owning configuration, warmup schedules, and cache generation. SleekView reads its state and offers row level actions through its existing functions.
It reads the cache directory under wp-content/cache/swift-performance/ and matches files to URLs and post ids from wp_posts.
No. Cache contents are generated by Swift Performance Pro Cache. SleekView triggers clear or warmup actions but does not edit cached HTML directly.
Views read a paginated directory listing and join to indexed tables. The work happens in WP Admin only and does not touch the front end serving path.
Yes. A companion view reads swift_performance_settings and lists exclusions as labelled rows with applicable post types.
Yes. Select a filtered subset of URLs and the bulk action runs the same clear function the plugin uses per row.
Yes. Each blog id has its own cache directory and options. Views can pin to one blog id or aggregate across the network.
Local cache and warmup are covered. Third party CDN edge metrics are not pulled, though local CDN configuration in swift_performance_settings appears as rows.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkoutBrowse more
- Flexible Shipping
- Woocommerce Stock Sync
- Paystack Woocommerce
- Woocommerce Shipping Multiple Addresses
- Yith Woocommerce Wishlist
- Edd Stripe Pro
- Woocommerce Attribute Swatches
- Shopify Importer
- Variation Swatches
- Advanced Coupons
- Woocommerce Quick Order
- Wcam Marketplace
- Woocommerce Vendor Payouts
- Site Reviews
- Woocommerce Cheque Payment Pro
- Restrict User Access Pro
- Woocommerce Paid Courses
- Memberpress Buddypress
- Membershipworks
- Wishlist Member
- Lifterlms Pro Membership
- Membership Pro Paypal
- Subscriptio
- Memberpress
- Profile Magic
- Groups Paid Membership
- Indeed Ultimate Member
- Memberpress Corporate Pro
- Paid Membership Pro Pro
- Restrict Content