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 90% (1.1s median), whereas the 22.2% taking over 1,500ms pass at 74% (1.8s median).

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

26.0% of sites use 350 to 700ms DOMComplete document lifecycle milestones, and 91% of those sites have a good LCP, against 86% of all sites.

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

LCP pass rate

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

SitesGood, needs improvement, poor LCPMedian
All sites69,74586%1.4s
350 to 700ms DOMComplete 26.0%17,76291%1.2s
Under 350ms DOMComplete 26.4%16,70290%1.1s
700 to 1,500ms DOMComplete 25.4%18,36288%1.5s
Over 1,500ms DOMComplete 22.2%16,86374%1.8s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop 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. 350 to 700ms DOMComplete is 26.0% 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 · 69,745 with desktop 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 350 to 700ms DOMComplete and over 1,500ms DOMComplete sits in time to first byte (TTFB): 476 ms median for 350 to 700ms DOMComplete against 881 ms for over 1,500ms DOMComplete. Overall median field LCP is 1.2s for 350 to 700ms DOMComplete (TTFB 476 ms, load delay 247 ms, load duration 107 ms, render delay 182 ms) versus 1.8s for over 1,500ms DOMComplete.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Sites with document lifecycle milestones 50,937571 ms274 ms191 ms274 mslab 316 ms1.4s
Under 350ms DOMComplete 11,032394 ms224 ms224 mslab 254 ms1.1s
350 to 700ms DOMComplete 13,015476 ms247 ms182 ms247 mslab 286 ms1.2s
700 to 1,500ms DOMComplete 13,956649 ms289 ms202 ms289 mslab 335 ms1.5s
Over 1,500ms DOMComplete 12,934881 ms336 ms218 ms336 mslab 391 ms1.8s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop 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, 90% pass field LCP at a 1.1s median, compared with 74% (1.8s 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 (90% good LCP, 1.1s median) versus 22.2% above 1,500ms (74% good LCP, 1.8s median).

The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop 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
88% vs 59% good LCP (< 350ms vs > 1.5s DOMComplete)

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

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

Explore WordPress document lifecycle data →
Shopify 8,573 sites
98% vs 94% 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 (98% field LCP pass rate), 31% exceed 1,500ms (94%), and 24% finish in 350 to 700ms (98% pass rate, 1.1s median).

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

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

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

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