WordPress document lifecycle milestones and the Core Web Vitals

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

Over 1,500ms DOMComplete is the most used: 34.2% of WordPress sites. 350 to 700ms DOMComplete is 21.6% of WordPress sites.

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): 699 ms median for 350 to 700ms DOMComplete against 1396 ms for over 1,500ms DOMComplete. Overall median field LCP is 1.4s for 350 to 700ms DOMComplete (TTFB 699 ms, load delay 250 ms, load duration 127 ms, render delay 212 ms) versus 2.2s for over 1,500ms DOMComplete.

On jQuery, 35% of sites use over 1,500ms DOMComplete document lifecycle milestones, and 75% of jQuery sites have a good LCP, against 76% of all sites. On Vue, 38% of sites use over 1,500ms DOMComplete, and 75% of Vue sites have a good LCP.

FrameworkDocument lifecycle milestones on its sitesGood LCP

WordPress sites with document lifecycle milestones 63,291 sitesOver 1,500ms DOMComplete 34%700 to 1,500ms DOMComplete 32%350 to 700ms DOMComplete 22%Under 350ms DOMComplete 13%76%

Alpine 380 sitesOver 1,500ms DOMComplete 33%700 to 1,500ms DOMComplete 31%350 to 700ms DOMComplete 24%Under 350ms DOMComplete 12%82%

jQuery 60,310 sitesOver 1,500ms DOMComplete 35%700 to 1,500ms DOMComplete 32%350 to 700ms DOMComplete 21%Under 350ms DOMComplete 11%75%

Vue 4,844 sitesOver 1,500ms DOMComplete 38%700 to 1,500ms DOMComplete 32%350 to 700ms DOMComplete 20%Under 350ms DOMComplete 10%75%

React 2,233 sitesOver 1,500ms DOMComplete 47%700 to 1,500ms DOMComplete 27%350 to 700ms DOMComplete 17%66%

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

Does the framework explain the document lifecycle milestones difference?

On jQuery, 89% of sites with 350 to 700ms DOMComplete document lifecycle milestones have a good LCP, against 59% of jQuery sites with over 1,500ms DOMComplete. Within jQuery, sites with 350 to 700ms DOMComplete have a good LCP more often. On Vue, 88% of sites with 350 to 700ms DOMComplete document lifecycle milestones have a good LCP, against 58% of Vue sites with over 1,500ms DOMComplete. Within Vue, sites with 350 to 700ms 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 7,949 sites (12.6%) reaching DOMComplete in under 350ms, 88% pass field LCP at a 1.2s median, compared with 59% (2.2s median) on the 34.2% (21,660) exceeding 1,500ms.