boring Cache Check

boring Cache Check gives you a calm, practical view of the cache signals exposed by the current page. Before a check begins, the initial popup prominently states: “Checks this page’s URL, response headers, supported cache markers, WordPress login context, and local load timing. Processed locally and kept only for this browser session.” Open the extension, select “Check this page”, and the page reloads normally. The extension reads common HTTP response headers and reports one of six useful states: - HIT - MISS - BYPASS - DYNAMIC - UNKNOWN - ERROR You also get a confidence level, a short explanation, the detected cache layer, important cache values, HTTP status, local page-load timing, and a collapsible full response-header report. HIT, MISS, BYPASS, and other states use distinct colors while remaining fully labeled in text. Important values such as FastPixel, Varnish, X-Cacheable, cache age, and policy headers remain visible without opening the raw report. Some WordPress page caches do not expose a HIT response header. For WP Rocket, the extension can therefore recognize its local page-source cache footprint. A cached@ timestamp is treated as a detected cache result. WP Rocket metadata without that timestamp is shown as context only. FastPixel’s CDN/edge and local cache headers are interpreted as separate cache layers. If the outer FastPixel cache misses but its local cache hits, the extension reports the local hit and explains both values. For WordPress pages, a server-provided login or session skip reason is shown directly. If the response is otherwise unknown, a standard WordPress logged-in page marker is reported as a likely bypass. Explicit cache-result headers still take precedence. The extension does not read the user’s role or claim that the user is an administrator. The same normal reload provides a local “Page loaded” and TTFB snapshot. “Page structure ready” remains available in technical details. These are single local measurements, not a Lighthouse score or Time to Interactive. Choose “Copy summary” for the result, timing, and important values, or “Copy full report” for the complete visible response-header report. The result is intentionally conservative. Cache signals are hints, not guarantees. Missing signals do not prove that caching is disabled, and policy headers such as Cache-Control do not automatically prove a hit or miss. Everything runs locally in the browser: - No analytics - No telemetry - No tracking - No cloud service - No external API - No persistent URL history - No remote code Cookie and authentication response-header values are redacted before the temporary report is stored, displayed, or copied. The extension reloads only the page you explicitly ask it to check. It does not bypass, clear, warm, or modify the cache. Boring tools, because they simply work.