WordPress HTTP ETag cache validators and the Core Web Vitals

87.7% of audited sites (55,531) serve ETag headers on their responses (76% good LCP, 1.8s median), while 12.3% omit ETag validators (79% good LCP, 1.6s median).

Field data PhoneDesktopAll Scope All sites October 2026 edition · Desktop field outcomes · WordPress sites only
WordPress Scoped to 63,295 sites out of 203,892 analyzed (cms) Compare with all sites →

One in ten WordPress sites, 12.3%, have no ETag cache validation. Of the 87.7% that do, 100% use ETag validators, and 76% of those sites have a good LCP, against 76% of all WordPress sites.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 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: 76%, against 76% of all WordPress sites.

SitesGood, needs improvement, poor LCPMedian
All WordPress sites17,00576%1.7s
No ETag header 12.3%1,66279%1.6s
ETag header present 87.7%15,34376%1.8s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

ETag cache validation usage

Nine in ten WordPress sites uses ETag cache validation, and 100% of those use ETag validators.

All WordPress sites 63,295 sites
No ETag header 12.3% ETag cache validation 87.7%
Sites with ETag cache validation 55,531 sites
ETag header present 100.0%
ETag header present 100.0%
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 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 time to first byte (TTFB): 1004 ms median for ETag validators against 936 ms for no ETag header. Overall median field LCP is 1.8s for ETag validators (TTFB 1004 ms, load delay 290 ms, load duration 128 ms, render delay 220 ms) versus 1.6s for no ETag header.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All WordPress sites 11,805999 ms289 ms219 ms289 mslab 330 ms1.8s
No ETag header 1,066936 ms273 ms202 ms273 mslab 314 ms1.6s
ETag header present 10,7391004 ms290 ms220 ms290 mslab 333 ms1.8s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

ETag cache validation per framework

Alpine sets the ETag cache validation to ETag validators on 96% of its sites, and 82% of Alpine sites have a good LCP, against 76% of all sites.

FrameworkETag cache validation on its sitesGood LCP
All WordPress sites 63,295 sitesETag header present 88%No ETag header 12%76%
Alpine 380 sitesETag header present 96%82%
jQuery 60,314 sitesETag header present 88%No ETag header 12%75%
Vue 4,844 sitesETag header present 84%No ETag header 16%75%
React 2,233 sitesETag header present 89%No ETag header 11%66%
ETag header present No ETag header
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

ETag headers or the framework

Does the framework explain the ETag cache validation difference?

On jQuery, 75% of sites with ETag validators ETag cache validation have a good LCP, against 79% of jQuery sites without ETag cache validation. Within jQuery, 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 55,531 audited sites (87.7%) 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 76% good LCP (1.8s median, 1004 ms TTFB) while the 12.3% without ETag headers record 79% good LCP (1.6s median, 936 ms TTFB).

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding HTTP ETag cache validators

Keep content-hash ETag headers enabled for static assets and HTML revalidation, or pair long Cache-Control max-age rules with versioned query strings. On WordPress, 87.7% of sites emit ETag validators (76% good LCP, 1.8s median) while 12.3% strip or omit them (79% good LCP, 1.6s median).

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 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 · 63,295 crawled WordPress sites (17,005 with desktop Chrome field data, October 2026) · How we measured