OOmnistu

Blog / Performance

Performance

Back/forward cache (bfcache): why the Back button can be instant, and what blocks it

Understand bfcache restores, common blockers and the privacy, analytics and freshness checks a restored page needs.

OOmnistu
Reviewed 2026-11-16 · 6 min read

When someone taps Back, some pages reappear instantly and some reload from scratch. The difference is often the back/forward cache, or bfcache. This article summarises web.dev's guide to it, as read on 15 November 2026 (the page says it was last updated 16 October 2026). It matters for page speed, for how pageviews and Core Web Vitals are counted, and for what stale or private data a restored page may show. The page itself is written for developers; here is the version for the person who commissions or reviews a site.

What it is

The page says browsers keep the whole page in memory when you navigate away, pause its JavaScript, and unpause it if you come back soon, so the restore needs no network. It says all major browsers have a bfcache, including Chrome since version 96, Firefox and Safari. It is not the HTTP cache: bfcache is a snapshot of the whole page in memory including the JavaScript heap, while the HTTP cache holds only responses. The page's explanation is that restores are always faster than even the best-optimised non-bfcache navigation.

It also says Chrome usage data shows that 1 in 10 navigations on desktop and 1 in 5 on mobile are back or forward. That is Chrome's data as quoted on the page; we have not checked it.

Details the page gives:

What blocks it (as the page lists)

What a restored page can show

Because the page is restored from memory, the page says Cache-Control revalidation does not happen on restore. If a site holds user state, especially sensitive state, it should be refreshed or cleared on the pageshow event when its persisted property is true. The page's two examples: a checkout page showing an out-of-date cart after a back navigation, and, more critically, a user who signed out on a public computer whose private data a next user could see by pressing Back. Its example reloads the page if a login cookie is missing. That is illustrative, not sufficient session validation: the server must still enforce access, and restoration handling must not briefly expose another user's sensitive state.

Ads

The page says a publisher who wants ads refreshed on back/forward should not use no-store, which it calls a bad approach that harms performance. Instead keep the page eligible and refresh the ads. It says some ad tagging libraries such as Google Publisher Tag automatically refresh actively viewed slots on a bfcache restore, and otherwise you can use pageshow to coordinate a refresh only where your ad provider's policies, consent requirements and SDK behavior permit it. This is not permission to manufacture ad impressions.

Analytics and Core Web Vitals

Omnistu advice for a site project (not from the source)

Limits

One web.dev page, read in full on 15 November 2026. Browser behaviour changes and the page itself notes it differs by browser; it links to Firefox, Safari and cross-browser pages we did not read. We ran no tests and make no claim about how much any site would speed up. The page's code examples were skimmed, not run, and its Google Analytics example assumes that product's tag.

By Omnistu.

Sources

Previous
Showing ads in an Android app: what Google Play's Ads policy restricts