Web font hosting sources and the Core Web Vitals
70.6% of font-using sites (130,081) self-host fonts on their own origin (85% good LCP, 1.4s median) and 31.3% use dedicated platform/CDN font hosts (86% good LCP), while the 41.0% loading from Google Fonts drop to 84% good LCP (1.5s median).
4.5% of sites use Adobe Fonts web font hosting source, and 87% of those sites have a good LCP, against 86% of all sites.
LCP pass rate
Sites with Adobe Fonts web font hosting source have a good LCP most often: 87%, against 86% of all sites. Sites with Google Fonts font source have it least often, at 84%.
Web font hosting source usage
Self-hosted fonts is the most used: 70.6% of sites. Adobe Fonts is 4.5% of sites.
LCP phase breakdown by web font hosting source
Across the four LCP sub-parts in Chrome's field data, the largest gap between Adobe Fonts and Google Fonts sits in time to first byte (TTFB): 593 ms median for Adobe Fonts against 627 ms for Google Fonts. Overall median field LCP is 1.5s for Adobe Fonts (TTFB 593 ms, load delay 296 ms, load duration 126 ms, render delay 223 ms) versus 1.5s for Google Fonts.
Understanding web font hosting sources
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 75,476 sites (41.0%) loading Google Fonts, good LCP is 84% (1.5s median), and across 8,267 sites (4.5%) loading Adobe Fonts it is 87% (1.5s median). Self-hosted fonts (70.6%) reach 85% good LCP (1.4s median) and dedicated platform CDNs (31.3%) reach 86% (1.4s median).
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, 70.6% self-host fonts (85% good LCP) while 41.0% load Google Fonts (84% good LCP).
How web font hosting source plays out per platform
What the field data shows when you isolate a single CMS or framework.
Shopify 8,390 stores 92.5% of Shopify stores serve fonts from their first-party domain (97% good LCP vs 95% with Google Fonts).
Shopify's font_face filter serves theme fonts from the storefront's /cdn/fonts/ path. Across Shopify, 92.5% of stores serve first-party fonts (97% good LCP, 1.3s median), 32.3% load Google Fonts (95% good LCP, 1.4s median), and 3.1% load Adobe Fonts (96%).
React & Next.js 9,431 sites React & Next.js sites loading external Google Fonts (18.9%) pass LCP at 65% vs 85% on dedicated CDNs.
Across 9,431 font-using React sites, 77.1% serve fonts from external CDNs (85% good LCP, 1.4s median) and 18.9% load Google Fonts at runtime (65% good LCP, 2.0s median, 20 percentage points apart).
By Arjen Karel · 210,902 crawled sites (69,745 with desktop Chrome field data, 184,141 sites with web font hosting source, October 2026). How we measured.