Web font hosting sources on React sites
26.9% of font-using sites (2,534) self-host fonts on their own origin (64% good LCP, 2.1s median) and 77.1% use dedicated platform/CDN font hosts (90% good LCP), while the 18.9% loading from Google Fonts drop to 65% good LCP (2.0s median).
77.1% of React sites use CDN-hosted fonts web font hosting source, and 90% of those sites have a good LCP, against 85% of all React sites.
LCP pass rate
Sites with CDN-hosted fonts web font hosting source have a good LCP most often: 90%, against 85% of all React sites. Sites with self-hosted fonts font source have it least often, at 64%.
Web font hosting source usage
CDN-hosted fonts is the most used: 77.1% of React sites.
LCP phase breakdown by web font hosting source
Across the four LCP sub-parts in Chrome's field data, the largest gap between CDN-hosted fonts and self-hosted fonts sits in time to first byte (TTFB): 446 ms median for CDN-hosted fonts against 1151 ms for self-hosted fonts. Overall median field LCP is 1.3s for CDN-hosted fonts (TTFB 446 ms, load delay 452 ms, load duration 143 ms, render delay 159 ms) versus 2.1s for self-hosted fonts.
Web font hosting source per platform
Wix sets the web font hosting source to CDN-hosted fonts on 100% of its sites, and 94% of Wix sites have a good LCP, against 85% of all sites. WordPress sets the web font hosting source to self-hosted fonts on 88% of its sites, and 61% of WordPress sites have a good LCP.
Wix 5,801 sitesDedicated CDN / third-party font host 100%94%
WordPress 2,305 sitesSelf-hosted (same origin) 88%Google Fonts (fonts.googleapis.com / gstatic) 48%Dedicated CDN / third-party font host 29%61%Font hosting source or the platform
Does the platform explain the web font hosting source difference?
On Wix, 94% of sites with CDN-hosted fonts web font hosting source have a good LCP, against 90% of Wix sites with Google Fonts. Within Wix, sites with CDN-hosted fonts have a good LCP more often. On WordPress, 60% of sites with CDN-hosted fonts web font hosting source have a good LCP, against 59% of WordPress sites with self-hosted fonts. Within WordPress, sites with CDN-hosted fonts and self-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 1,782 sites (18.9%) loading Google Fonts, good LCP is 65% (2.0s median), and across 150 sites (1.6%) loading Adobe Fonts it is 75% (1.9s median). Self-hosted fonts (26.9%) reach 64% good LCP (2.1s median) and dedicated platform CDNs (77.1%) reach 90% (1.3s 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, 26.9% self-host fonts (64% good LCP) while 18.9% load Google Fonts (65% good LCP).
By Arjen Karel · 9,570 crawled React sites (9,110 with all devices Chrome field data, 9,431 sites with web font hosting source, October 2026). How we measured.