HTTP cache TTL tiers (immutable, long TTL, no-store) and the Core Web Vitals
Unspecified cache headers (97.6%), long TTLs (74.1%), medium TTLs (73.5%), no-store (67.7%), short TTLs (67.7%), no-cache (39.6%), and Cache-Control: immutable (26.7%).
26.7% of sites use Cache-Control: immutable HTTP cache TTL tiers, and 87% of those sites have a good LCP, against 86% of all sites.
LCP pass rate
Sites with Cache-Control: immutable HTTP cache TTL tiers have a good LCP most often: 87%, against 86% of all sites. Sites with no-store cache tiers have it least often, at 85%.
HTTP cache TTL tiers usage
Unspecified cache is the most used: 97.6% of sites. Cache-Control: immutable is 26.7% of sites.
How HTTP cache TTL tiers affect the four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between Cache-Control: immutable and no-store sits in time to first byte (TTFB): 498 ms median for Cache-Control: immutable against 592 ms for no-store. Overall median field LCP is 1.4s for Cache-Control: immutable (TTFB 498 ms, load delay 363 ms, load duration 120 ms, render delay 215 ms) versus 1.4s for no-store.
Understanding HTTP cache TTL tiers
How Cache-Control: immutable and long TTLs accelerate repeat views
Field Core Web Vitals combine first visits and repeat navigations from Chrome users. Sites that serve content-hashed static bundles with Cache-Control: immutable (26.7% of sites) achieve 87% good field LCP (1.4s median LCP), outperforming sites limited to short TTLs (67.7%, 86% good LCP) or no-store responses (67.7%, 85% good LCP).
Fingerprint static CSS, JavaScript, and font filenames and serve them with Cache-Control: public, max-age=31536000, immutable. While 74.1% of sites use long cache TTLs, only 26.7% include the immutable directive (87% good LCP), which prevents unnecessary 304 revalidation round-trips when users reload or navigate across pages.
How HTTP cache TTL tiers plays out per platform
What the field data shows when you isolate a single CMS or framework.
16.5% of WordPress sites serve Cache-Control: immutable assets, while 80.2% use long TTLs.
WordPress core appends a ?ver= query string to enqueued scripts and styles with wp_enqueue_script(). Across WordPress, 80.2% of sites serve long-TTL static files and 16.5% emit Cache-Control: immutable.
70.6% of React & Next.js sites serve Cache-Control: immutable assets (85% good LCP).
Across React sites, 70.6% emit Cache-Control: immutable headers on static chunks (85% good LCP) compared with 76% on short-TTL sites.
By Arjen Karel · 225,631 crawled sites (74,498 with desktop Chrome field data, 220,979 sites with HTTP cache TTL tiers, November 2026). How we measured.