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

all-device field data

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

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

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 32026 64052

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

Good (≤2.5s) Needs improvement Poor (>4s) Site count

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

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

Document lifecycle (lab) — dom interactiveSitesPassing LCPLCP

0–249 64,052 90% 1.2s

250–499 45,208 90% 1.4s

500–749 22,832 86% 1.6s

750–999 13,794 81% 1.8s

1000–1249 9,160 75% 2.0s

1250–1499 6,418 67% 2.1s

1500–1749 4,500 59% 2.3s

1750–1999 3,235 52% 2.5s

2000+ 16,162 50% 2.5s

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): LCP 1.2s. At the high end (2000+ms): LCP 2.5s. computed

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

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 35685 71370

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

Good (≤2.5s) Needs improvement Poor (>4s) Site count

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

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

Document lifecycle (lab) — dom completeSitesPassing LCPLCP

0–499 71,370 91% 1.2s

500–999 48,257 88% 1.5s

1000–1499 23,177 80% 1.8s

1500–1999 12,516 71% 2.0s

2000–2499 7,351 62% 2.2s

2500–2999 4,705 56% 2.3s

3000+ 17,985 61% 2.1s

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): LCP 1.2s. At the high end (3000+ms): LCP 2.1s. computed

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

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

0ms 750ms 1500ms 2250ms 3000ms

2.5s

0 35483 70966

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

Good (≤2.5s) Needs improvement Poor (>4s) Site count

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

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

Document lifecycle (lab) — loadSitesPassing LCPLCP

0–499 70,966 91% 1.2s

500–999 48,205 88% 1.5s

1000–1499 23,226 80% 1.8s

1500–1999 12,590 71% 2.0s

2000–2499 7,445 63% 2.2s

2500–2999 4,759 56% 2.3s

3000+ 18,170 61% 2.1s

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): LCP 1.2s. At the high end (3000+ms): LCP 2.1s. computed

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

Document lifecycle (lab) correlates with the LCP. DOM interactive separates passing sites from failing sites the most. Where the DOM interactive is low, 90% of sites pass the LCP. Where it is high, 50% 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 189,915 sites, representing millions of real page loads · How we measured