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).

Field data PhoneDesktopAll Scope All sites October 2026 edition · Desktop field outcomes

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.

The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with ETag validators ETag cache validation have a good LCP most often: 86%, against 86% of all sites.

SitesGood, needs improvement, poor LCPMedian
All sites69,74586%1.4s
No ETag header 16.2%9,16687%1.2s
ETag header present 83.8%60,57986%1.4s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

ETag cache validation usage

83.8% of sites use ETag cache validation, and 100% of those use ETag validators.

All sites 210,902 sites
No ETag header 16.2% ETag cache validation 83.8%
Sites with ETag cache validation 176,769 sites
ETag header present 100.0%
ETag header present 100.0%
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

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.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All sites 50,980571 ms274 ms191 ms274 mslab 316 ms1.4s
No ETag header 6,198549 ms217 ms156 ms217 mslab 248 ms1.3s
ETag header present 44,782575 ms283 ms196 ms283 mslab 325 ms1.4s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

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.

PlatformETag cache validation on its sitesGood LCP
All sites 210,902 sitesETag header present 84%No ETag header 16%86%
Shopify 8,573 sitesETag header present 100%97%
Squarespace 2,258 sitesETag header present 100%94%
Drupal 3,296 sitesETag header present 92%93%
Joomla 2,551 sitesETag header present 87%No ETag header 13%93%
Wix 5,825 sitesETag header present 100%92%
Adobe Commerce 1,095 sitesETag header present 98%83%
WordPress 65,509 sitesETag header present 88%No ETag header 12%76%
ETag header present No ETag header
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

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).

The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
6

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).

The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Last-Modified present → Uncompressed text responses → Main CDN → HTTP protocol → By Arjen Karel · 210,902 crawled sites (69,745 with desktop Chrome field data, October 2026) · How we measured