Performance fix guide
Page Not Eligible for Back/Forward Cache
The page is not eligible for the browser back/forward cache (bfcache), which means navigating back requires a full reload instead of an instant restore.
Issue ID: CWV-BFCACHE-001
Severity: minor
Impact: Low
Effort: M
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
The page is not eligible for the browser back/forward cache (bfcache), which means navigating back requires a full reload instead of an instant restore.
Why it matters
The page is not eligible for the browser back/forward cache (bfcache), which means navigating back requires a full reload instead of an instant restore. This affects load speed, Core Web Vitals, and how many visitors stay long enough to convert.
How we detect it
- FreeSiteAudit flags this issue when the rule for CWV-BFCACHE-001 fails and the page evidence points to Performance tool.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Avoid using unload event listeners
- 2Close WebSocket connections when the page is hidden
- 3Ensure no Cache-Control: no-store header is set for the document
- 4Check chrome://back-forward-cache for specific blockers
How to re-check it
- Test bfcache eligibility in Chrome DevTools Application panel
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.