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

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

2

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

0.00 0.04 0.08 0.11 0.15

0.1

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 (≤0.1) Needs improvement Poor (>0.25) Site count

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

3

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

Document lifecycle (lab) — dom interactiveSitesPassing CLSCLS

0 583 92% 0.00

9–17 114 88% 0.00

18–35 1,513 83% 0.00

36–73 7,509 84% 0.00

74–151 23,531 88% 0.00

152–311 45,538 89% 0.00

312–642 45,134 88% 0.00

643–1327 33,249 88% 0.00

1328–2742 17,561 87% 0.01

2743–5664 6,721 84% 0.01

>p98 3,690 86% 0.00

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): CLS 0.00. At the high end (>p98): CLS 0.00. computed

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

4

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

0.00 0.04 0.08 0.11 0.15

0.1

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 (≤0.1) Needs improvement Poor (>0.25) Site count

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

5

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

Document lifecycle (lab) — dom completeSitesPassing CLSCLS

0 1,449 90% 0.00

12–23 185 89% 0.00

24–50 1,410 90% 0.00

51–107 4,541 90% 0.00

108–229 17,845 90% 0.00

230–493 44,990 90% 0.00

494–1059 52,670 88% 0.00

1060–2277 36,554 86% 0.01

2278–4893 16,497 85% 0.01

4894–10516 5,327 83% 0.01

>p98 3,674 85% 0.01

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): CLS 0.00. At the high end (>p98): CLS 0.01. computed

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

6

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

0.00 0.04 0.08 0.11 0.15

0.1

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 (≤0.1) Needs improvement Poor (>0.25) Site count

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

7

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

Document lifecycle (lab) — loadSitesPassing CLSCLS

0 1,468 90% 0.00

12–23 185 89% 0.00

24–50 1,402 90% 0.00

51–107 4,522 90% 0.00

108–230 17,855 90% 0.00

231–494 44,714 90% 0.00

495–1061 52,586 88% 0.00

1062–2281 36,689 86% 0.01

2282–4903 16,644 85% 0.01

4904–10541 5,404 83% 0.01

>p98 3,673 85% 0.01

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): CLS 0.00. At the high end (>p98): CLS 0.01. computed

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

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