Unlocking Back/Forward Cache (bfcache) for Instant Back Navigations
Back/forward navigations account for 15–20% of CrUX page loads. Blocking bfcache forces full network reloads that drag down real-user CWV.
Dmitry K., Technical SEO Lead · SEO Space
1. Why bfcache Blockers Quietly Degrade Field Core Web Vitals
When shoppers click from a category grid to a product page and press Browser Back, an eligible bfcache entry restores the full JavaScript and scroll state from memory in 0ms.
Legacy `window.onunload` handlers—often injected by outdated chat widgets or analytics tags—or overly strict `Cache-Control: no-store` HTML headers disqualify pages from bfcache across Chrome, Edge, and Safari.
- Audit Chrome DevTools -> Application -> Back/forward cache across top landing templates.
- Replace any `unload` listeners with `pagehide` or `visibilitychange` events.
- Never emit `Cache-Control: no-store` on public indexable HTML pages; use `no-cache` or `max-age=0, must-revalidate` instead.
2. Refreshing Stale Stock Badges on pageshow Restore
When `event.persisted` is true in `pageshow`, run a tiny async check to refresh live inventory or cart counts without blocking bfcache eligibility.
window.addEventListener('pageshow', (event) => {
if (event.persisted) {
refreshCartCountAndStockBadge();
}
}); 3. Common bfcache Disqualifiers & Clean Fixes
Eliminate the top three engineering blockers reported in Chrome DevTools NotRestoredReasons telemetry.
| Disqualifier Reason | Typical Culprit | Production Resolution |
|---|---|---|
| unload handler registered | Legacy analytics / chat SDK | Migrate to pagehide / visibilitychange |
| Cache-Control: no-store | Over-aggressive security middleware | Use Cache-Control: no-cache on public SSR |
| Open WebSocket / IDB lock | Unclosed connection on hide | Close in pagehide & reopen on pageshow |
Need this indexation setup audited on your domain?
Send your website URL. We check raw HTML parity, log crawl hits, canonical discipline, and sitemap architecture manually within 24 hours.