manifest / performance / w3tc-cache-insights
W3TC Cache Insights
A lightweight dashboard that shows what W3 Total Cache is actually caching — sizes, entry counts, backend stats, recent purges and a live flush feed — plus a safe cleanup for leftover _old files and an opt-in origin cache primer that keeps the page cache warm after purges. Reuses W3TC's own measurement code; no debug logging or Pro licence required.
by Robert Went · github.com/robwent/w3tc-cache-insights · website
★ 0stars
2release downloads
0forks
Install
The author publishes release zips, so WP-CLI can install straight from GitHub:
wp plugin install https://github.com/robwent/w3tc-cache-insights/releases/download/0.4.0/w3tc-cache-insights-0.4.0.zipDeclares an update source (https://github.com/robwent/w3tc-cache-insights), so updates arrive through the plugin's own updater.
From the readme
W3TC Cache Insights
A lightweight dashboard for W3 Total Cache that answers a simple question: what is actually being cached right now? It's an inspection tool at heart, with one safe maintenance action (clearing leftover old files) and, since 0.3.0, an opt-in cache primer that keeps the origin page cache warm (off by default — a fresh install still only observes).
It reuses W3TC's own measurement code rather than reinventing it, and is deliberately built to add zero overhead to normal page loads — everything is computed on demand from an admin screen and cached briefly.
No W3TC Pro licence and no debug logging required. Works on the free version.
What it shows
- Cache modules — page, database, object and minify cache: whether each is on, which engine it uses (Disk, Redis, Memcached, APCu…), and for disk engines the on-disk size and entry count.
- Cache directory — every sub-folder of wp-content/cache sized, including the housekeeping dirs the per-module view doesn't cover (tmp, log, config, fragment). Engine-agnostic; answers "what's actually in the cache folder".
- Page cache explorer — because the disk (Enhanced) page cache mirrors your URL structure on disk, it's browsabl
Read the full README on GitHub →