Shopify LCP image origin and the Core Web Vitals
Serving the hero image from your own domain versus an external image CDN: how a separate connection adds 82 ms of resource load delay (670 ms vs 588 ms) and when <link rel="preconnect"> pays it back.
94.1% of Shopify sites use first-party LCP image hosting, and 96% of those sites have a good LCP, against 96% of all Shopify sites.
LCP pass rate
Sites with first-party LCP image hosting have a good LCP most often: 96%, against 96% of all Shopify sites. Sites with third-party image hosting have it least often, at 90%.
LCP image hosting usage
First-party is the most used: 94.1% of Shopify sites.
Where third-party LCP images lose and win time: the four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between first-party and third-party sits in resource load delay: 588 ms median for first-party against 670 ms for third-party. Overall median field LCP is 1.3s for first-party (TTFB 387 ms, load delay 588 ms, load duration 211 ms, render delay 289 ms) versus 1.5s for third-party.
LCP image origin combined with preconnect and priority hints
Combining first-party with Highprio reaches 97% good LCP across 2,073 sites (521 ms median load delay). At the other end, third-party paired with None sits at 90% across 246 sites (640 ms median load delay).
| Image origin | No priority hint | <link rel="preconnect"> | fetchpriority="high" | <link rel="preload"> |
|---|---|---|---|---|
| Same-origin / first-party | 96% 4,514 sites | 96% 46 sites | 97% 2,129 sites | few sites |
| Third-party domain | 90% 252 sites | 91% 123 sites | 90% 42 sites | few sites |
LCP image hosting per framework
Vue sets the LCP image hosting to first-party on 93% of its sites, and 95% of Vue sites have a good LCP, against 96% of all sites.
Vue 819 sitesSame-origin / first-party 93%95%
jQuery 2,748 sitesSame-origin / first-party 93%94%LCP image origin or the framework
Does the framework explain the LCP image hosting difference?
On jQuery, 94% of sites with first-party LCP image hosting have a good LCP, against 86% of jQuery sites with third-party. Within jQuery, sites with first-party have a good LCP more often. On Vue, 96% of sites with first-party LCP image hosting have a good LCP, against 88% of Vue sites with third-party. Within Vue, sites with first-party have a good LCP more often.
Why third-party hero images pay a connection tax in resource load delay
When the LCP image lives on the same origin as the HTML document, the browser reuses the open HTTP/2 or HTTP/3 connection immediately. When the image sits on a separate domain, Chrome must resolve DNS, complete a TCP or QUIC handshake, and negotiate TLS before requesting the first image byte. That handshake shows up directly in Chrome's field data: third-party LCP images have a 670 ms median resource load delay compared with 588 ms for first-party images (82 ms slower to start), even though dedicated image CDNs finish the download slightly faster (197 ms vs 211 ms).
Understanding LCP image origin
Serve your hero banner from Shopify's built-in first-party CDN path (/cdn/shop/files/...) instead of an external host. Across Shopify stores, 94.1% use Shopify's first-party CDN path and reach 96% good LCP (1.3s median), while stores loading the hero from a third-party domain drop to 90% good LCP (1.5s median).
By Arjen Karel · 8,246 crawled Shopify sites (8,062 with all devices Chrome field data, 7,125 sites with LCP image hosting, October 2026). How we measured.