The State of Web Vitals

Third-party share

The share of requests going to third parties.

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

At a glance the headline numbers for Third-party share

The share of requests going to third parties.

—
Median (p50)
0 sites
—
p75
—
p99
Long tail
The State of Web Vitals · Q1 2026 · 94,910 sites · desktop field datacorewebvitals.io/state-of-cwv
2

Third-party share the value at each percentile of the fleet

0.0%
p10
0.0%
p25
0.0%
p50
0.0%
p75
0.0%
p90
0.0%
p99

Third-party share —. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · desktop field datacorewebvitals.io/state-of-cwv
3

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

The domain count measures connections. The third-party share measures how much of the page you do not control. Third-party script runs on the same main thread as your own code. A slow tag delays the response to every click, and that lag is your INP. Ads, embeds and consent banners inject late and shift the layout. That is CLS.

A third-party file can grow or change behaviour overnight. It never passes through your build pipeline. Your vitals move while your own code did not change. The higher the share, the more of your Core Web Vitals depends on someone else's release schedule.

Go fix it The case for limiting analytics and tracking scripts → Chat widgets with perfect Core Web Vitals → Speed up a Calendly integration →
Related signals Media per page → Image format mix → Script loading mix → Iframe loading → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured