Script origin (1P/3P)

First-party vs third-party scripts - counts and bytes.

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

At a glance the headline numbers for Script origin (1P/3P)

First-party vs third-party scripts - counts and bytes.

2
Categories
In the distribution
78.8%
Fleet share
Top: first_party
97.4%
Sites with any
Of first_party

21.2% of scripts come from third parties.

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

The script origin (1P/3P) mix who uses what, and how fast each group loads

Median INP (sites using feature)
0
100ms
200ms
300ms
400ms
500ms
First party98ms79% of sites
Third party101ms21% of sites
VariantShare of requestsMedian
First party
79%
98ms
Third party
21%
101ms

Script origin (1P/3P). On the fleet: 78.8% first party, 21.2% third party. 97.4% of sites use at least one first_party.

By count first party leads (78.8%); by bytes it is third party (56.1%). computed

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

Passing INP per bucket every category and count level at once - color is the pass rate

1
2
3
4
5
6
7
8
9
10
11
First party 78.8%
82
88
91
91
92
93
94
94
95
92
86
Third party 21.2%
94
95
92
94
93
93
93
91
92
89
79
← few of this category on the pagemany →
60%95%+ of sites passing INP Faded cells: under 100 sites

Each row is a category, each column its own count bucket (few on the left, many on the right); the cell is the share of those sites passing INP.

Third party swings the hardest: 94% of sites pass INP with few, 79% with many. computed

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

Few vs many - does quantity cost INP? the pass rate with few vs many of each category

60%70%80%90%100% few → many
Third party 21.2% 94%79%
First party 78.8% 82%86%
% of sites passing INP · hollow ring = pages with few, solid dot = pages with many

Per category: the pass rate among pages with FEW of it (hollow ring) against pages with MANY (solid dot), worst trend first. Thin buckets are excluded from the endpoints.

More Third party costs the most: the INP pass rate falls from 94% with few to 79% with many. computed

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

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

First-party script is in your bundle, your build, your deploy. Third-party script arrives from someone else's server at whatever size and shape it has today. Both run on the same main thread. Only one of them is yours to fix.

A high third-party share is a ceiling on your INP work: optimize your own code all you want, the tags still run between your visitor's clicks. Past that ceiling the fix list changes. Fewer vendors, deferred loading, facades instead of always-on embeds.

How does this affect the Core Web Vitals?

The choice barely moves the INP: 93% pass at best, 92% at worst. This signal does not separate passing sites from failing ones.

Related signals Script initiator → Image dimensions set → Scripts per page → Stylesheets per page → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured