WordPress web font hosting sources and the Core Web Vitals
85.0% of font-using sites (52,250) self-host fonts on their own origin (68% good LCP, 2.0s median) and 21.1% use dedicated platform/CDN font hosts (69% good LCP), while the 49.9% loading from Google Fonts drop to 66% good LCP (2.1s median).
4.4% of WordPress sites use Adobe Fonts web font hosting source, and 69% of those sites have a good LCP, against 70% of all WordPress sites.
LCP pass rate
Sites with Adobe Fonts web font hosting source have a good LCP most often: 69%, against 70% of all WordPress sites. Sites with Google Fonts font source have it least often, at 66%.
Web font hosting source usage
Self-hosted fonts is the most used: 85.0% of WordPress sites. Adobe Fonts is 4.4% of WordPress 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): 1039 ms median for Adobe Fonts against 1172 ms for Google Fonts. Overall median field LCP is 2.0s for Adobe Fonts (TTFB 1039 ms, load delay 409 ms, load duration 186 ms, render delay 286 ms) versus 2.1s for Google Fonts.
Web font hosting source per framework
On jQuery, 86% of sites use self-hosted fonts web font hosting source, and 69% of jQuery sites have a good LCP, against 70% of all sites. On Vue, 94% of sites use self-hosted fonts, and 67% of Vue sites have a good LCP.
Alpine 364 sitesSelf-hosted (same origin) 69%Google Fonts (fonts.googleapis.com / gstatic) 40%Dedicated CDN / third-party font host 32%Adobe Fonts (use.typekit.net) 13%78%
jQuery 58,860 sitesSelf-hosted (same origin) 86%Google Fonts (fonts.googleapis.com / gstatic) 51%Dedicated CDN / third-party font host 21%69%
Vue 4,738 sitesSelf-hosted (same origin) 94%Dedicated CDN / third-party font host 22%Google Fonts (fonts.googleapis.com / gstatic) 18%67%
React 2,200 sitesSelf-hosted (same origin) 87%Google Fonts (fonts.googleapis.com / gstatic) 49%Dedicated CDN / third-party font host 29%63%Font hosting source or the framework
Does the framework explain the web font hosting source difference?
On jQuery, 69% of sites with Adobe Fonts web font hosting source have a good LCP, against 67% of jQuery sites with self-hosted fonts. Within jQuery, sites with Adobe Fonts and self-hosted fonts have a good LCP about equally often. On Vue, 56% of sites with Adobe Fonts web font hosting source have a good LCP, against 67% of Vue sites with self-hosted fonts. Within Vue, sites with Adobe Fonts have a good LCP less 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 30,689 sites (49.9%) loading Google Fonts, good LCP is 66% (2.1s median), and across 2,682 sites (4.4%) loading Adobe Fonts it is 69% (2.0s median). Self-hosted fonts (85.0%) reach 68% good LCP (2.0s median) and dedicated platform CDNs (21.1%) reach 69% (2.0s median).
Understanding web font hosting sources
Use the WordPress 6.5+ Font Library or local theme.json font declarations to download Google Fonts onto your own origin and eliminate external fonts.googleapis.com requests. On WordPress, 49.9% of sites still load Google Fonts externally (66% good LCP, 2.1s median) compared to 85.0% self-hosting fonts (68% good LCP).
By Arjen Karel · 63,295 crawled WordPress sites (36,524 with phone Chrome field data, 61,498 sites with web font hosting source, October 2026). How we measured.