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

LCP INP CLS

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

672ms

DOM complete

on the typical page

676ms

load event

on the typical page

185,361

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

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

0ms 63ms 125ms 188ms 250ms

200ms

0 32026 64052

0–249 250–499 500–749 750–999 1000–1249 1250–1499 1500–1749 1750–1999 2000+

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

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

Document lifecycle (lab) — dom interactiveSitesPassing INPINP

0–249 64,052 88% 97ms

250–499 45,208 93% 96ms

500–749 22,832 94% 99ms

750–999 13,794 94% 101ms

1000–1249 9,160 94% 100ms

1250–1499 6,418 94% 102ms

1500–1749 4,500 94% 103ms

1750–1999 3,235 92% 103ms

2000+ 16,162 92% 103ms

Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — dom interactive 384ms. p75 859ms. p99 12.4s. At the low end (0–249ms): INP 97ms. At the high end (2000+ms): INP 103ms. computed

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

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

0ms 63ms 125ms 188ms 250ms

200ms

0 35685 71370

0–499 500–999 1000–1499 1500–1999 2000–2499 2500–2999 3000+

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

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

Document lifecycle (lab) — dom completeSitesPassing INPINP

0–499 71,370 90% 95ms

500–999 48,257 93% 97ms

1000–1499 23,177 93% 102ms

1500–1999 12,516 93% 104ms

2000–2499 7,351 93% 105ms

2500–2999 4,705 93% 106ms

3000+ 17,985 90% 108ms

Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — dom complete 672ms. p75 1.4s. p99 24.1s. At the low end (0–499ms): INP 95ms. At the high end (3000+ms): INP 108ms. computed

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

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

0ms 63ms 125ms 188ms 250ms

200ms

0 35483 70966

0–499 500–999 1000–1499 1500–1999 2000–2499 2500–2999 3000+

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

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

Document lifecycle (lab) — loadSitesPassing INPINP

0–499 70,966 90% 95ms

500–999 48,205 93% 97ms

1000–1499 23,226 93% 102ms

1500–1999 12,590 93% 104ms

2000–2499 7,445 93% 105ms

2500–2999 4,759 93% 106ms

3000+ 18,170 90% 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 (0–499ms): INP 95ms. At the high end (3000+ms): INP 108ms. computed

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

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: 88% at one end, 92% at the other. This signal does not separate passing sites from failing ones.

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 189,915 sites, representing millions of real page loads · How we measured