Shopify connection and preload hints and the Core Web Vitals
76.6% of audited sites (6,320) combine preconnect and preload hints (97% good LCP, 1.3s median), while 2.3% rely solely on legacy dns-prefetch hints (97% good LCP, 1.1s median).
76.6% of Shopify sites use both preconnect and preload hints connection and preload hints, and 97% of those sites have a good LCP, against 97% of all Shopify sites.
LCP pass rate
Sites with both preconnect and preload hints connection and preload hints have a good LCP most often: 97%, against 97% of all Shopify sites. Sites with preconnect hints without preload connection hints have it least often, at 96%.
Connection and preload hints usage
Both preconnect and preload hints is the most used: 76.6% of Shopify sites.
The four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between both preconnect and preload hints and preconnect hints without preload sits in resource load delay: 614 ms median for both preconnect and preload hints against 692 ms for preconnect hints without preload. Overall median field LCP is 1.3s for both preconnect and preload hints (TTFB 302 ms, load delay 614 ms, load duration 153 ms, render delay 298 ms) versus 1.3s for preconnect hints without preload.
Connection and preload hints per framework
Vue sets the connection and preload hints to both preconnect and preload hints on 80% of its sites, and 97% of Vue sites have a good LCP, against 97% of all sites.
Connection and preload hints or the framework
Does the framework explain the connection and preload hints difference?
On jQuery, 96% of sites with both preconnect and preload hints connection and preload hints have a good LCP, against 94% of jQuery sites with preconnect hints without preload. Within jQuery, sites with both preconnect and preload hints and preconnect hints without preload have a good LCP about equally often. On Vue, 97% of sites with both preconnect and preload hints connection and preload hints have a good LCP, against 92% of Vue sites with preconnect hints without preload. Within Vue, sites with both preconnect and preload hints and preconnect hints without preload have a good LCP about equally often.
Why targeted preload and preconnect beat legacy dns-prefetch
dns-prefetch only resolves the domain name, leaving TCP and TLS handshakes on the critical path. Pairing preconnect on critical asset CDNs with preload on the LCP image eliminates both connection and discovery delay. Across 6,320 sites (76.6%) pairing preconnect and preload, 97% pass field LCP (1.3s median), compared with 97% (1.1s median) on the 2.3% using dns-prefetch alone.
Understanding connection and preload hints
Use <link rel="preload"> for late-discovered hero images or critical fonts, and limit <link rel="preconnect"> to the 2 to 4 third-party origins needed on the critical path. Across all audited sites, 76.6% combine preconnect and preload (97% good LCP, 1.3s median) versus 2.3% with dns-prefetch only (97% good LCP, 1.1s median).
By Arjen Karel · 8,246 crawled Shopify sites (3,818 with desktop Chrome field data, October 2026). How we measured.