Performance 6 min read

Web fonts without the slowdown: a practical guide

Beautiful type does not have to cost speed. How to load web fonts the fast way.

On this page 11 sections

Typography carries much of a brand’s personality, and custom fonts are one of the easiest ways to make a website feel distinctive. They are also a common reason pages feel slow: text that appears late, jumps when the font arrives, or doesn’t appear at all on a weak mobile connection.

You don’t have to choose between good type and a fast site. This guide explains how fonts affect loading and the handful of techniques that make them almost free.

The short answer

To keep web fonts fast:

  • Use fewer font files. Each weight and style is a separate download. Two or three files are enough for most sites.
  • Serve WOFF2. It is the most compressed format and supported by every current browser.
  • Self-host the files on your own domain rather than loading them from a third party.
  • Preload the one or two fonts used above the fold.
  • Set font-display so text is visible while the font loads.
  • Tune the fallback font so the swap doesn’t shift the layout.

How fonts slow a page down

A browser only discovers that it needs a font after it has downloaded the HTML and the CSS, and worked out which text uses that font. Only then does the font request start. On a slow connection, that chain can take a noticeable time, and during it the browser has to decide what to show.

Two problems follow:

Problem What the visitor sees Metric it affects
Invisible text while the font loads Blank spaces where headings should be Largest Contentful Paint (LCP)
Text that reflows when the font arrives Lines and buttons jumping position Cumulative Layout Shift (CLS)

Both are measured in Core Web Vitals, so font loading affects how Google assesses page experience as well as how the site feels.

Choose fewer, smarter font files

The cheapest font is the one you don’t download. Before any technical tuning, look at how many files your design uses.

  • Limit weights. Regular and bold, plus perhaps one display weight for headings, cover most designs. Light, medium, semibold and extra-bold all add files.
  • Consider variable fonts. A single variable font file can contain a range of weights. If your design uses three or more weights of one family, one variable file is often smaller than the separate files combined.
  • Skip italics you rarely use. If italics appear only in the odd quotation, the browser’s synthetic italic may be acceptable.
  • Question the second family. A separate heading font is a design choice with a speed cost. Sometimes a heavier weight of the body font does the same job.

Use WOFF2 and subset the characters

WOFF2 compresses font data better than older formats, and every current browser supports it, so you no longer need to ship TTF or WOFF fallbacks for modern visitors.

Subsetting removes characters you don’t need. A font with full support for many scripts can be several times larger than a version with only the characters your pages use. For a multilingual site, split the font into subsets per script and let the browser download only what each page needs, using unicode-range:

@font-face {
  font-family: 'Brand Sans';
  src: url('/fonts/brand-sans-latin.woff2') format('woff2');
  font-weight: 400 700;
  font-display: swap;
  unicode-range: U+0000-00FF, U+2000-206F;
}

A page in one language then downloads only that language’s subset.

Self-host instead of loading from a third party

Loading fonts from an external service means an extra connection to another domain before the font can download. Browsers also no longer share cached files between sites, so the old argument that visitors already have a popular font cached no longer applies.

Self-hosting puts the files on your own domain, alongside the rest of the site. It also avoids sending visitor data to a third party, which keeps your privacy policy simpler. Check the font’s licence first: most open-source fonts allow self-hosting, while commercial fonts set their own terms.

Preload the fonts that matter

Preloading tells the browser about a font as soon as it reads the HTML, instead of waiting for the CSS. Use it only for the fonts needed in the first screen, usually the body font and perhaps the main heading font:

<link rel="preload" href="/fonts/brand-sans-latin.woff2" as="font" type="font/woff2" crossorigin>

The crossorigin attribute is required even for fonts on your own domain. Preloading everything defeats the purpose, because it competes with other important files such as the main image.

Control what happens while fonts load

The font-display descriptor tells the browser what to do before the font arrives. MDN’s reference on font-display lists the options; the two most useful are:

  • swap shows text in a fallback font immediately, then swaps to the web font when it loads. Text is never invisible.
  • optional gives the font a very short window. If it doesn’t arrive in time, the page keeps the fallback for that visit. This avoids late swaps entirely on slow connections.

Most business sites use swap for body and heading text.

Match the fallback to avoid layout shift

With swap, the first text a visitor sees uses a system font. If that fallback is wider or taller than your web font, lines rewrap when the swap happens, and everything below moves.

You can reduce this by adjusting the fallback font so its size and spacing match the web font, using size-adjust and related descriptors:

@font-face {
  font-family: 'Brand Sans Fallback';
  src: local('Arial');
  size-adjust: 104%;
  ascent-override: 92%;
}

Then list it in your font stack straight after the web font. The exact values depend on the fonts; tools and frameworks can calculate them. web.dev’s guide to font best practices explains the approach in more detail.

How to check your fonts

  1. Run PageSpeed Insights on a key page. Look for font files in the network dependency chain and any layout shift caused by text. Our guide to reading PageSpeed Insights explains the report.
  2. Count the font files in your browser’s developer tools, Network tab, filtered by “Font”.
  3. Throttle the connection to a slow mobile speed and reload. Watch whether text appears immediately and whether it jumps.

Frequently asked questions

Are system fonts faster than web fonts?

Yes, because there is nothing to download. Some sites use a system font stack for body text and a web font only for headings. The trade-off is less control over how the text looks across devices.

Do web fonts affect SEO?

Not directly, but slow fonts can worsen LCP and CLS, which are part of how Google measures page experience. They also affect how quickly visitors can read your content, which matters more.

How many fonts should a website use?

One or two families, and as few weights as the design allows. Two to four font files in total keeps most sites fast.

What to do next

Open your homepage, filter the Network tab by fonts, and count the files. If there are more than four, start by removing weights you don’t need.

When we build a site through our website design and development service, fonts are self-hosted, subset and preloaded as part of the build, so the design looks right without slowing pages down. For more on overall speed, see our website speed optimisation guide.

Written by the PORVIX team

The people who design, build and maintain websites for growing businesses. We write about the questions that come up on real projects, in plain language, and update articles when the advice changes.

Published

How we work

Is your current site costing you enquiries?

A free, plain-language audit, by email within 2 business days.

Get a free audit
Get a free audit

Keep reading

More plain-language guides.

More on performance first, then other guides worth reading next.

All insights

Start here

Let’s build a website that brings in business.

Tell us about your project. You’ll hear back from a real person within one business day, with honest advice either way.

  • Free consultation
  • Fixed written quote
  • Your details stay private