Skip to content

Cache-Control: no-store blocks browser back/forward cache

The back/forward cache, or bfcache, is a browser feature that lets visitors hit the back or forward button and see the page appear instantly, without reloading it from scratch. This check found a Cache-Control: no-store header on a public page with no cookie-setting reason that would justify it, and browsers exclude any page sending no-store from using bfcache. This is a Lighthouse 12 opportunity that Google's own tooling flags directly: near-instant back/forward navigation is a real, measurable engagement signal, and losing it makes browsing your site feel slower than it needs to, particularly on mobile where visitors flick back and forth often. Your developer should remove no-store from public pages and use no-cache or a short max-age instead, reserving no-store only for genuinely sensitive, logged-in responses that must never be cached under any circumstances. This is a small server configuration change, about thirty minutes to make and verify.

Why this matters

This is a Lighthouse 12 opportunity that Google's own tooling flags directly: near-instant back/forward navigation is a real, measurable engagement signal, and losing it makes browsing your site feel slower than it needs to, particularly on mobile where visitors flick back and forth often.

How to fix it

Your developer should remove no-store from public pages and use no-cache or a short max-age instead, reserving no-store only for genuinely sensitive, logged-in responses that must never be cached under any circumstances. This is a small server configuration change, about thirty minutes to make and verify.