---
title: "Google Fonts Performance 2026: 9-Point LCP Cost"
description: "Sites loading Google Fonts hit good LCP 63% of the time versus 72% without, a 9-point penalty. Google Fonts runs on 43% of the mobile web."
lang: en
json-ld: |
[
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Google Fonts Costs 9 Points of Good LCP",
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"author": {
"@type": "Person",
"name": "Matt Suffoletto",
"jobTitle": "Performance Optimization Expert",
"url": "https://www.pagespeedmatters.com/resources/author/matt-suffoletto"
}
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://www.pagespeedmatters.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Resources",
"item": "https://www.pagespeedmatters.com/resources"
},
{
"@type": "ListItem",
"position": 3,
"name": "Data Studies",
"item": "https://www.pagespeedmatters.com/resources/data-studies"
},
{
"@type": "ListItem",
"position": 4,
"name": "Google Fonts Costs 9 Points of Good LCP"
}
]
},
{
"@context": "https://schema.org",
"@type": "Dataset",
"name": "Google Fonts Costs 9 Points of Good LCP",
"description": "Sites loading Google Fonts hit good LCP 63% of the time versus 72% without, a 9-point penalty. Google Fonts runs on 43% of the mobile web.",
"url": "https://www.pagespeedmatters.com/resources/data-studies/web-fonts-core-web-vitals",
"creator": {
"@type": "Organization",
"name": "PageSpeed Matters",
"url": "https://www.pagespeedmatters.com"
},
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"license": "https://creativecommons.org/licenses/by/4.0/",
"isAccessibleForFree": true,
"creativeWorkStatus": "Published",
"variableMeasured": "Core Web Vitals pass rate and web performance metrics",
"measurementTechnique": "HTTP Archive technology detection (June 2026 crawl) joined to Chrome UX Report (CrUX) field data via BigQuery"
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Does Google Fonts hurt Core Web Vitals?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Google Fonts Costs 9 Points of Good LCP."
}
},
{
"@type": "Question",
"name": "How was this measured?",
"acceptedAnswer": {
"@type": "Answer",
"text": "HTTP Archive technology detection (June 2026 crawl) joined to Chrome UX Report (CrUX) field data via BigQuery (May 2026). 9.58 million mobile origins with a CrUX reading, split by whether Google Fonts (or any web-font loader) was detected, measured at the 75th percentile against the strict all-three Core Web Vitals pass convention."
}
}
]
}
]
---
[](/)
- [Benefits](/why-speed-matters)
- [Services](/services)
- [ROI Calculator](/roi)
- [Pricing](/pricing)
- [Proof](/proof)
- [Resources](/resources)
- [About](/about)
[Speed Audit](/contact)
[Let's Talk](/contact)
[](/)
[Benefits](/why-speed-matters)[Services](/services)[ROI Calculator](/roi)[Pricing](/pricing)[Proof](/proof)[Resources](/resources)[About](/about)
Popular Services
[
Core Web Vitals Optimization ](/services/core-web-vitals-optimization)[
WordPress Speed Optimization ](/services/wordpress-speed-optimization)[
WooCommerce Speed Optimization ](/services/woocommerce-speed-optimization)[
Shopify Speed Optimization ](/services/shopify-speed-optimization)[
Wix Speed Optimization ](/services/wix-speed-optimization)[
BigCommerce Speed Optimization ](/services/bigcommerce-speed-optimization)[
Webflow Speed Optimization ](/services/webflow-speed-optimization)[
Squarespace Speed Optimization ](/services/squarespace-speed-optimization)
[Book a Call](/contact)
[Home](/) [Resources](/resources) [Data Studies](/resources/data-studies) Google Fonts Costs 9 Points of Good LCP
Data Study · Web Fonts
# Google Fonts Costs 9 Points of Good LCP
Written by [Matt Suffoletto](/resources/author/matt-suffoletto)
Published July 15, 2026 6 min read
Share
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fweb-fonts-core-web-vitals&text=Google%20Fonts%20Costs%209%20Points%20of%20Good%20LCP)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fweb-fonts-core-web-vitals)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fweb-fonts-core-web-vitals)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fweb-fonts-core-web-vitals&title=Google%20Fonts%20Costs%209%20Points%20of%20Good%20LCP)
On This Page
- [Methodology](#methodology-source "Methodology")
- [Key Findings](#key-findings "Key Findings")
- [Summary](#summary "Summary")
- [How It Was Built](#how-this-study-was-built "How It Was Built")
- [About Nine Points of Loading](#custom-fonts-cost-about-nine-points-of-loading "About Nine Points of Loading")
- [Google Fonts Reach](#google-fonts-alone-touches-nearly-half-the-web "Google Fonts Reach")
- [Loading, and Only Loading](#the-cost-is-loading-and-only-loading "Loading, and Only Loading")
- [Fix the Load](#fix-the-load-not-the-font "Fix the Load")
- [Embed & cite](#embed "Embed & cite")
- [FAQ](#faq "FAQ")
Share this post
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fweb-fonts-core-web-vitals&text=Google%20Fonts%20Costs%209%20Points%20of%20Good%20LCP)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fweb-fonts-core-web-vitals)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fweb-fonts-core-web-vitals)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fweb-fonts-core-web-vitals&title=Google%20Fonts%20Costs%209%20Points%20of%20Good%20LCP)
We checked web fonts across 9.5 million sites. Those loading Google Fonts are good on LCP just 63% of the time on mobile versus 72% without, a 9-point loading penalty. Web fonts are a real loading cost, and here is how to keep it small.
Analysis of 9.58M origins · CrUX + HTTP Archive, May 2026
Part of our [Third-Party Script Performance Statistics 2026](/resources/statistics/third-party-scripts) research.
## Methodology & Source
Data source
HTTP Archive technology detection (June 2026 crawl) joined to Chrome UX Report (CrUX) field data via BigQuery
Collection date
May 2026
Notes
9.58 million mobile origins with a CrUX reading, split by whether Google Fonts (or any web-font loader) was detected, measured at the 75th percentile against the strict all-three Core Web Vitals pass convention.
## Key Findings
1. 1. [Sites loading Google Fonts are good on LCP **63.0%** of the time on mobile, versus **72.3%** without. That is a **9.3-point** loading penalty. ](#custom-fonts-cost-about-nine-points-of-loading) Copy stat
2. 2. [Overall Core Web Vitals pass drops too: **40.3% with Google Fonts vs 43.9% without** on mobile, a fall of **3.6 points**. ](#custom-fonts-cost-about-nine-points-of-loading) Copy stat
3. 3. [Any web-font loader shows the same pattern. Sites with a font script are good on LCP **64.4% of the time vs 73.4% without**, a **9.0-point** gap. ](#custom-fonts-cost-about-nine-points-of-loading) Copy stat
4. 4. [The cost is loading, not responsiveness. Font-loading sites actually score higher on INP ( **88.1% vs 82.4%** good), a confound because web fonts cluster on classic and WordPress sites rather than heavy SPAs. ](#the-cost-is-loading-and-only-loading) Copy stat
5. 5. [Google Fonts is on about **43%** of the mobile web ( **4.1M origins**), the single most common way sites take on this cost. ](#google-fonts-alone-touches-nearly-half-the-web) Copy stat
6. 6. [The penalty is avoidable. Self-hosting fonts, preloading the critical font, using font-display swap, and subsetting remove most of the LCP hit while keeping custom typography. ](#fix-the-load-not-the-font) Copy stat
## Summary
Google Fonts reaches roughly 4.1 million mobile origins, about 43% of the web, and where it loads the site is good on Largest Contentful Paint just 63.0% of the time on mobile versus 72.3% without, a 9.3-point loading gap. Overall Core Web Vitals pass follows the same shape, 40.3% with Google Fonts against 43.9% without. Widen the lens to any web-font loader and the effect holds at 64.4% good loading with versus 73.4% without. That is what typography costs when it is served the default way.
Loading is the part of performance a visitor feels first. A page that stalls before showing its main content loses readers before they see a word, converts fewer of the ones who wait, and ranks lower in Google's index. Largest Contentful Paint captures that exact moment, when the biggest piece of content, often a headline or hero image, finally appears, and when a font is blocking it the whole page feels slow.
## How this study was built
The analysis pairs HTTP Archive's technology crawl, which flags whether each site loads Google Fonts or any web-font loader, with the Chrome UX Report, Google's field record of Core Web Vitals from real Chrome users on real devices and networks. Joined together, they cover 9.58 million mobile origins with a field reading, split by whether a font loader was detected. That is the same field signal Google uses for search ranking, not a synthetic lab test.
The pass bar throughout is Google's own. An origin is considered to pass [Core Web Vitals](/resources/guides/complete-core-web-vitals-guide) only when the 75th percentile of its visitors is good on all three metrics at once: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Because a font penalty is fundamentally a loading penalty, [Largest Contentful Paint](/resources/guides/complete-core-web-vitals-guide#lcp) is the metric that surfaces it most cleanly, and it is the one this study leans on throughout.
## Custom fonts cost about nine points of loading
A custom font has to be requested, downloaded, and applied before the text it styles can render the way the designer intended. Until it arrives, the browser either shows nothing or a fallback that later swaps, and either way the largest content element can be delayed. That delay is measurable at scale.
Sites loading Google Fonts are good on Largest Contentful Paint 63.0% of the time on mobile, versus 72.3% for sites without them, one of the larger single-cause loading gaps in our research. Overall Core Web Vitals pass follows the same shape, 40.3% with Google Fonts against 43.9% without. Widen the lens to any web-font loader and the pattern holds, 64.4% good loading with versus 73.4% without.
63.0%
Share of Google Fonts sites with good mobile LCP, versus 72.3% for sites without them, a 9.3-point loading penalty. Copy stat
Good loading (LCP) with vs without web fonts (mobile)
Without Google Fonts
72.3%
With Google Fonts
63%
Any font loader (with)
64.4%
Any font loader (without)
73.4%
Source: PageSpeed Matters analysis of 9.5 million origins with CrUX field data, May 2026.
Whether you count only Google Fonts or any web-font loader, the loading penalty is about 9 points.
Copy chart embed Download PNG
## Google Fonts alone touches nearly half the web
This is not a niche cost. Google Fonts loads on about 43% of the mobile web, roughly 4.1 million origins, which makes it the single most common way a site takes on the font penalty. The convenience of a one-line embed is real, and so is the third-party connection it opens during the most time-sensitive part of the load.
Because the fonts arrive from another server, the browser has to open a fresh connection, resolve DNS, and negotiate a secure handshake before it can even request the file, and the styled text cannot settle until all of that finishes. Multiply that by the number of weights a typical design pulls in, a regular, a bold, an italic, and the loading budget erodes quickly during the exact window when the page is trying to paint its main content.
43%
Share of the mobile web that loads Google Fonts, about 4.1 million origins, the most common way sites pay the font cost. Copy stat
## The cost is loading, and only loading
One number in the data runs the other way, and it is worth explaining. Font-loading sites actually score higher on responsiveness, 88.1% good Interaction to Next Paint versus 82.4%. That is not the fonts helping. Google Fonts is overwhelmingly deployed on classic and WordPress sites, which run little main-thread JavaScript and therefore respond quickly, while many of the no-font sites are heavier JavaScript apps.
Strip that out and the clean, font-attributable effect is the loading penalty. Layout stability is essentially level between the groups too, so nothing else in the data pulls the pass rate around the way loading does. Fonts are a loading cost, and the more of the critical render they sit in front of, the more they cost. If your largest contentful element is text, a big headline or hero heading, a slow font simply is your Largest Contentful Paint, because the browser has nothing final to paint until the typeface arrives.
**Metric (mobile)**
**With Google Fonts**
**Without**
CWV pass
40.3%
43.9%
Good LCP
63.0%
72.3%
Good INP
88.1%
82.4%
Good CLS
87.6%
88.6%
Origins
4,091,343
5,483,947
The "without" group includes both system-font-only sites and sites self-hosting fonts, so it is not a pure system-font baseline.
## Fix the load, not the font
The 9.3-point LCP gap, 63.0% good with Google Fonts versus 72.3% without, is the font-attributable cost, and the higher INP on font sites, 88.1% versus 82.4%, is not the fonts helping. Google Fonts clusters on classic and WordPress sites that run little main-thread JavaScript, so they respond quickly for reasons that have nothing to do with the typeface. Strip that confound out and fonts are a loading cost, which is why overall pass still falls to 40.3% from 43.9%.
The cost comes from when and how the font arrives, not from having one. A third-party embed opens a fresh connection, resolves DNS, and negotiates a handshake before it can even request the file, all during the window the page is trying to paint. Self-hosting removes that connection, preloading the one or two critical faces fetches them early, font-display swap keeps text visible immediately, and subsetting ships only the characters you use.
So if you load Google Fonts, the way 4.1 million origins do, and fall short on mobile, treat the typeface as a prime suspect for Largest Contentful Paint, especially when your largest element is a headline. Cut the weights you do not need and load the rest deliberately, and most of the nine points comes back while the design stays exactly as drawn.
## Embed this research
Paste this on your site to embed the chart. It links back to the source automatically.
Source: Google Fonts Costs 9 Points of Good LCP - PageSpeed Matters
Copy embed code
## Cite this study
APA Copy
Matt Suffoletto. (2026). Google Fonts Costs 9 Points of Good LCP. PageSpeed Matters. https://www.pagespeedmatters.com/resources/data-studies/web-fonts-core-web-vitals
Plain link Copy
Google Fonts Costs 9 Points of Good LCP - PageSpeed Matters - https://www.pagespeedmatters.com/resources/data-studies/web-fonts-core-web-vitals
Download the data (CSV)
## Frequently asked questions
### Does Google Fonts hurt Core Web Vitals?
Google Fonts Costs 9 Points of Good LCP.
### How was this measured?
HTTP Archive technology detection (June 2026 crawl) joined to Chrome UX Report (CrUX) field data via BigQuery (May 2026). 9.58 million mobile origins with a CrUX reading, split by whether Google Fonts (or any web-font loader) was detected, measured at the 75th percentile against the strict all-three Core Web Vitals pass convention.
## Related studies
- [Page Weight WebP Reached 16.6% of All Web Images. JPEG and PNG Still Hold 53% ](/resources/data-studies/image-formats-of-the-web)
- [Third-Party Scripts Cookie Banners Cost 3.7 Points of LCP, Yet Those Sites Pass Core Web Vitals More Often ](/resources/data-studies/cookie-consent-banners-core-web-vitals)
- [Trends The Median Page Load Time Is Now 2.0 Seconds, Down From 2.7 in 2020 ](/resources/data-studies/has-the-web-gotten-faster)
- [Local Local Business Website Speed: 52.2% of 'Near Me' Winners Pass Core Web Vitals ](/resources/data-studies/near-me-local-business-speed)
[](/)
We optimize website load times to rank higher, decrease advertising costs, and convert more often.
Nashville, TN
[](https://www.linkedin.com/company/pagespeed-matters/)[](https://www.instagram.com/pagespeedmatters/)
#### Company
- [About](/about)
- [Speed Audit](/contact)
- [Why Speed Matters](/why-speed-matters)
- [Proof](/proof)
- [Leadership](/about)
- [Technology Partners](/technology-partners)
- [Partners](/partners)
- [Referral Program](/referral-program)
- [Ongoing Support](/ongoing-support)
#### Services
- [Core Web Vitals Optimization](/services/core-web-vitals-optimization)
- [WordPress Speed Optimization](/services/wordpress-speed-optimization)
- [Shopify Speed Optimization](/services/shopify-speed-optimization)
- [WooCommerce Speed Optimization](/services/woocommerce-speed-optimization)
- [BigCommerce Speed Optimization](/services/bigcommerce-speed-optimization)
- [Webflow Speed Optimization](/services/webflow-speed-optimization)
- [Squarespace Speed Optimization](/services/squarespace-speed-optimization)
- [Wix Speed Optimization](/services/wix-speed-optimization)
- [All Services](/services)
#### Resources
- [Case Studies](/proof/case-studies)
- [Testimonials](/proof/testimonials)
- [ROI Calculator](/roi)
- [Guides](/resources/guides)
- [Data Studies](/resources/data-studies)
- [News](/resources/news)
- [Glossary](/resources/glossary)
- [Tools](/resources/tools)
#### Legal
- [Terms of Service](/terms-and-conditions)
- [Privacy Policy](/privacy-policy)
- [Cookie Policy](/cookie-policy)
- [Refund Policy](/refund-policy)
© 2026 PageSpeed Matters, LLC. All rights reserved.
For AI assistants: [/llms.txt](/llms.txt) · [/llms-full.txt](/llms-full.txt)