Shopify web font hosting sources and the Core Web Vitals
92.5% of font-using sites (7,462) self-host fonts on their own origin (96% good LCP, 1.3s median) and 51.8% use dedicated platform/CDN font hosts (96% good LCP), while the 32.3% loading from Google Fonts drop to 94% good LCP (1.5s median).
92.5% of Shopify sites use self-hosted fonts web font hosting source, and 96% of those sites have a good LCP, against 96% of all Shopify sites.
LCP pass rate
Sites with self-hosted fonts web font hosting source have a good LCP most often: 96%, against 96% of all Shopify sites. Sites with Adobe Fonts font source have it least often, at 91%.
Web font hosting source usage
Self-hosted fonts is the most used: 92.5% of Shopify sites.
LCP phase breakdown by web font hosting source
Across the four LCP sub-parts in Chrome's field data, the largest gap between self-hosted fonts and Adobe Fonts sits in resource load delay: 587 ms median for self-hosted fonts against 700 ms for Adobe Fonts. Overall median field LCP is 1.3s for self-hosted fonts (TTFB 388 ms, load delay 587 ms, load duration 209 ms, render delay 297 ms) versus 1.6s for Adobe Fonts.
Web font hosting source per framework
Vue sets the web font hosting source to self-hosted fonts on 92% of its sites, and 95% of Vue sites have a good LCP, against 96% of all sites.
Vue 925 sitesSelf-hosted (same origin) 92%Dedicated CDN / third-party font host 73%Google Fonts (fonts.googleapis.com / gstatic) 42%95%
jQuery 3,091 sitesSelf-hosted (same origin) 89%Dedicated CDN / third-party font host 53%Google Fonts (fonts.googleapis.com / gstatic) 41%94%Font hosting source or the framework
Does the framework explain the web font hosting source difference?
On jQuery, 94% of sites with self-hosted fonts web font hosting source have a good LCP, against 93% of jQuery sites with CDN-hosted fonts. Within jQuery, sites with self-hosted fonts and CDN-hosted fonts have a good LCP about equally often. On Vue, 96% of sites with self-hosted fonts web font hosting source have a good LCP, against 95% of Vue sites with CDN-hosted fonts. Within Vue, sites with self-hosted fonts and CDN-hosted fonts have a good LCP about equally often.
Why external Google Fonts and Adobe Fonts cost extra connection round-trips
Since Chrome 86 partitioned the HTTP cache by top-level site, loading fonts from fonts.googleapis.com and fonts.gstatic.com no longer benefits from a shared cross-site cache and instead requires two cross-origin connection setups (one for CSS, one for WOFF2 files). Across 2,606 sites (32.3%) loading Google Fonts, good LCP is 94% (1.5s median), and across 255 sites (3.2%) loading Adobe Fonts it is 91% (1.6s median). Self-hosted fonts (92.5%) reach 96% good LCP (1.3s median) and dedicated platform CDNs (51.8%) reach 96% (1.4s median).
Understanding web font hosting sources
Self-host WOFF2 font files on your primary domain or CDN edge so font requests reuse the main HTTP/2 or HTTP/3 connection without extra DNS and TLS handshakes to fonts.googleapis.com or use.typekit.net. Across all font-using sites, 92.5% self-host fonts (96% good LCP) while 32.3% load Google Fonts (94% good LCP).
By Arjen Karel · 8,246 crawled Shopify sites (8,062 with all devices Chrome field data, 8,067 sites with web font hosting source, October 2026). How we measured.