WordPress document lifecycle milestones and the Core Web Vitals
12.6% of audited sites (7,949) reach DOMComplete in under 350ms and pass field LCP at 89% (1.3s median), whereas the 34.2% taking over 1,500ms pass at 49% (2.5s median).
12.6% of WordPress sites use under 350ms DOMComplete document lifecycle milestones, and 89% of those sites have a good LCP, against 70% of all WordPress sites.
LCP pass rate
Sites with under 350ms DOMComplete document lifecycle milestones have a good LCP most often: 89%, against 70% of all WordPress sites. Sites with over 1,500ms DOMComplete DOMComplete time have it least often, at 49%.
Document lifecycle milestones usage
Over 1,500ms DOMComplete is the most used: 34.2% of WordPress sites. Under 350ms DOMComplete is 12.6% of WordPress 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): 691 ms median for under 350ms DOMComplete against 1621 ms for over 1,500ms DOMComplete. Overall median field LCP is 1.3s for under 350ms DOMComplete (TTFB 691 ms, load delay 252 ms, load duration 151 ms, render delay 217 ms) versus 2.5s for over 1,500ms DOMComplete.
Document lifecycle milestones per framework
On jQuery, 35% of sites use over 1,500ms DOMComplete document lifecycle milestones, and 69% of jQuery sites have a good LCP, against 70% of all sites. On Vue, 38% of sites use over 1,500ms DOMComplete, and 68% of Vue sites have a good LCP.
Document lifecycle milestones or the framework
Does the framework explain the document lifecycle milestones difference?
On jQuery, 87% of sites with under 350ms DOMComplete document lifecycle milestones have a good LCP, against 48% of jQuery sites with over 1,500ms DOMComplete. Within jQuery, sites with under 350ms DOMComplete have a good LCP more often. On Vue, 87% of sites with under 350ms DOMComplete document lifecycle milestones have a good LCP, against 46% of Vue sites with over 1,500ms DOMComplete. Within Vue, 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 7,949 sites (12.6%) reaching DOMComplete in under 350ms, 89% pass field LCP at a 1.3s median, compared with 49% (2.5s median) on the 34.2% (21,660) exceeding 1,500ms.
Understanding document lifecycle milestones
Defer non-critical plugin scripts and lazy-load offscreen images and iframes so synchronous subresources do not hold back DOMComplete. On WordPress, 12.6% of sites finish DOMComplete under 350ms (89% good LCP) while 34.2% exceed 1,500ms (49% good LCP).
By Arjen Karel · 63,295 crawled WordPress sites (60,855 with all devices Chrome field data, 63,291 sites with document lifecycle milestones, October 2026). How we measured.