ETag present

Whether responses carry ETag validators.

Field data PhoneDesktopAll Scope All sites Q2 2026 edition · Phone field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for ETag present

Whether responses carry ETag validators.

0.0%
Adoption
0 of 0
With (median INP)
Without (median INP)
The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
2

ETag present sites that have it vs sites that don't

ETag present
0%

0.0% of sites send ETag headers (0 of 0). With send: INP —, 0.0% pass. Without: INP —, 0.0% pass. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
3

Why this matters for the Core Web Vitals, and where to start fixing it

An ETag is a validator. When a cached file expires, the browser can ask the server whether it changed and get a tiny 304 Not Modified back instead of the whole file. Without a validator, an expired file is downloaded again in full.

Validators matter most for the in-between caching strategies: short TTLs with frequent revisits. For hashed, immutable assets they are redundant because the file never changes under its name. One thing to watch on multi-server setups: default ETags can differ per server, and a mismatched ETag silently turns every revalidation into a full download.

Related signals Last-Modified present → Uncompressed text responses → Main CDN → HTTP protocol → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured