Shopify document lifecycle milestones and the Core Web Vitals
3.2% of audited sites (263) reach DOMComplete in under 350ms and pass field LCP at 98% (1.1s median), whereas the 31.3% taking over 1,500ms pass at 93% (1.5s median).
23.7% of Shopify sites use 350 to 700ms DOMComplete document lifecycle milestones, and 98% of those sites have a good LCP, against 96% of all Shopify sites.
LCP pass rate
Sites with 350 to 700ms DOMComplete document lifecycle milestones have a good LCP most often: 98%, against 96% of all Shopify sites. Sites with over 1,500ms DOMComplete DOMComplete time have it least often, at 93%.
Document lifecycle milestones usage
700 to 1,500ms DOMComplete is the most used: 41.8% of Shopify sites. 350 to 700ms DOMComplete is 23.7% of Shopify sites.
The four LCP phases
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 resource load delay: 513 ms median for 350 to 700ms DOMComplete against 677 ms for over 1,500ms DOMComplete. Overall median field LCP is 1.2s for 350 to 700ms DOMComplete (TTFB 358 ms, load delay 513 ms, load duration 206 ms, render delay 234 ms) versus 1.5s for over 1,500ms DOMComplete.
Document lifecycle milestones per framework
On jQuery, 41% of sites use 700 to 1,500ms DOMComplete document lifecycle milestones, and 94% of jQuery sites have a good LCP, against 96% of all sites. On Vue, 45% of sites use over 1,500ms DOMComplete, and 95% of Vue sites have a good LCP.
Document lifecycle milestones or the framework
Does the framework explain the document lifecycle milestones difference?
On jQuery, 97% of sites with 350 to 700ms DOMComplete document lifecycle milestones have a good LCP, against 94% of jQuery sites with 700 to 1,500ms DOMComplete. Within jQuery, sites with 350 to 700ms DOMComplete have a good LCP more often. On Vue, 99% of sites with 350 to 700ms DOMComplete document lifecycle milestones have a good LCP, against 96% of Vue sites with 700 to 1,500ms DOMComplete. Within Vue, sites with 350 to 700ms DOMComplete and 700 to 1,500ms 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 263 sites (3.2%) reaching DOMComplete in under 350ms, 98% pass field LCP at a 1.1s median, compared with 93% (1.5s median) on the 31.3% (2,584) exceeding 1,500ms.
Understanding document lifecycle milestones
Defer non-critical scripts and lazy-load below-the-fold subresources so DOMInteractive and DOMComplete are not held back by slow third-party requests. Across all audited sites, 3.2% finish DOMComplete under 350ms (98% good LCP, 1.1s median) versus 31.3% above 1,500ms (93% good LCP, 1.5s median).
By Arjen Karel · 8,246 crawled Shopify sites (8,062 with all devices Chrome field data, October 2026). How we measured.