Start from the active tab.
The extension uses temporary access after you open it and choose to check the current HTTP or HTTPS page.
Chrome and Brave add-on
boring Cache Check
Check page caching from your browser. Local, temporary, no tracking.
A small Chrome and Brave extension that reads visible cache response headers, supported cache markers, WordPress login context, and local load timing for the page you explicitly choose to check.
A quick cache check for the page in front of you.
Open the extension, choose Check this page, and let the page reload normally. The result is a conservative interpretation of visible cache signals, not a promise that every cache layer is perfectly configured.
How it works
One page. One reload. One readable result.
boring Cache Check observes the next main-frame response for the active tab after you start a check. It does not continuously monitor your browsing and it does not modify requests.
Reload normally.
The page reloads without cache-busting query parameters, forced empty-cache reloads, cache clearing, or warmup behavior.
Read visible signals.
Common cache headers, supported local cache footprints, bypass context, HTTP status, and local timing are turned into one result.
Keep it temporary.
The current result is kept in browser session storage so it survives the popup closing during reload, then clears with navigation, tab closure, extension reload, or browser restart.
Cache signals
Cache headers are useful hints. Not courtroom evidence.
The extension reports states such as HIT, MISS, BYPASS, DYNAMIC, UNKNOWN, or ERROR. Explicit cache-result headers have priority. Missing signals do not prove that caching is disabled.
Response headers
Reads visible headers such as Cache-Status, FastPixel, Cloudflare, Varnish, LiteSpeed, FastCGI, cache age, and policy headers where Chrome exposes them.
Layer-aware FastPixel
CDN and local cache headers are interpreted separately, so an outer MISS with a local HIT can still be reported as a useful cache layer result.
WP Rocket footprint
A supported cached@ page-source footprint can be treated as a detected cache result. Metadata without the footprint remains context only.
Bypass context
Server-provided skip reasons and standard WordPress logged-in markers can explain likely bypass situations without reading account roles or usernames.
Local timing
Shows local page loaded, TTFB, and page structure ready timing for the user-requested reload. It is not a Lighthouse score or Core Web Vitals report.
Copyable report
Copy a compact summary or a full visible response-header report. Cookie and authentication response-header values are redacted.
Local-first by design
No analytics. No telemetry. No external API.
All analysis happens locally in the browser. The extension does not send URLs, headers, results, timing, or cache reports to boring works or to third parties.
✓ Current tab only
✓ User-initiated check
✓ Temporary session storage
✓ No persistent URL history
✓ No tracking
✓ No remote code
Store privacy URL
The product-specific privacy policy for Chrome Web Store submission is available at:
Screenshots
A small popup with clear states.
The extension stays compact: disclosure before the check, color-coded but labeled results, important values, local timing, and a technical section when needed.
Before you check
The popup states what will be processed before the user starts the check.
Detected cache hit
Important values and timing are visible without opening technical details.
Unknown is okay
No visible cache signal is treated calmly: it is not reported as proof that caching is disabled.
Support
Questions, store review, or cache-signal edge cases?
For support, privacy questions, or Chrome Web Store review context, contact boring works by email. Please include the extension version, browser, URL context if safe to share, and the copied summary when useful.
Support email
tools@boringworks.eu
Use this address for support and privacy questions related to boring Cache Check.
Store fields
Stable URLs
Chrome Web Store: Open store listing ↗
Homepage: https://boringworks.eu/boring-cache-check/
Support: https://boringworks.eu/boring-cache-check/#support
Privacy: https://boringworks.eu/boring-cache-check/privacy/
Why boring?
Because the best tools do not need to perform.
This is the shared boring works principle, not a feature of one extension. A good tool should solve a real task clearly, stay understandable, and get out of the way.
No dashboard where a popup is enough.
No hidden service where local browser processing can do the job.
No certainty theatre where cache signals are only careful hints.