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
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
2
Distribution & median LCP site count and median LCP at each level of document lifecycle (lab) — dom interactive
0ms
1250ms
2500ms
3750ms
5000ms
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 · phone 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
66%
1.9s
9–17
114
88%
1.3s
18–35
1,513
82%
1.4s
36–73
7,509
85%
1.4s
74–151
23,531
90%
1.2s
152–311
45,538
90%
1.3s
312–642
45,134
87%
1.5s
643–1327
33,249
78%
1.8s
1328–2742
17,561
55%
2.4s
2743–5664
6,721
48%
2.6s
>p98
3,690
63%
2.0s
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.37. At the low end (0ms): LCP 1.9s. At the high end (>p98): LCP 2.0s. computed
The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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
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 · phone 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
70%
1.8s
12–23
185
88%
1.3s
24–50
1,410
83%
1.4s
51–107
4,541
88%
1.2s
108–229
17,845
91%
1.2s
230–493
44,990
91%
1.3s
494–1059
52,670
86%
1.5s
1060–2277
36,554
73%
1.9s
2278–4893
16,497
59%
2.2s
4894–10516
5,327
60%
2.2s
>p98
3,674
73%
1.8s
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.37. At the low end (0ms): LCP 1.8s. At the high end (>p98): LCP 1.8s. computed
The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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
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 · phone 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
70%
1.8s
12–23
185
88%
1.3s
24–50
1,402
83%
1.4s
51–107
4,522
88%
1.2s
108–230
17,855
91%
1.2s
231–494
44,714
91%
1.3s
495–1061
52,586
87%
1.5s
1062–2281
36,689
74%
1.9s
2282–4903
16,644
59%
2.2s
4904–10541
5,404
60%
2.2s
>p98
3,673
73%
1.8s
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.37. At the low end (0ms): LCP 1.8s. At the high end (>p98): LCP 1.8s. computed
The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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?
Passing LCP barely moves across the range: 66% at one end, 63% at the other. This signal does not separate passing sites from failing ones.
Chrome field data from 189,915 sites, representing millions of real page loads.
How we measured.