This feature is only shown in the feature list to users with edit access.

It allows popular payloads that are identical across websites to be cached in a privacy-preserving single-keyed cache to accelerate page loads on the web, and reduce the amount of data transferred over the wire and reduce network costs, resulting in faster performance.


Browsers split HTTP caches based on the top-frame visited origin (“double-keyed” or "triple-keyed" caching) to prevent sites from tracking users via a timing attack on a cross-site client cache. Chrome’s analysis estimates that split caching results in a 3% increase in cache misses, i.e. fetches for which a payload exists in the cache of the user's device, but is unavailable to the page because it was fetched by the user while loading a page from a different origin. This results in approximately 4% more total bytes being fetched over the network. Our analysis further revealed that many of the redundant fetches caused by split caching were for common payloads associated with displaying user content (libraries, fonts, widgets, ads) or common payloads that assist in operating online businesses (analytics). The delayed arrival of these common payloads resulted in visible "jank" for users, impacting performance metrics like LCP, FCP and CLS. This jank has been associated with negative effects to online business' engagement and conversion rates. Furthermore, delayed loads of analytics and ads payloads can result in missed ads impressions and dropped analytics hits.

Status in Chromium


In development (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signals


Intent to Prototype url

Intent to Prototype thread

Last updated on 2022-05-10