HTTP ETag cache validators and the Core Web Vitals
83.8% of audited sites (176,769) serve ETag headers on their responses (86% good LCP, 1.4s median), while 16.2% omit ETag validators (87% good LCP, 1.2s median).
16.2% of sites have no ETag cache validation. Of the 83.8% that do, 100% use ETag validators, and 86% of those sites have a good LCP, against 86% of all sites.
LCP pass rate
Sites with ETag validators ETag cache validation have a good LCP most often: 86%, against 86% of all sites.
ETag cache validation usage
83.8% of sites use ETag cache validation, and 100% of those use ETag validators.
LCP phase breakdown for sites with and without ETag headers
Across the four LCP sub-parts in Chrome's field data, the largest gap between ETag validators and no ETag header sits in resource load delay: 283 ms median for ETag validators against 217 ms for no ETag header. Overall median field LCP is 1.4s for ETag validators (TTFB 575 ms, load delay 283 ms, load duration 112 ms, render delay 196 ms) versus 1.3s for no ETag header.
ETag cache validation per platform
Wix sets the ETag cache validation to ETag validators on 100% of its sites, and 92% of Wix sites have a good LCP, against 86% of all sites.
ETag headers or the platform
Does the platform explain the ETag cache validation difference?
On WordPress, 75% of sites with ETag validators ETag cache validation have a good LCP, against 79% of WordPress sites without ETag cache validation. Within WordPress, sites with ETag validators ETag cache validation have a good LCP less often.
Why ETag headers matter on repeat visits and CDN edge revalidations
An Entity Tag (ETag) is an opaque version identifier attached to an HTTP response. Across 176,769 audited sites (83.8%) that emit ETag headers, browsers and CDN edges can send If-None-Match conditional requests when cached files expire and receive a header-only 304 Not Modified response instead of re-downloading the full payload. Because first-visit crawl and field LCP measurements weight initial loads and immutable hashed assets heavily, sites with ETag headers record 86% good LCP (1.4s median, 575 ms TTFB) while the 16.2% without ETag headers record 87% good LCP (1.2s median, 549 ms TTFB).
Understanding HTTP ETag cache validators
Enable strong or weak content-based ETag headers on your web server or CDN edge so expired cache entries can revalidate via If-None-Match and 304 Not Modified in a single header-only round trip. If you run multiple origin servers behind a load balancer, avoid inode-based default ETags in Apache or nginx so revalidation requests never miss across nodes. Across all audited sites, 83.8% emit ETag validators (86% good LCP, 1.4s median) and 16.2% omit them (87% good LCP, 1.2s median).
By Arjen Karel · 210,902 crawled sites (69,745 with desktop Chrome field data, October 2026). How we measured.