The typical page reaches DOM interactive after 384ms in the lab

1

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

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

384ms

DOM interactive

on the typical page

671ms

DOM complete

on the typical page

676ms

load event

on the typical page

185,146

sites measured

phone field data

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

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

2

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

0ms 63ms 125ms 188ms 250ms

200ms

0 22769 45538

0 4–8 9–17 18–35 36–73 74–151 152–311 312–642 643–1327 1328–2742 2743–5664 >p98

Good (≤200ms) Needs improvement Poor (>500ms) Site count

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

3

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

Document lifecycle (lab) — dom interactiveSitesPassing INPINP

0 583 96% 99ms

9–17 114 81% 115ms

18–35 1,513 78% 119ms

36–73 7,509 77% 120ms

74–151 23,531 88% 97ms

152–311 45,538 92% 95ms

312–642 45,134 94% 97ms

643–1327 33,249 94% 100ms

1328–2742 17,561 94% 103ms

2743–5664 6,721 93% 103ms

>p98 3,690 90% 103ms

Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — dom interactive 384ms. p75 858ms. p99 12.4s. At the low end (0ms): INP 99ms. At the high end (>p98): INP 103ms. computed

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

4

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

0ms 63ms 125ms 188ms 250ms

200ms

0 26335 52670

0 5–11 12–23 24–50 51–107 108–229 230–493 494–1059 1060–2277 2278–4893 4894–10516 >p98

Good (≤200ms) Needs improvement Poor (>500ms) Site count

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

5

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

Document lifecycle (lab) — dom completeSitesPassing INPINP

0 1,449 95% 100ms

12–23 185 78% 117ms

24–50 1,410 79% 107ms

51–107 4,541 81% 106ms

108–229 17,845 88% 95ms

230–493 44,990 92% 93ms

494–1059 52,670 93% 97ms

1060–2277 36,554 94% 103ms

2278–4893 16,497 92% 106ms

4894–10516 5,327 89% 111ms

>p98 3,674 87% 108ms

Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — dom complete 671ms. p75 1.4s. p99 24.1s. At the low end (0ms): INP 100ms. At the high end (>p98): INP 108ms. computed

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

6

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

0ms 63ms 125ms 188ms 250ms

200ms

0 26293 52586

0 5–11 12–23 24–50 51–107 108–230 231–494 495–1061 1062–2281 2282–4903 4904–10541 >p98

Good (≤200ms) Needs improvement Poor (>500ms) Site count

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

7

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

Document lifecycle (lab) — loadSitesPassing INPINP

0 1,468 95% 100ms

12–23 185 78% 117ms

24–50 1,402 79% 107ms

51–107 4,522 81% 106ms

108–230 17,855 88% 95ms

231–494 44,714 92% 93ms

495–1061 52,586 93% 97ms

1062–2281 36,689 94% 103ms

2282–4903 16,644 92% 106ms

4904–10541 5,404 89% 111ms

>p98 3,673 87% 108ms

Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — load 676ms. p75 1.4s. p99 24.1s. At the low end (0ms): INP 100ms. At the high end (>p98): INP 108ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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 INP. DOM complete separates passing sites from failing sites the most. Where the DOM complete is low, 95% of sites pass the INP. Where it is high, 87% do. The decline is gradual. There is no point where sites suddenly start failing.

Go fix it How we measured → Head vs footer JavaScript →