Active cache plugins
Detects common WordPress page-cache plugins and warns when more than one is active.
Free WordPress Plugin
WPColt Cache Inspector
A safe diagnostic plugin that explains why a WordPress site is slow, stale, bypassing cache, or serving the wrong content from the wrong layer.
No setting changes
No cache purges
No frontend payload
Sample Scan
62%
Confidence score
Caching works at the edge, but the origin stack needs cleanup.
Two page cachesWP Rocket and LiteSpeed Cache active
CONFLICTCloudflare HTMLCF-Cache-Status: BYPASS
BYPASSObject cacheRedis drop-in installed but not connected
BROKEN
First recommendation
Disable one page-cache plugin before changing Cloudflare rules.
HITSecond request cached
MISSOrigin generated HTML
StackPlugin -> Server -> CDN
CF headerCF-Cache-Status: BYPASS
01 / Scope
What the first version checks.
Version one is deliberately narrow, safe, and useful. It reads signals, compares requests, and reports probable causes.
Server and proxy cache
Looks for Varnish, Nginx FastCGI cache, LiteSpeed, Cloudflare, and similar proxy layers.
Redis or Memcached
Checks whether object caching is actually connected instead of just installed.
Two public requests
Tests the homepage and one post twice as a logged-out visitor to compare cache behavior.
Header interpretation
Reads Age, X-Cache, X-Varnish, CF-Cache-Status, Cache-Control, cookies, and related headers.
Commerce safety checks
Flags account, cart, and checkout pages that appear cacheable when they should not be.
02 / Report
Designed for the fix, not the flex.
A raw header table is useful evidence, but it is not a plan. WPColt turns the evidence into a practical order of operations.
Working
Static assets are cached correctly by Cloudflare and return increasing Age values.
Broken
HTML requests are bypassing cache because a plugin sets a unique visitor cookie.
Fix first
Remove the cookie from anonymous page views, then retest the homepage before touching TTLs.
Verify
Second logged-out request should return HIT from at least one page-cache layer.
03 / Conflicts
The problems it is built to catch.
These are the cache mistakes that make agencies lose hours and site owners lose trust.
Two page-cache plugins fighting over headers and purge behavior.
Cloudflare caching HTML incorrectly or bypassing it on every visit.
Stale pages after updates because purge and cache lifetime settings disagree.
WooCommerce private pages accidentally being treated as public cacheable pages.
Analytics, membership, or consent cookies preventing normal page caching.
Object cache installed, advertised, or dropped in, but not connected cleanly.
04 / Next
Read Documentation
The next cache mystery should not take an afternoon.
Use the documentation and sample report to see exactly how WPColt turns cache symptoms into a fix order you can trust.