Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

Website speed · 17 Nov 2026 · 7 min read

Web fonts: how to choose and load them without slowing your site

Fonts are files the browser must download. This guide shows how many to use, what font swapping does and when self-hosting makes sense.

The short answer

Web fonts are files that must download before text appears in its final typeface. Use as few families and weights as the design needs, load compressed WOFF2 files, set font-display to swap so text shows at once, preload only the key fonts and cache them well. Self-hosting gives control but needs licence checks.

Why fonts affect speed

Web fonts are files. Each font family, weight and style you use is another file the browser must download before it can show your text in the intended typeface. Until that file arrives, the browser has to decide what to show, and that decision shapes how fast the page feels.

The cost is not always obvious, because fonts look free. A design with a heading font, a body font, and three weights of each can easily ask for several files before a visitor reads a word. On a slow phone connection, that delay is felt. Font loading speed is a small part of the overall picture, but it is one of the few parts a designer chooses directly.

This guide explains how to pick fonts with speed in mind and how to load them without surprises. Your platform decides how much control you have over font loading, so it helps to know what a CMS is and how to choose one.

How many fonts should a site use?

As few as the design needs. For most business sites, one family for headings and one for body text is plenty, and a single family used well often looks more consistent. Each extra family multiplies the files.

The weights and styles matter as much as the number of families. Regular, bold and italic of one family are three files, unless you use a variable font, which packs a range of weights into one file. Ask the designer which weights are really used on the page. If a weight appears only once, replace it with one you already load.

  • List every font file the site requests. Your browser's developer tools show them under the network panel, filtered by fonts.
  • Remove families, weights or styles that do no visible work.
  • Load only the character sets your languages need. A site in English does not need the files for scripts it never displays.
  • Consider a system font for body text, which needs no download at all, and keep the custom font for headings or the logo.

A short brand font set is also easier to keep consistent. If you are choosing fonts for a brand, our guide to how to choose fonts for your brand covers the design side.

What is font swapping?

While a font file is downloading, the browser can behave in different ways. It can hide the text until the font arrives, which leaves a gap and is sometimes called the flash of invisible text. It can show the text in a fallback font and then swap in the real one when it loads, which is sometimes called the flash of unstyled text. Or it can wait a short time and then choose one of those.

The CSS setting that controls this is called font-display. Setting it to the value "swap" tells the browser to show text immediately in a fallback and swap when the web font is ready. Other values change how long the browser waits, or whether it swaps at all. The behaviour is documented by the browser vendors and by the web standards bodies, so check the current documentation for exact definitions.

For most content sites, showing readable text straight away matters more than a perfect typeface for the first moment. That favours swapping. The side effect is a visible jump when the fonts change, because two fonts rarely have the same letter widths. The jump can shift the layout, which counts against visual stability. You can reduce it by choosing a fallback font with similar proportions, and by adjusting the fallback's size so the two line up closely. Our guide to Core Web Vitals explains the layout shift measure and why it matters.

Do I need to self-host fonts?

You can load fonts from a third party font service or host the files yourself, on your own domain. Both work. The trade offs are these.

ApproachAdvantagesThings to check
Third party font serviceEasy to add, handles formats and subsets for youAn extra connection to another domain, a dependency on the provider, and privacy and consent questions because visitor requests go to the provider
Self-hosted filesSame domain as your site, full control over caching and which files load, no third party requestYou must prepare the files, check the font licence allows it and keep the files updated

Many sites choose self-hosting for control, and some choose a service for convenience. We do not recommend a particular service. Whichever route you take, read the font's licence and the provider's own documentation. Privacy rules on third party requests differ by country and change, so a lawyer should advise where it matters; our guide to what to back up on a website also reminds you to keep copies of font files and licences with your site files.

If you self-host, serve the font in a compressed web format such as WOFF2, which current browsers support, set long caching for the files and make sure the server sends them correctly.

Loading the fonts efficiently

A few practical steps cover most of the benefit.

  1. Use modern compressed font formats and subset the files to the characters you need.
  2. Preload the one or two fonts used above the fold, so the browser fetches them early. Preloading too many fonts competes with other important files, so be selective.
  3. Set a sensible font-display value and choose fallback fonts that resemble the final design.
  4. Cache the files for a long time and give them stable addresses, so returning visitors do not download them again.
  5. Avoid loading fonts that only a rarely seen page uses on every page.
  6. If you use a font for icons, check whether a small set of SVG icons would be lighter.

Then measure. Run your key pages through a speed test and compare before and after a change. Our guide to checking and improving website speed gives the method, and the fonts are rarely the only cause of a slow page. Large images and scripts usually weigh more.

Choosing fonts that read well

Speed is one test. Readability is the other, and it matters more for the people using the site. Pick faces with clear letter shapes at small sizes, enough contrast against the background and a comfortable weight for body text. Very thin or decorative faces belong in a logo or a large heading, not in a paragraph. Allow readers to enlarge text without the layout breaking, and do not put essential text inside images.

Think about the fallback when you design, not afterwards. If the font fails to load, the page must still be readable. Test with the font blocked, on a slow connection, and with the browser's text size increased.

Fonts should also match the brand rules you already have. If you use a custom typeface for a logo, check that the licence covers use on the web. Licences for print and web are often separate.

Fonts in a redesign or move

When a site is rebuilt, the font files are easy to lose or duplicate. Keep an inventory: families, weights, file formats, where the files live and under what licence. When you move to new hosting or a new address, make sure the font files are reachable at the new location and that old links do not break; the guide to redirect planning for a redesign or domain move explains how to keep the old addresses working.

Small touches such as the tab icon use the same brand assets. See our guide to favicons and browser tab icons to keep them in step. Types of hosting differ in how well they serve static files like fonts, so ask your host about caching and compression; the guide to web hosting types is a good place to start those questions.

For help planning type, speed and build together, our website development service page describes the service.

Related guides

Questions and answers

How many fonts should a website use?

Use as few as the design needs, often one family for headings and one for body text. Count weights and styles too, since each is usually a separate file unless you use a variable font. Remove any that do no visible work.

What is font swapping?

It is a setting called font-display. With swap, the browser shows text immediately in a fallback font and replaces it with the web font once it loads. It avoids invisible text but can cause a small visual jump, so pick a similar fallback.

Do I need to self-host fonts?

No, but it gives you more control over caching and avoids a third party request. A font service is easier to set up. Check the font licence and the provider's documentation, and ask a lawyer about privacy questions where they apply.

Do web fonts slow down a website?

They can, because each file must download before the final typeface shows. Fewer files, compressed formats, subsetting, preloading the important ones and good caching keep the cost small. Images and scripts usually weigh more than fonts.

What font format should I use?

WOFF2 is the usual choice for the web because it is compressed and current browsers support it. Check the current compatibility information, and see the font's licence for what formats you may serve.

Can I just use system fonts?

Yes. System fonts need no download, load immediately and can look clean. The trade off is less control, because the font differs by device. Many sites use system fonts for body text and a custom font for headings.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote