HTTP Last-Modified headers on React sites
99.7% of audited sites (9,537) include Last-Modified timestamp validators (84% good LCP, 1.4s median), while 0.3% omit them (71% good LCP, 2.1s median).
0.3% of React sites have no Last-Modified cache validation. Of the 99.7% that do, 100% use Last-Modified headers, and 84% of those sites have a good LCP, against 84% of all React sites.
LCP pass rate
Sites with Last-Modified headers Last-Modified cache validation have a good LCP most often: 84%, against 84% of all React sites.
Last-Modified cache validation usage
99.7% of React sites use Last-Modified cache validation, and 100% of those use Last-Modified headers.
LCP phase breakdown for sites with and without Last-Modified headers
Across the four LCP sub-parts in Chrome's field data, the largest gap between Last-Modified headers and no Last-Modified header sits in time to first byte (TTFB): 502 ms median for Last-Modified headers against 969 ms for no Last-Modified header. Overall median field LCP is 1.4s for Last-Modified headers (TTFB 502 ms, load delay 432 ms, load duration 131 ms, render delay 180 ms) versus 2.1s for no Last-Modified header.
Last-Modified cache validation per platform
Wix sets the Last-Modified cache validation to Last-Modified headers on 100% of its sites, and 94% of Wix sites have a good LCP, against 84% of all sites.
Last-Modified headers or the platform
How Last-Modified supports conditional requests and heuristic browser caching
Last-Modified is HTTP's original timestamp validator. Across 9,537 audited sites (99.7%), responses include Last-Modified so browsers can send If-Modified-Since on expired cache entries and RFC 9111 caches can apply heuristic freshness when explicit max-age directives are absent. Sites sending Last-Modified reach 84% good LCP (1.4s median, 502 ms TTFB), compared with 71% good LCP (2.1s median, 969 ms TTFB) on the 0.3% of sites that omit it.
Understanding HTTP Last-Modified headers
Emit Last-Modified headers alongside ETag and Cache-Control on static and cacheable responses so both browsers and CDN edge nodes can revalidate stale objects via If-Modified-Since. In containerized CI/CD pipelines that rewrite file modification timestamps on every deploy, pair Last-Modified with content-hash ETag validators so unchanged files still return 304 Not Modified. Across the dataset, 99.7% of sites send Last-Modified (84% good LCP, 1.4s median) and 0.3% omit it (71% good LCP, 2.1s median).
By Arjen Karel · 9,570 crawled React sites (5,488 with phone Chrome field data, October 2026). How we measured.