Document lifecycle milestones on Wix sites

Sites with under 350ms DOMComplete document lifecycle milestones have a good LCP most often: 96%, against 94% of all Wix sites. Sites with 700 to 1,500ms DOMComplete DOMComplete time have it least often, at 89%.

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

Across the four LCP sub-parts in Chrome's field data, the largest gap between under 350ms DOMComplete and 700 to 1,500ms DOMComplete sits in resource load delay: 435 ms median for under 350ms DOMComplete against 496 ms for 700 to 1,500ms DOMComplete. Overall median field LCP is 1.1s for under 350ms DOMComplete (TTFB 408 ms, load delay 435 ms, load duration 131 ms, render delay 152 ms) versus 1.4s for 700 to 1,500ms DOMComplete.

React sets the document lifecycle milestones to under 350ms DOMComplete on 67% of its sites, and 94% of React sites have a good LCP, against 94% of all sites.

FrameworkDocument lifecycle milestones on its sitesGood LCP

All Wix sites 5,621 sitesUnder 350ms DOMComplete 67%350 to 700ms DOMComplete 20%94%

React 5,620 sitesUnder 350ms DOMComplete 67%350 to 700ms DOMComplete 20%94%

Under 350ms DOMComplete 350 to 700ms DOMComplete 700 to 1,500ms DOMComplete Over 1,500ms DOMComplete

Does the framework explain the document lifecycle milestones difference?

On React, 96% of sites with under 350ms DOMComplete document lifecycle milestones have a good LCP, against 93% of React sites with 350 to 700ms DOMComplete. Within React, sites with under 350ms DOMComplete have a good LCP more 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 3,752 sites (66.7%) reaching DOMComplete in under 350ms, 96% pass field LCP at a 1.1s median, compared with 89% (1.4s median) on the 6.0% (335) exceeding 1,500ms.