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 60 ms of resource load delay (686 ms vs 626 ms) and when <link rel="preconnect"> pays it back.
94.1% of Shopify sites use first-party LCP image hosting, and 97% of those sites have a good LCP, against 97% of all Shopify sites.
LCP pass rate
Sites with first-party LCP image hosting have a good LCP most often: 97%, against 97% of all Shopify sites. Sites with third-party image hosting have it least often, at 92%.
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: 626 ms median for first-party against 686 ms for third-party. Overall median field LCP is 1.3s for first-party (TTFB 302 ms, load delay 626 ms, load duration 153 ms, render delay 300 ms) versus 1.5s for third-party.
LCP image origin combined with preconnect and priority hints
Combining first-party with None reaches 97% good LCP across 2,024 sites (655 ms median load delay). At the other end, third-party paired with None sits at 94% across 126 sites (638 ms median load delay).
| Image origin | No priority hint | <link rel="preconnect"> | fetchpriority="high" | <link rel="preload"> |
|---|---|---|---|---|
| Same-origin / first-party | 97% 4,514 sites | 91% 46 sites | 97% 2,129 sites | few sites |
| Third-party domain | 94% 252 sites | 89% 123 sites | 92% 42 sites | few sites |
LCP image hosting per framework
Vue sets the LCP image hosting to first-party on 93% of its sites, and 97% of Vue sites have a good LCP, against 97% of all sites.
Vue 819 sitesSame-origin / first-party 93%97%
jQuery 2,748 sitesSame-origin / first-party 93%95%LCP image origin or the framework
Does the framework explain the LCP image hosting difference?
On jQuery, 95% of sites with first-party LCP image hosting have a good LCP, against 90% of jQuery sites with third-party. Within jQuery, sites with first-party and third-party have a good LCP about equally 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 686 ms median resource load delay compared with 626 ms for first-party images (60 ms slower to start), even though dedicated image CDNs finish the download slightly faster (150 ms vs 153 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 97% good LCP (1.3s median), while stores loading the hero from a third-party domain drop to 92% good LCP (1.4s median).
By Arjen Karel · 8,246 crawled Shopify sites (3,818 with desktop Chrome field data, 7,125 sites with LCP image hosting, October 2026). How we measured.