LCP phase breakdown

The LCP attribution sub-parts: TTFB, resource load delay, resource load time, element render delay.

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

At a glance the headline numbers for LCP phase breakdown

The LCP attribution sub-parts: TTFB, resource load delay, resource load time, element render delay.

1.3s
Median LCP stack
the measures at p50
49%
Biggest: TTFB
644ms of the stack
1.2s
Headroom at p50
vs the 2.5s target
+0.64
Strongest correlation
TTFB vs LCP (Spearman)

The typical LCP image waits 318ms before it even starts downloading.

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

Where the milliseconds go the phases at the median, against the budget

2.5s target
TTFB 644ms Load delay 318ms Load time 141ms Render delay 223ms

At the median the whole stack uses 1.3s, inside the 2.5s LCP budget. The biggest piece is TTFB at 644ms. computed

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

Passing CLS per phase the share of sites passing, by how long each phase takes

100%75%50%25%
TTFB Load delay Load time Render delay

Each line is one phase: left = sites where it is quick, right = sites where it drags (buckets, short to long). The steeper the fall, the more that phase decides CLS.

Load delay falls hardest: from its fastest to its slowest bucket the CLS pass rate drops 35 points, down to 49%. computed

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

The 4 distributions how each phase spreads across sites - color is the share passing in that range

TTFB p50 644ms · p75 1.2s
21–35>p98
Load delay p50 318ms · p75 551ms
0>p98
Load time p50 141ms · p75 226ms
0>p98
Render delay p50 223ms · p75 344ms
30–44>p98
mostly passing tipping mostly failing

TTFB stays green across its whole range: it never decides CLS. Load delay turns red in its tail - the failing sites live there. computed

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

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

The LCP is a sum of four waits. TTFB is the server and the network producing the HTML. Load delay is the gap before the LCP resource even starts downloading, which is mostly a discovery problem. Load time is the download itself. Render delay is the gap between having the resource and painting it, usually render-blocking CSS or a font.

The split tells you which fix applies. A TTFB problem lives in hosting and caching. A load delay problem lives in markup and hints. A load time problem lives in image weight. A render delay problem lives in the head of the document. Optimizing the image while TTFB is the bottleneck does nothing.

How do the LCP phases affect the Core Web Vitals?

TTFB is part of the LCP itself, so this is arithmetic, not correlation. 90% of sites at the low end pass the LCP. Past 2.1s, the typical site fails. At the top of the range only 7% pass.

Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.