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

desktop field data

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

The State of Web Vitals · Q2 2026 · 189,915 sites · desktop 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 · desktop 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 99% 49ms

9–17 114 100% 45ms

18–35 1,513 96% 52ms

36–73 7,509 97% 52ms

74–151 23,531 99% 49ms

152–311 45,538 99% 48ms

312–642 45,134 99% 49ms

643–1327 33,249 99% 49ms

1328–2742 17,561 99% 50ms

2743–5664 6,721 99% 50ms

>p98 3,690 99% 48ms

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 49ms. At the high end (>p98): INP 48ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · desktop 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 · desktop 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 100% 50ms

12–23 185 97% 45ms

24–50 1,410 98% 46ms

51–107 4,541 98% 46ms

108–229 17,845 98% 46ms

230–493 44,990 99% 47ms

494–1059 52,670 99% 49ms

1060–2277 36,554 99% 51ms

2278–4893 16,497 99% 54ms

4894–10516 5,327 98% 55ms

>p98 3,674 99% 52ms

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 50ms. At the high end (>p98): INP 52ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · desktop 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 · desktop 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 100% 50ms

12–23 185 97% 45ms

24–50 1,402 98% 46ms

51–107 4,522 98% 46ms

108–230 17,855 98% 46ms

231–494 44,714 99% 47ms

495–1061 52,586 99% 49ms

1062–2281 36,689 99% 51ms

2282–4903 16,644 99% 54ms

4904–10541 5,404 98% 55ms

>p98 3,673 99% 52ms

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 50ms. At the high end (>p98): INP 52ms. computed

The State of Web Vitals · Q2 2026 · 189,915 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?

Passing INP barely moves across the range: 100% at one end, 99% at the other. This signal does not separate passing sites from failing ones.

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