All Production Symptoms
Production Symptom3 Causal Mechanisms

Browser Back button reloads the entire page from scratch

Attaching unload listeners, sending Cache-Control: no-store, or holding open IndexedDB locks disqualifies the page from instant Back/Forward Cache snapshots.

DevTools / RUM Signature
DevTools Application > Back/forward cache: NotRestoredReasons = ["unload-handler"] or Cache-Control: no-store

Causal Chain of Browser Mechanisms

Ordered from trigger to root invariant. Open any mechanism to inspect its internals or reproduce the behavior in an interactive lab.

Step 1
Network & PerformanceBaseline · Widely

In-memory cache snapshotting the full JS heap and DOM tree on outbound navigation to restore the page instantaneously on Back/Forward.

Step 2
Network & PerformanceBaseline · Widely

Controls disk and shared cache reuse via Cache-Control, ETag, and Vary headers—separating immutable hashed assets from revalidated HTML documents.

Step 3
Web APIsBaseline · Widely

Prevent dropped analytics and broken bfcache on tab close by handing <= 64 KB POST payloads to the browser network process on visibilitychange.

Seen in Architecture Autopsies