Cache Enabler is intentionally small: it writes static HTML and gzip files under wp-content/cache/cache-enabler/ per host and per URL, and stores a handful of options under cache_enabler. The default admin is a single Settings page with an aggregate cache size figure and a Clear Cache button. There is no per-URL list, no filter by age and no sort by size.

SleekView reads the cache directory and the option row and turns every cached file into a row in a real table view. URL, size, age, gzip variant and the resolved post type become first-class columns with sort, filter and inline action. A maintenance engineer can scope the table to stale entries in one click, an agency lead can spot the templates producing oversized cached pages without SSH.

Cache Enabler keeps writing and serving cache files exactly as before, including the Apache and NGINX rewrites that bypass PHP. SleekView is read-only against the cache directory, so the front-end pipeline is unaffected.

Cache Enabler is deliberately small. It writes static files, serves them through Apache or NGINX rewrites and exposes a Clear Cache button. The simplicity is the point.

The trade-off is that the admin tells the operator almost nothing about what the cache contains, how big it is per template or how old each entry actually is. SleekView reads the same cache directory the plugin writes to and renders cached pages as rows with size, age, gzip variant and resolved post type. The plugin keeps doing the cache work it does well; SleekView gives the team a shared screen to read the result, scoped per role and embeddable on the frontend.