Document lifecycle milestones on Wix sites

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

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 350 to 700ms DOMComplete sits in time to first byte (TTFB): 300 ms median for under 350ms DOMComplete against 391 ms for 350 to 700ms DOMComplete. Overall median field LCP is 1.2s for under 350ms DOMComplete (TTFB 300 ms, load delay 459 ms, load duration 256 ms, render delay 140 ms) versus 1.3s for 350 to 700ms DOMComplete.

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

FrameworkDocument lifecycle milestones on its sitesGood LCP

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

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

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