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 LCP site count and median LCP at each level of document lifecycle (lab) — dom interactive

0ms 750ms 1500ms 2250ms 3000ms

2.5s

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 (≤2.5s) Needs improvement Poor (>4s) Site count

The State of Web Vitals · Q2 2026 · 189,915 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 583 76% 1.8s

9–17 114 97% 1.1s

18–35 1,513 85% 1.3s

36–73 7,509 88% 1.2s

74–151 23,531 91% 1.1s

152–311 45,538 92% 1.2s

312–642 45,134 90% 1.3s

643–1327 33,249 86% 1.6s

1328–2742 17,561 68% 2.1s

2743–5664 6,721 56% 2.3s

>p98 3,690 71% 1.7s

Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — dom interactive 384ms. p75 858ms. p99 12.4s. Spearman with LCP r = +0.34. At the low end (0ms): LCP 1.8s. At the high end (>p98): LCP 1.7s. computed

The State of Web Vitals · Q2 2026 · 189,915 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 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 (≤2.5s) Needs improvement Poor (>4s) Site count

The State of Web Vitals · Q2 2026 · 189,915 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 1,449 79% 1.6s

12–23 185 88% 1.1s

24–50 1,410 85% 1.2s

51–107 4,541 89% 1.1s

108–229 17,845 91% 1.0s

230–493 44,990 92% 1.1s

494–1059 52,670 90% 1.3s

1060–2277 36,554 83% 1.6s

2278–4893 16,497 69% 1.9s

4894–10516 5,327 70% 1.8s

>p98 3,674 79% 1.5s

Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — dom complete 671ms. p75 1.4s. p99 24.1s. Spearman with LCP r = +0.33. At the low end (0ms): LCP 1.6s. At the high end (>p98): LCP 1.5s. computed

The State of Web Vitals · Q2 2026 · 189,915 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 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 (≤2.5s) Needs improvement Poor (>4s) Site count

The State of Web Vitals · Q2 2026 · 189,915 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 1,468 79% 1.6s

12–23 185 88% 1.1s

24–50 1,402 85% 1.2s

51–107 4,522 89% 1.1s

108–230 17,855 91% 1.0s

231–494 44,714 92% 1.1s

495–1061 52,586 90% 1.3s

1062–2281 36,689 83% 1.6s

2282–4903 16,644 69% 1.9s

4904–10541 5,404 70% 1.8s

>p98 3,673 79% 1.5s

Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — load 676ms. p75 1.4s. p99 24.1s. Spearman with LCP r = +0.33. At the low end (0ms): LCP 1.6s. At the high end (>p98): LCP 1.5s. 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?

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

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