Document lifecycle (lab)

Lab document lifecycle: DOM interactive, DOM complete, load event.

Field data PhoneDesktopAll Scope All sites Q1 2026 edition · All devices field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for Document lifecycle (lab)

Lab document lifecycle: DOM interactive, DOM complete, load event.

387ms
DOM interactive
on the typical page
688ms
DOM complete
on the typical page
692ms
load event
on the typical page
94,847
sites measured
all-device field data

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

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices 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 11757 23514
0 4–8 9–16 17–33 34–67 68–135 136–273 274–552 553–1115 1116–2253 2254–4555 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · all devices 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 317 99% 83ms
17–33 532 83% 96ms
34–67 3,203 83% 100ms
68–135 9,427 91% 86ms
136–273 21,973 95% 83ms
274–552 23,514 96% 86ms
553–1115 18,396 97% 87ms
1116–2253 11,156 96% 89ms
2254–4555 4,432 96% 90ms
>p98 1,891 95% 92ms
Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — dom interactive 387ms. p75 850ms. p99 6.7s. At the low end (0ms): INP 83ms. At the high end (>p98): INP 92ms. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices 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 13517 27034
0 5–11 12–22 23–47 48–100 101–210 211–444 445–938 939–1981 1982–4184 4185–8836 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · all devices 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 750 98% 86ms
23–47 543 87% 89ms
48–100 1,643 86% 85ms
101–210 7,250 90% 83ms
211–444 21,237 95% 81ms
445–938 27,034 96% 85ms
939–1981 20,747 96% 89ms
1982–4184 9,965 96% 93ms
4185–8836 3,789 93% 95ms
>p98 1,882 92% 96ms
Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — dom complete 688ms. p75 1.4s. p99 15.0s. At the low end (0ms): INP 86ms. At the high end (>p98): INP 96ms. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices 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 13496 26991
0 5–11 12–22 23–47 48–100 101–211 212–446 447–943 944–1993 1994–4214 4215–8907 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · all devices 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 758 97% 86ms
23–47 542 87% 89ms
48–100 1,635 87% 85ms
101–211 7,268 90% 83ms
212–446 21,197 95% 81ms
447–943 26,991 96% 85ms
944–1993 20,756 96% 89ms
1994–4214 10,012 96% 93ms
4215–8907 3,800 93% 95ms
>p98 1,881 92% 96ms
Good Needs Improvement Poor Faded rows: under 100 sites

Document lifecycle (lab) — load 692ms. p75 1.4s. p99 15.1s. At the low end (0ms): INP 86ms. At the high end (>p98): INP 96ms. computed

The State of Web Vitals · Q1 2026 · 94,910 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 INP. DOM complete separates passing sites from failing sites the most. Where the DOM complete is low, 98% of sites pass the INP. Where it is high, 92% do. The decline is gradual. There is no point where sites suddenly start failing.

Related signals Total Blocking Time (lab) → Main-thread CPU (lab) → Lab paint timeline → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured