The State of Web Vitals

Third-party share

The share of requests going to third parties.

Field data PhoneDesktopAll Scope All sites Q2 2026 edition · All devices 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.

75.0%
on the typical site
half of sites sit at or below
75.0%
1 in 4 sites exceed this
the top quarter
93.7%
the heaviest 1%
the long tail
4,450
sites measured
all-device field data

On the typical site, third parties account for 75.0% of the page.

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

Distribution & median INP site count and median INP at each level of third-party share

0ms 63ms 125ms 188ms 250ms
200ms
0 1499 2997
0 0–10 10–20 20–30 30–40 40–50 50–60 60–70 70–80 80–90 90–100 100
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
3

Passing INP by third-party share which level passes the INP most often

Third-party shareSitesPassing INPINP
0 40 81% 90ms
0–10 22 92% 95ms
10–20 44 91% 90ms
20–30 21 100% 95ms
30–40 19 93% 90ms
50–60 29 94% 89ms
60–70 1,213 94% 87ms
70–80 2,997 92% 85ms
100 41 90% 94ms
Good Needs Improvement Poor Faded rows: under 100 sites

Third-party share 75.0%. p75 75.0%. p99 93.7%. At the low end (0): INP 90ms. At the high end (100): INP 94ms. computed

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

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.

How does the third-party share affect the Core Web Vitals?

Passing INP barely moves across the range: 94% at one end, 92% at the other. This signal does not separate passing sites from failing ones.

The effect is bigger on LCP. With little third-party content, 86% of sites pass it. Where third parties dominate, 80% do.

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 189,915 sites, representing millions of real page loads · How we measured