How Fonts Slow Down Your Site and What to Do About It
On a high-traffic project, we noticed LCP increased by 1.2 seconds due to loading a custom font. The browser waited for Google Fonts five times (different weights), and users saw a blank screen for two whole seconds. After properly configuring font-display, preload, and subset, we reduced the time to 0.4 seconds—and CLS dropped from 0.25 to 0.01. The fix took 6 hours but paid off with a 40% improvement in Core Web Vitals.
In this article, we’ll show you how to configure fonts without losing performance. You’ll learn which font-display values to choose, how to preload critical fonts, why subsetting matters, and why self-hosting beats Google Fonts. We’ll also share real cases from our practice—over 50 projects with font optimization.
Why font-display: swap Doesn’t Solve CLS
font-display: swap shows a system font immediately, then swaps to the custom font. However, if the font hasn’t loaded within 100 ms, a re-layout occurs—CLS increases. To avoid this, you need to compensate for the metric differences between the custom and fallback fonts. Use the properties ascent-override, descent-override, line-gap-override, and size-adjust:
@font-face {
font-family: 'InterFallback';
src: local('Arial');
ascent-override: 90%;
descent-override: 22%;
line-gap-override: 0%;
size-adjust: 107%;
}
body {
font-family: 'Inter', 'InterFallback', sans-serif;
}
To find precise values, use the fontaine package or the built-in Next.js next/font function—it automatically generates a fallback with correct metrics. As stated in the MDN documentation, using size-adjust achieves minimal CLS. According to Web Almanac, improper font loading increases CLS by an average of 0.15.
| Value |
Behavior |
When to Use |
| auto |
Depends on browser |
Not recommended |
| block |
Hide text until loaded (FOIT) |
Icon fonts |
| swap |
Fallback → custom when loaded |
Body text |
| fallback |
100 ms hidden, then swap |
Balance FCP/CLS |
| optional |
Only if already cached |
Non-critical fonts |
Preload: Only Critical Files
Preloading all fonts on the page is a common mistake. The browser is forced to load 5–6 files in a competitive queue, slowing down other resources. Preload only above-the-fold fonts—for example, the regular and bold weights for headings:
<link rel="preload" href="/fonts/inter-regular.woff2" as="font" type="font/woff2" crossorigin>
<link rel="preload" href="/fonts/inter-700.woff2" as="font" type="font/woff2" crossorigin>
How Subsetting Reduces Font Size by 5–10×
The full Inter font includes Latin, Cyrillic, Greek, Hebrew, and weighs ~500 KB. After subsetting to only needed characters (Cyrillic + basic Latin), the size drops to 30–80 KB—savings of 5–10×. Use pyftsubset from the fonttools library:
pip install fonttools brotli
pyftsubset inter-regular.ttf \
--unicodes="U+0020-007E,U+00A0-00FF,U+0400-045F,U+0490-0491" \
--layout-features="kern,liga,calt" \
--flavor=woff2 \
--output-file=inter-regular-subset.woff2
Additional: Automating Subsetting
For CI/CD, you can use the npm package `fontkit` or the built-in capabilities of Webpack/Next.js. This allows generating subsets at build time.
Self-Hosted Fonts Are 200+ ms Faster Than Google Fonts
Google Fonts adds DNS lookup, TLS handshake, and cross-origin latency. Self-hosted fonts:
- Eliminate an extra request to a third-party domain
- Allow HTTP/2 push (though preload is better)
- Work even when Google is blocked (e.g., in China)
Measurements show that self-hosting on the same CDN speeds up LCP by 200–300 ms compared to Google Fonts. We recommend downloading fonts via google-webfonts-helper or installing the npm package @fontsource-variable/inter.
| Comparison |
Google Fonts |
Self-hosted |
| Extra DNS lookup |
Yes |
No |
| Cache control |
Limited |
Full |
| Subset capability |
Via URL |
Custom |
| Works when blocked |
No |
Yes |
What’s Included in Font Optimization Work
If you order this service from us, the result includes:
-
Audit of current fonts—analysis of weight, number of styles, source (Google Fonts/self-hosted)
-
Subsetting—generating subsets for Cyrillic and Latin
-
Self-hosting—moving fonts to your server or CDN
-
Configuring font-display—correct values for critical and non-critical fonts
-
Preloading critical files—only for above-the-fold
-
CLS compensation—fallback with correct metrics
-
Documentation—description of all changes and maintenance recommendations
Timeline: 4 to 8 hours depending on the number of fonts and weights. The cost is calculated individually—contact us for an estimate for your project.
Our team has 10+ years of experience in web performance and certification in Google Core Web Vitals. We guarantee metric improvements: LCP will drop by at least 30%, and CLS will be below 0.1. Order font optimization with a guaranteed metric improvement. Contact us for a comprehensive site audit.
Why are Core Web Vitals critical for technical SEO?
PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.
Core Web Vitals: what really affects rankings
Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.
LCP: why 8 seconds is not an image problem
LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.
Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.
Solution:
- Move to
<img> with fetchpriority="high" and loading="eager"
- Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
-
<link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
- Remove render-blocking scripts above hero with
defer
Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.
If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.
CLS: what causes layout shifts and how to stop them
CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.
Sources:
- Images without dimensions.
<img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
- Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via
min-height or load before main content.
- Web fonts.
font-display: swap with size-adjust minimizes CLS.
- Dynamic content — add skeleton placeholder with dimensions.
| Typical scenario |
CLS before |
CLS after |
Main fix |
| Discount banner without min-height |
0.42 |
0.02 |
min-height: 300px |
| Article images without attributes |
0.18 |
0.01 |
width/height + aspect-ratio |
| Chat widget loaded after 3s |
0.35 |
0.05 |
position: fixed with reserved margin |
INP: why interface freezes for 500ms
INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.
Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.
Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:
- Processing large list without requestIdleCallback or requestAnimationFrame
- Heavy event listeners without debounce/throttle
- Synchronous setState in React triggering full re-render
- Third-party scripts on main thread
Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.
How do structured data and Schema.org improve search visibility?
Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.
Markup types by scenario:
- E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
- Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
- Local business: LocalBusiness with address, telephone, openingHours, geo.
- FAQ: FAQPage with mainEntity — questions appear as expandable block.
Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.
How to conduct a technical SEO audit
Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.
Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.
JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.
Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.
Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.
What does the optimization process look like?
| Stage |
What's included |
Duration |
| Audit |
Scanning, Core Web Vitals analysis, Schema audit, priority report |
1–2 weeks |
| Single template optimization |
LCP, CLS, INP, SSR/SSG implementation, preload setup |
2–4 weeks |
| Full technical optimization |
All templates, code splitting, Web Workers, CI monitoring |
4–10 weeks |
| Schema.org implementation |
JSON-LD generation, validation, rich snippet testing |
1–3 weeks |
What deliverables do you receive?
- Documentation: report of found issues, priority roadmap, timelines for each stage.
- Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
- Training: one or two calls reviewing typical mistakes for your team.
- Support: one month accompaniment after deployment — metric checks, regression fixes.
How many positions can you regain through technical SEO?
We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.
Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.
