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).

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices field outcomes · WordPress sites only
WordPress Scoped to 63,295 sites out of 203,892 analyzed (cms) Compare with all sites →

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.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field data · 63,291 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
1

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%.

SitesGood, needs improvement, poor LCPMedian
All WordPress sites60,85570%1.9s
Under 350ms DOMComplete 12.6%7,57289%1.3s
350 to 700ms DOMComplete 21.6%13,14886%1.5s
700 to 1,500ms DOMComplete 31.6%19,21176%1.9s
Over 1,500ms DOMComplete 34.2%20,92049%2.5s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field data · 63,291 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
2

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.

Over 1,500ms DOMComplete 34.2% 700 to 1,500ms DOMComplete 31.6% 350 to 700ms DOMComplete 21.6% Under 350ms DOMComplete 12.6%
Over 1,500ms DOMComplete 34.2% 700 to 1,500ms DOMComplete 31.6% 350 to 700ms DOMComplete 21.6% Under 350ms DOMComplete 12.6%
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field data · 63,291 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
3

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.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
WordPress sites with document lifecycle milestones 43,6181127 ms340 ms340 mslab 340 ms1.9s
Under 350ms DOMComplete 5,216691 ms252 mslab 252 ms1.3s
350 to 700ms DOMComplete 9,267797 ms290 ms290 mslab 290 ms1.5s
700 to 1,500ms DOMComplete 13,7501102 ms345 ms345 mslab 345 ms1.9s
Over 1,500ms DOMComplete 15,3851621 ms407 ms407 mslab 407 ms2.5s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field data · 63,291 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
4

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.

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%70%
Alpine 380 sitesOver 1,500ms DOMComplete 33%700 to 1,500ms DOMComplete 31%350 to 700ms DOMComplete 24%Under 350ms DOMComplete 12%80%
jQuery 60,310 sitesOver 1,500ms DOMComplete 35%700 to 1,500ms DOMComplete 32%350 to 700ms DOMComplete 21%Under 350ms DOMComplete 11%69%
Vue 4,844 sitesOver 1,500ms DOMComplete 38%700 to 1,500ms DOMComplete 32%350 to 700ms DOMComplete 20%Under 350ms DOMComplete 10%68%
React 2,233 sitesOver 1,500ms DOMComplete 47%700 to 1,500ms DOMComplete 27%350 to 700ms DOMComplete 17%61%
Over 1,500ms DOMComplete 700 to 1,500ms DOMComplete 350 to 700ms DOMComplete Under 350ms DOMComplete
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field data · 63,291 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
5

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.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field data · 63,291 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
6

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).

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field data · 63,291 sites with document lifecycle milestonesBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Total Blocking Time (lab) → Main-thread CPU (lab) → Lab paint timeline → 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