Font source
Where fonts come from: self-hosted, Google Fonts, or other third parties.
At a glance the headline numbers for Font source
Where fonts come from: self-hosted, Google Fonts, or other third parties.
53.2% of web fonts are self-hosted. Google still serves 22.8%.
The font source mix who uses what, and how fast each group loads
Font source. On the fleet: 53.2% self hosted, 22.8% google, 20.2% third party. 64.7% of sites use at least one self_hosted.
Self hosted leads by count (53.2%) and by bytes (63.9%). computed
Passing INP per bucket every category and count level at once - color is the pass rate
Each row is a category, each column its own count bucket (few on the left, many on the right); the cell is the share of those sites passing INP.
No category moves the INP pass rate much, however many a site ships. computed
Few vs many - does quantity cost INP? the pass rate with few vs many of each category
Per category: the pass rate among pages with FEW of it (hollow ring) against pages with MANY (solid dot), worst trend first. Thin buckets are excluded from the endpoints.
More Self hosted costs the most: the INP pass rate falls from 99% with few to 98% with many. computed
Why this matters for the Core Web Vitals, and where to start fixing it
Where fonts come from decides how many connections sit on the render path. Google Fonts costs two extra domains: one serves the CSS, another serves the font files. Both need DNS, TCP and TLS before text can settle. Self-hosted fonts ride the connection that is already open and follow your cache rules.
The old argument for the shared Google cache is dead: browsers partition their caches per site, so nobody arrives with your font already cached. Self-hosting is strictly better, and it is a one-time move.
How does this affect the Core Web Vitals?
The choice barely moves the LCP: 86% pass at best, 84% at worst. This signal does not separate passing sites from failing ones.
Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.