The State of Web Vitals

LCP origin

Whether the LCP resource is served first-party or third-party.

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

At a glance the headline numbers for LCP origin

Whether the LCP resource is served first-party or third-party.

2
Categories
67,350 sites
78.6%
Top share
first_party
97ms
Top INP
Median for first_party

21.4% of LCP images load from a third-party domain.

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

LCP origin who uses what, and how fast each group loads

Median INP
0
100ms
200ms
300ms
400ms
500ms
first_party97ms79% of sites
third_party102ms21% of sites
VariantShare of sitesMedian
first_party 52,962 sites
79%
97ms
third_party 14,388 sites
21%
102ms

Little daylight between the groups: every variant sits near 97ms median INP. computed

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

Passing INP per LCP origin which group passes the INP most often

VariantSitesPassing INPINP
First party 78.6% 52,962 94% 97ms
Third party 21.4% 14,388 89% 102ms
Good Needs Improvement Poor Sorted best-passing first · median colored by its own rating · pass = good INP (200ms at p75) · one value per site

94% of First party sites pass INP. Third party trails 5 points behind. computed

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

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

An LCP image on a third-party domain pays the connection tax at the worst possible moment. The DNS lookup, TCP handshake and TLS negotiation for that domain happen before the first byte of the image arrives. The same image on your main domain rides the connection that is already open.

Third-party also means someone else's cache rules and someone else's outages under your most important resource. Self-host the hero if you can. If an image CDN must serve it, preconnect to that domain so the setup happens early instead of inside the LCP.

How does this affect the Core Web Vitals?

The choice barely moves the LCP: 84% pass at best, 81% at worst. This signal does not separate passing sites from failing ones.

Go fix it LCP: resource load delay → Third-party domains → Guide to resource prioritization →
Related signals LCP image size → LCP loading attribute → LCP element type → LCP responsive markup → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured