Document lifecycle milestones on React sites
48.2% of audited sites (4,617) reach DOMComplete in under 350ms and pass field LCP at 90% (1.2s median), whereas the 17.5% taking over 1,500ms pass at 58% (2.2s median).
48.2% of React sites use under 350ms DOMComplete document lifecycle milestones, and 90% of those sites have a good LCP, against 79% of all React sites.
LCP pass rate
Sites with under 350ms DOMComplete document lifecycle milestones have a good LCP most often: 90%, against 79% of all React sites. Sites with over 1,500ms DOMComplete DOMComplete time have it least often, at 58%.
Document lifecycle milestones usage
Under 350ms DOMComplete is the most used: 48.2% of React sites.
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): 362 ms median for under 350ms DOMComplete against 1252 ms for over 1,500ms DOMComplete. Overall median field LCP is 1.2s for under 350ms DOMComplete (TTFB 362 ms, load delay 425 ms, load duration 197 ms, render delay 149 ms) versus 2.2s for over 1,500ms DOMComplete.
Document lifecycle milestones per platform
Wix sets the document lifecycle milestones to under 350ms DOMComplete on 67% of its sites, and 92% of Wix sites have a good LCP, against 79% of all sites.
Wix 5,824 sitesUnder 350ms DOMComplete 67%350 to 700ms DOMComplete 20%92%
WordPress 2,342 sitesOver 1,500ms DOMComplete 47%700 to 1,500ms DOMComplete 26%350 to 700ms DOMComplete 17%66%Document lifecycle milestones or the platform
Does the platform explain the document lifecycle milestones difference?
On Wix, 94% of sites with under 350ms DOMComplete document lifecycle milestones have a good LCP, against 91% of Wix sites with 350 to 700ms DOMComplete. Within Wix, sites with under 350ms DOMComplete and 350 to 700ms DOMComplete have a good LCP about equally often. On WordPress, 76% of sites with under 350ms DOMComplete document lifecycle milestones have a good LCP, against 78% of WordPress sites with 350 to 700ms DOMComplete. Within WordPress, sites with under 350ms DOMComplete and 350 to 700ms DOMComplete have a good LCP about equally often.
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 4,617 sites (48.2%) reaching DOMComplete in under 350ms, 90% pass field LCP at a 1.2s median, compared with 58% (2.2s median) on the 17.5% (1,676) exceeding 1,500ms.
Understanding document lifecycle milestones
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, 48.2% finish DOMComplete under 350ms (90% good LCP, 1.2s median) versus 17.5% above 1,500ms (58% good LCP, 2.2s median).
By Arjen Karel · 9,570 crawled React sites (1,979 with desktop Chrome field data, October 2026). How we measured.