The State of Web Vitals

Document lifecycle (lab)

Lab document lifecycle: DOM interactive, DOM complete, load event.

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

At a glance the headline numbers for Document lifecycle (lab)

Lab document lifecycle: DOM interactive, DOM complete, load event.

387ms
DOM interactive
on the typical page
688ms
DOM complete
on the typical page
692ms
load event
on the typical page
94,847
sites measured
desktop field data

The typical page reaches DOM interactive after 387ms in the lab.

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

Distribution & median LCP site count and median LCP at each level of document lifecycle (lab) — dom interactive

0ms 750ms 1500ms 2250ms 3000ms
2.5s
0 11757 23514
0 4–8 9–16 17–33 34–67 68–135 136–273 274–552 553–1115 1116–2253 2254–4555 >p98
Good (≤2.5s) Needs improvement Poor (>4s) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · desktop field datacorewebvitals.io/state-of-cwv
3

Passing LCP by document lifecycle (lab) — dom interactive which level passes the LCP most often

Document lifecycle (lab) — dom interactiveSitesPassing LCPLCP
0 317 79% 1.8s
17–33 532 82% 1.4s
34–67 3,203 87% 1.2s
68–135 9,427 90% 1.1s
136–273 21,973 92% 1.1s
274–552 23,514 91% 1.3s
553–1115 18,396 88% 1.5s
1116–2253 11,156 75% 1.9s
2254–4555 4,432 56% 2.3s
>p98 1,891 62% 2.0s
Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — dom interactive 387ms. p75 850ms. p99 6.7s. Spearman with LCP r = +0.34. At the low end (0ms): LCP 1.8s. At the high end (>p98): LCP 2.0s. computed

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

Distribution & median LCP site count and median LCP at each level of document lifecycle (lab) — dom complete

0ms 750ms 1500ms 2250ms 3000ms
2.5s
0 13517 27034
0 5–11 12–22 23–47 48–100 101–210 211–444 445–938 939–1981 1982–4184 4185–8836 >p98
Good (≤2.5s) Needs improvement Poor (>4s) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · desktop field datacorewebvitals.io/state-of-cwv
5

Passing LCP by document lifecycle (lab) — dom complete which level passes the LCP most often

Document lifecycle (lab) — dom completeSitesPassing LCPLCP
0 750 78% 1.7s
23–47 543 84% 1.2s
48–100 1,643 89% 1.1s
101–210 7,250 90% 1.0s
211–444 21,237 92% 1.1s
445–938 27,034 91% 1.3s
939–1981 20,747 86% 1.6s
1982–4184 9,965 72% 1.9s
4185–8836 3,789 71% 1.8s
>p98 1,882 77% 1.7s
Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — dom complete 688ms. p75 1.4s. p99 15.0s. Spearman with LCP r = +0.34. At the low end (0ms): LCP 1.7s. At the high end (>p98): LCP 1.7s. computed

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

Distribution & median LCP site count and median LCP at each level of document lifecycle (lab) — load

0ms 750ms 1500ms 2250ms 3000ms
2.5s
0 13496 26991
0 5–11 12–22 23–47 48–100 101–211 212–446 447–943 944–1993 1994–4214 4215–8907 >p98
Good (≤2.5s) Needs improvement Poor (>4s) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · desktop field datacorewebvitals.io/state-of-cwv
7

Passing LCP by document lifecycle (lab) — load which level passes the LCP most often

Document lifecycle (lab) — loadSitesPassing LCPLCP
0 758 78% 1.7s
23–47 542 84% 1.2s
48–100 1,635 89% 1.1s
101–211 7,268 90% 1.0s
212–446 21,197 92% 1.1s
447–943 26,991 91% 1.3s
944–1993 20,756 86% 1.6s
1994–4214 10,012 72% 1.9s
4215–8907 3,800 70% 1.8s
>p98 1,881 77% 1.6s
Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — load 692ms. p75 1.4s. p99 15.1s. Spearman with LCP r = +0.34. At the low end (0ms): LCP 1.7s. At the high end (>p98): LCP 1.6s. computed

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

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

The document lifecycle is the old way of measuring pages, and it still says useful things. DOM interactive marks the HTML fully parsed. DOM complete waits for the subresources. The load event is the official end of loading, and everything that listens for it (analytics, widgets, third-party tags) starts there.

A long gap between interactive and complete means resource weight, not markup. These milestones do not map onto user experience the way the vitals do, which is why they were replaced. But a page with a slow lifecycle does not produce fast vitals.

How does this affect the Core Web Vitals?

Document lifecycle (lab) correlates with the LCP. DOM interactive separates passing sites from failing sites the most. Where the DOM interactive is low, 79% of sites pass the LCP. Where it is high, 62% do. The decline is gradual. There is no point where sites suddenly start failing.

Go fix it How we measured → Head vs footer JavaScript →
Related signals Total Blocking Time (lab) → Main-thread CPU (lab) → Lab paint timeline → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured