Document lifecycle milestones and the Core Web Vitals

26.4% of audited sites (54,420) reach DOMComplete in under 350ms and pass field LCP at 91% (1.2s median), whereas the 22.2% taking over 1,500ms pass at 63% (2.1s median).

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices field outcomes

26.4% of sites use under 350ms DOMComplete document lifecycle milestones, and 91% of those sites have a good LCP, against 82% of all sites.

The State of Web Vitals · October 2026 · 210,902 crawled sites · 196,263 with all devices field data · 206,118 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with under 350ms DOMComplete document lifecycle milestones have a good LCP most often: 91%, against 82% of all sites. Sites with over 1,500ms DOMComplete DOMComplete time have it least often, at 63%.

SitesGood, needs improvement, poor LCPMedian
All sites196,26382%1.5s
Under 350ms DOMComplete 26.4%50,67491%1.2s
350 to 700ms DOMComplete 26.0%51,42390%1.3s
700 to 1,500ms DOMComplete 25.4%50,42683%1.7s
Over 1,500ms DOMComplete 22.2%43,60463%2.1s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · 210,902 crawled sites · 196,263 with all devices field data · 206,118 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Document lifecycle milestones usage

Under 350ms DOMComplete is the most used: 26.4% of sites.

Under 350ms DOMComplete 26.4% 350 to 700ms DOMComplete 26.0% 700 to 1,500ms DOMComplete 25.4% Over 1,500ms DOMComplete 22.2%
Under 350ms DOMComplete 26.4% 350 to 700ms DOMComplete 26.0% 700 to 1,500ms DOMComplete 25.4% Over 1,500ms DOMComplete 22.2%
The State of Web Vitals · October 2026 · 210,902 crawled sites · 196,263 with all devices field data · 206,118 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
3

The four LCP phases

Across the four LCP sub-parts in Chrome's field data, the largest gap between under 350ms DOMComplete and over 1,500ms DOMComplete sits in time to first byte (TTFB): 446 ms median for under 350ms DOMComplete against 1118 ms for over 1,500ms DOMComplete. Overall median field LCP is 1.2s for under 350ms DOMComplete (TTFB 446 ms, load delay 258 ms, load duration 122 ms, render delay 196 ms) versus 2.1s for over 1,500ms DOMComplete.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Sites with document lifecycle milestones 142,245647 ms318 ms224 ms318 mslab 318 ms1.5s
Under 350ms DOMComplete 34,215446 ms258 ms258 mslab 258 ms1.2s
350 to 700ms DOMComplete 37,348552 ms291 ms218 ms291 mslab 291 ms1.3s
700 to 1,500ms DOMComplete 37,671792 ms345 ms233 ms345 mslab 345 ms1.7s
Over 1,500ms DOMComplete 33,0111118 ms394 ms250 ms394 mslab 394 ms2.1s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · 210,902 crawled sites · 196,263 with all devices field data · 206,118 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Understanding document lifecycle milestones

What DOMInteractive and DOMComplete reveal about subresource contention

DOMInteractive marks when HTML parsing finishes and deferred scripts begin executing; DOMComplete waits for all synchronous subresources. Across 54,420 sites (26.4%) reaching DOMComplete in under 350ms, 91% pass field LCP at a 1.2s median, compared with 63% (2.1s median) on the 22.2% (45,850) exceeding 1,500ms.

Defer non-critical scripts and lazy-load below-the-fold subresources so DOMInteractive and DOMComplete are not held back by slow third-party requests. Across all audited sites, 26.4% finish DOMComplete under 350ms (91% good LCP, 1.2s median) versus 22.2% above 1,500ms (63% good LCP, 2.1s median).

The State of Web Vitals · October 2026 · 210,902 crawled sites · 196,263 with all devices field data · 206,118 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
Platform & Framework Takeaways

How document lifecycle milestones plays out per platform

What the field data shows when you isolate a single CMS or framework.

WordPress 65,505 sites
89% vs 48% good LCP (< 350ms vs > 1.5s DOMComplete)

WordPress sites taking over 1,500ms to reach DOMComplete pass LCP 41 points less often than sites under 350ms.

Across WordPress sites, 34% take over 1,500ms to reach DOMComplete in the lab (48% field LCP pass rate, 2.5s median) compared with 89% (1.3s median) on the 13% finishing under 350ms.

Explore WordPress document lifecycle data →
Shopify 8,573 sites
98% vs 93% good LCP (350-700ms vs > 1.5s)

73% of Shopify stores reach DOMComplete after 700ms.

Across Shopify storefronts, 42% reach DOMComplete in 700 to 1,500ms (97% field LCP pass rate), 31% exceed 1,500ms (93%), and 24% finish in 350 to 700ms (98% pass rate, 1.2s median).

Explore Shopify document lifecycle data →
React 9,570 sites
94% vs 56% good LCP (< 350ms vs > 1.5s DOMComplete)

React sites reaching DOMComplete under 350ms pass field LCP 38 points more often than sites over 1,500ms.

Across React sites, 48% reach DOMComplete in under 350ms (94% field LCP pass rate, 1.2s median) and 18% take over 1,500ms (56% pass rate, 2.3s median).

Explore React document lifecycle data →
Wix 5,825 sites
87% sites under 700ms DOMComplete

87% of Wix sites reach DOMComplete in under 700ms.

Across Wix sites, 67% reach DOMComplete in under 350ms (96% field LCP pass rate, 1.1s median), 20% finish in 350 to 700ms (93%), and 6% exceed 1,500ms (89%).

Explore Wix document lifecycle data →
Related signals Total Blocking Time (lab) → Main-thread CPU (lab) → Lab paint timeline → By Arjen Karel · 210,902 crawled sites (196,263 with all devices Chrome field data, 206,118 sites with document lifecycle milestones, October 2026) · How we measured