SleekView for Breeze: page cache & minify rule tables
Breeze stores cache settings, minify rules, and Varnish integration data in the breeze_basic_settings and breeze_advanced_settings options. SleekView turns those scattered config blobs into a sortable cache health view.
♾️ Lifetime License available
See every cached URL and minify rule Breeze is enforcing
Breeze is the official Cloudways caching plugin and stores its configuration across breeze_basic_settings, breeze_advanced_settings, breeze_cdn_integration, and breeze_varnish_settings. Cached pages live on disk under wp-content/cache/breeze with one folder per host, and Varnish purge events flow through the Cloudways platform when the integration is enabled. The plugin's admin presents this as Basic, Advanced, Database, CDN, Varnish, and Heartbeat tabs. Reading which URLs hold a fresh cache file, which minify rules apply where, and whether a recent Varnish purge fired is a multi-screen exercise.
SleekView reads each setting group along with the on-disk cache directory and renders flat tables. Sort cached URLs by file age and size. Filter minify rules by handle to find the script that broke a page. Show Varnish purge events as a chronological feed so the question of whether the last deployment actually flushed the upstream cache stops being a guess.
SleekView never modifies Breeze's settings. Purge and refresh actions trigger Breeze's own functions and the plugin's hooks for Varnish integration where present. The on-disk cache continues to serve front-end visitors as before, and the Cloudways platform still owns the upstream Varnish layer. SleekView just exposes whatever Breeze has already recorded as flat, sortable rows the team can read at a glance.
Workflow
From Breeze tabs to a queryable cache dashboard
Connect the breeze_* surface
Build the cache state view
Layer in minify and Varnish
Purge inline
Sample columns
A typical Breeze cache state view
wp_options (breeze_*), breeze cache directory listing
| URL | Cache age | Size | Minify | Last hit | Status |
|---|---|---|---|---|---|
| / | 00:02:08 | 52 KB | JS+CSS | 8s ago | Hit |
| /shop/ | 00:00:20 | 78 KB | CSS | 3s ago | Hit |
| /account/ | n/a | n/a | off | n/a | Excluded |
| /blog/old-news/ | 08:14:40 | 112 KB | JS+CSS | 4h ago | Stale |
Comparison
Default Breeze admin vs SleekView
Default Breeze admin
- Settings spread across Basic, Advanced, Database, CDN, Varnish, and Heartbeat tabs
- No per-URL view of cache age, size, or last hit
- Minify rules and exclusions live in long textareas without filtering
- Varnish purge events are not surfaced inside WP Admin
- No saved view to hand a developer during a launch
SleekView
- Per-URL cache state with age, size, last hit, and minify scope
- Minify rules and exclusions filterable by handle or pattern
- Varnish purge events as a chronological feed inside WP Admin
- Cross-reference excluded URLs with the page that requested them
- Save launch views like 'Stale homepage and shop entries'
Features
What SleekView gives you for Breeze
Cache state per URL
See exactly which URLs hold a fresh Breeze cache file, which are excluded, and which are stale past their expiry. Skip the disk-totals summary and read the actual state at the URL level.
Minify rules at handle level
Every minify rule and exclusion becomes a row with handle, pattern, and current setting. Filter to the handles enqueued on the broken page rather than scrolling a single textarea.
Varnish events as a feed
Each Varnish purge becomes a row with timestamp and trigger. Confirm whether a deploy or post save actually flushed the upstream cache without opening the Cloudways console.
Audience
Who uses SleekView for Breeze
Cloudways developers
Audit per-URL cache state during launches and after major releases. Sort cached pages by age and size, spot the entries still served stale, and trigger a purge inline before customers notice.
Agencies managing client sites
Hand the support team a saved view of cache state plus recent Varnish events. They confirm a flush ran without needing access to the Cloudways platform or the Breeze settings tabs.
Developers debugging minify regressions
Filter the minify rules table to the handles loaded on the broken URL, then toggle the rule inline. The change writes through Breeze's own settings functions and the disk cache invalidates accordingly.
The bigger picture
Why a host-bundled cache plugin needs a query layer
Breeze ships free with Cloudways and runs on plenty of sites that never expected to need a deeper inspection layer. The plugin handles file-based caching, basic minification, and Varnish integration with sensible defaults, and the settings tabs reflect that pragmatic scope. The trade-off is that once a site grows past the homepage and a few cornerstone pages, the team starts asking questions Breeze's tabs were never designed to answer.
Which URLs are still serving fresh cache after the last deployment. Which minify rule is responsible for the broken script on a single product page. Whether the upstream Varnish layer actually purged when WordPress thought it did.
SleekView turns the breeze_* options and the on-disk cache directory into structured rows the team can sort and filter. The plugin keeps doing what it does, the Cloudways platform still owns Varnish, and the cache itself is unchanged. SleekView just gives the team eyes on what each layer is actually doing, in the shape they need to act on it.
Questions
Common questions about SleekView for Breeze
No. Breeze is a free plugin from Cloudways that runs on any host, and SleekView reads the breeze_* options regardless of where the site is hosted. Varnish-specific data only appears when the integration is enabled, which is most common on Cloudways stacks. The page cache and minify features are available on any host.
No. SleekView paginates the directory listing and only reads it when an admin opens the view. The on-disk page cache continues to serve front-end visitors through the existing rewrite path, and front-end scripts have no awareness of SleekView. There is no extra query path on the front end and no measurable load added to the cache layer.
Yes. Inline purge actions call Breeze's own delete functions for a single URL or a wildcard match. The plugin's own logging continues to apply, and any Varnish purge that Breeze normally triggers as part of a local purge runs as well, so a SleekView purge stays consistent with one done in the plugin's interface.
Yes. Breeze stores per-subsite options on multisite, and SleekView respects that boundary. Each subsite shows its own cache state, minify rules, and Varnish events, with the appropriate table prefix. Network admins can switch sites and each one renders its own data independently.
Yes. When the Varnish integration is active, Breeze logs purge events through its own functions, and SleekView surfaces those as a feed next to the local cache state. A single workspace shows the local file age and the upstream purge timestamp, which makes it easy to confirm both layers are aligned.
Breeze's Database tab triggers the same kind of cleanup tasks WP-Optimize offers. SleekView reads whatever results Breeze records from those runs, with task, table, rows removed, and saved space available as columns. The team can build a maintenance view that includes both cache and database activity in one grid.
Yes. Toggling a minify rule, excluding a URL, or triggering a purge from a SleekView row uses Breeze's own settings functions. The plugin remains the source of truth for cache configuration, and changes propagate to the breeze_* options exactly as if they had been made in the plugin's interface.
Yes. Any saved view exports to CSV with the active filters, sort order, and visible columns. Useful for sharing a cache state snapshot with a Cloudways support engineer, archiving a baseline before a major release, or comparing two snapshots before and after a configuration change.
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 checkout