The State of Web Vitals

Web font hosting sources and the Core Web Vitals

70.6% of font-using sites (130,081) self-host fonts on their own origin (80% good LCP, 1.6s median) and 31.3% use dedicated platform/CDN font hosts (85% good LCP), while the 41.0% loading from Google Fonts drop to 79% good LCP (1.7s median).

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices field outcomes

31.3% of sites use CDN-hosted fonts web font hosting source, and 85% of those sites have a good LCP, against 82% of all sites.

The State of Web Vitals · October 2026 · 210,902 crawled sites · 196,263 with all devices field data · 184,141 sites with web font hosting sourceBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with CDN-hosted fonts web font hosting source have a good LCP most often: 85%, against 82% of all sites. Sites with Google Fonts font source have it least often, at 79%.

SitesGood, needs improvement, poor LCPMedian
All sites196,26382%1.5s
Dedicated CDN / third-party font host 31.3%55,45885%1.5s
Adobe Fonts (use.typekit.net) 4.5%8,01282%1.7s
Self-hosted (same origin) 70.6%125,73980%1.6s
Google Fonts (fonts.googleapis.com / gstatic) 41.0%72,45079%1.7s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · 210,902 crawled sites · 196,263 with all devices field data · 184,141 sites with web font hosting sourceBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Web font hosting source usage

Self-hosted fonts is the most used: 70.6% of sites. CDN-hosted fonts is 31.3% of sites.

Sites using each option (sites can use more than one) 184,141 sites
Self-hosted (same origin) 70.6% Google Fonts (fonts.googleapis.com / gstatic) 41.0% Dedicated CDN / third-party font host 31.3%
Self-hosted (same origin) 70.6% Google Fonts (fonts.googleapis.com / gstatic) 41.0% Dedicated CDN / third-party font host 31.3% Adobe Fonts (use.typekit.net) 4.5%
The State of Web Vitals · October 2026 · 210,902 crawled sites · 196,263 with all devices field data · 184,141 sites with web font hosting sourceBy Arjen Karel · corewebvitals.io/state-of-cwv
3

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 Google Fonts sits in time to first byte (TTFB): 551 ms median for CDN-hosted fonts against 737 ms for Google Fonts. Overall median field LCP is 1.5s for CDN-hosted fonts (TTFB 551 ms, load delay 374 ms, load duration 142 ms, render delay 229 ms) versus 1.7s for Google Fonts.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Sites with web font hosting source 130,002663 ms328 ms227 ms328 mslab 328 ms1.5s
Self-hosted (same origin) 93,716737 ms325 ms230 ms325 mslab 325 ms1.6s
Google Fonts (fonts.googleapis.com / gstatic) 52,654737 ms342 ms240 ms342 mslab 342 ms1.7s
Adobe Fonts (use.typekit.net) 5,896632 ms365 ms261 ms365 mslab 365 ms1.6s
Dedicated CDN / third-party font host 41,199551 ms374 ms229 ms374 mslab 374 ms1.5s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · 210,902 crawled sites · 196,263 with all devices field data · 184,141 sites with web font hosting sourceBy Arjen Karel · corewebvitals.io/state-of-cwv
4

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 79% (1.7s median), and across 8,267 sites (4.5%) loading Adobe Fonts it is 82% (1.7s median). Self-hosted fonts (70.6%) reach 80% good LCP (1.6s median) and dedicated platform CDNs (31.3%) reach 85% (1.5s 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 (80% good LCP) while 41.0% load Google Fonts (79% good LCP).

Go fix it Self-host Google Fonts → Responsive font loading strategy → Keep text visible during font load →
The State of Web Vitals · October 2026 · 210,902 crawled sites · 196,263 with all devices field data · 184,141 sites with web font hosting sourceBy Arjen Karel · corewebvitals.io/state-of-cwv
Platform & Framework Takeaways

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
96% vs 94% good LCP (Shopify self-hosted vs Google Fonts)

92.5% of Shopify stores serve fonts from their first-party domain (96% good LCP vs 94% 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 (96% good LCP, 1.3s median), 32.3% load Google Fonts (94% good LCP, 1.4s median), and 3.1% load Adobe Fonts (91%).

Read the Shopify font source breakdown →
React & Next.js 9,431 sites
90% vs 65% good LCP (CDN font host vs Google Fonts)

React & Next.js sites loading external Google Fonts (18.9%) pass LCP at 65% vs 90% on dedicated CDNs.

Across 9,431 font-using React sites, 77.1% serve fonts from external CDNs (90% good LCP, 1.3s median) and 18.9% load Google Fonts at runtime (65% good LCP, 2.0s median, 25 percentage points apart).

Related signals Script loading mix → DOM depth → Iframe loading → Scripts per page → By Arjen Karel · 210,902 crawled sites (196,263 with all devices Chrome field data, 184,141 sites with web font hosting source, October 2026) · How we measured