FREEFirst project with us? Your landing page design is on the house.See the offer

SEO and AEO

Web fonts and site speed: fewer files, faster text

How web fonts slow a page and how to fix it: WOFF2, fewer weights, variable fonts, font-display swap, preload, self-hosting and matched fallback fonts.

By Abdul QuadirUpdated 2026-11-107 min read
TL;DR
  • Fonts slow a page in two ways: text waits for the file, and the page shifts when the font replaces the fallback.
  • Ship WOFF2 only, and load fewer families and weights. One variable font can replace several weight files.
  • Set font-display to swap so text shows at once, and preload only the one or two fonts used at the top of the page.
  • Self-hosting gives you control and keeps visitor data on your side, but it is only faster on a fast host with long cache times.
  • Match the fallback font with size-adjust so the swap barely moves the page, and read the font's licence before you convert or self-host it.

The short answer

Web fonts slow a page in two ways. Text can stay hidden while the font file downloads, and the page can jump when the font arrives and replaces the fallback. Fix both with a short list: use WOFF2 files, load fewer families and weights, set font-display: swap, preload the one or two fonts used at the top of the page, and pick a fallback font that takes up nearly the same space.

Everything below comes from Google's web.dev guide to font best practices, MDN, and the Webflow and Astro docs. No tricks, only fewer and smaller files that arrive sooner.

How a font slows a page down

A font is a file. Until it arrives, the browser has to decide what to do with the text that needs it. The web.dev guide names two costs:

  • Delayed text. If a web font has not loaded, browsers usually hold back the text that uses it. That often delays First Contentful Paint, and sometimes LCP too, when the largest thing on screen is a heading or a paragraph.
  • Layout shift. The fallback font and the web font rarely take up the same space. When one replaces the other, lines rewrap and everything below moves. That counts towards CLS.

There is a third, quieter cost: a font is only requested once the browser has read the CSS that uses it. A @font-face rule on its own does not start a download. So a font named in a stylesheet that loads late is found late.

How much does this matter next to images and scripts? Usually less. In our site speed study (Forbes Cloud 100, checked 10 November 2026), the median Lighthouse mobile performance score is 48 out of 100, yet 90% keep layout shift at 0.1 or less. The study did not look at fonts on their own. Still, fonts are one of the cheapest things to get right, and they decide how soon people can read.

Use WOFF2, and load fewer files

WOFF2 is the format to ship. The web.dev guide says it has the widest browser support and the best compression of the modern formats, and that it compresses about 30% better than WOFF because it uses Brotli. Its advice is to use WOFF2 alone and skip the older formats.

Check what your site sends today. Open the Network tab in your browser's developer tools, filter by Font and reload. If you see .ttf, .otf or .woff files, convert them. Webflow's help page on custom fonts also recommends WOFF2 and says it can be up to 50% smaller than TTF or OTF.

One level further is subsetting: removing the characters you never use. A site in English does not need Cyrillic or Greek glyphs in the same file. The unicode-range descriptor lets you split a font by script, and the browser only downloads a file when the page has a character in its range. Check the licence before you subset a font. More on that below.

Then load fewer of them. Each family, weight and style is its own file. A design with two families, four weights each and italics can ask for a dozen files before anyone reads a word.

  • Count what the design really uses. Regular and bold cover most pages.
  • Drop italics you never set. The browser can fake a slant for the odd word, though a true italic looks better in long text.
  • Think about system fonts for body text. They are already on the device, so there is nothing to download. In CSS that is font-family: system-ui.
  • Replace icon fonts with SVG icons. The web.dev guide notes icon fonts are more likely to cause layout shifts.

Variable fonts put every weight of a family in one file. If your design uses several weights of the same family, one variable file can replace them all. It is not a free win: web.dev points out that a variable font is usually larger than a single static file. One weight only? A static file is smaller. Three or more? The variable file usually pays off.

Set font-display so text shows at once

The font-display descriptor tells the browser what to do while a font loads. MDN describes it as a timeline with a block period, when text is invisible, and a swap period, when fallback text shows and can still be replaced. The web.dev guide gives the usual timings:

ValueText hidden forCan still swap forGood for
block2 to 3 secondsNo limitRare cases where fallback text must never show
swap0 msNo limitBrand fonts that must always appear
fallback100 ms3 secondsA middle ground
optional100 msNonePages where no shift matters more than the font

Without the descriptor, the browser decides. The guide says Chromium and Firefox hide text for up to 3 seconds, and Safari hides it until the font arrives.

swap delays text the least, which is why most sites use it. The trade is a visible change when the font lands. optional removes that change, but on a slow connection the visitor may see the fallback font for the whole visit. Pick swap, then make the change small with the two steps below.

Preload the one font that matters

A preload tells the browser to fetch a file before it has found it in the CSS. For the font used in your heading or first paragraph, that can remove the wait.

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

Three rules:

  • Keep crossorigin, even for fonts on your own domain. MDN explains that fonts are always fetched in CORS mode, so the preload has to be set up the same way to be used.
  • Preload one or two files, not all of them. The web.dev guide warns that a preload takes browser resources away from other files. Preload the fonts visible at the top of the page and let the rest load normally.
  • A preload ignores unicode-range. If you split a font by script, preload the file your main language needs, not every part.

If the fonts live on another server, a preconnect to that server helps too. Font files need their own preconnect with crossorigin. And put the @font-face rules in the page head instead of a late stylesheet, so the browser finds them sooner. Do not inline the font files themselves; that makes the HTML heavy and slows everything else.

Self-hosting vs a font CDN, and the licence

You can serve font files from your own site or load them from a service such as Google Fonts or Adobe Fonts.

On paper, self-hosting should be faster, because the browser skips setting up a connection to a second server. The web.dev guide is careful here: in practice the difference is less clear cut, and self-hosting is less likely to win if your own host has no CDN or HTTP/2. So self-hosting is not a speed fix by default. It works when the files are WOFF2, served from a fast host with long cache times, and the key one is preloaded.

Self-hosting has two more points in its favour:

  • Control. You choose the format, the subset, the font-display value and what gets preloaded.
  • Privacy. Nothing about your visitors goes to a font service. Webflow's help page on adding Google Fonts notes that its Google Fonts integration sends visitor IP addresses to Google's servers and may not be GDPR compliant, and suggests uploading the files as custom fonts instead.

Check the licence first. A font is licensed software. Before you upload, convert, subset or self-host one, read its licence. Some licences cover desktop use only, some limit web use by page views or domains, and some do not allow changing the file, which includes subsetting. The web.dev guide says the same: check that the licence allows subsetting and self-hosting. Webflow's help page asks you to confirm you have permission before uploading a font.

Open source fonts under the SIL Open Font License are the simple case, and the ones on our site are under it. This is a reminder, not legal advice. If a licence is unclear, ask the foundry.

Match the fallback font to stop the jump

With swap, visitors see the fallback font first. If the fallback is wider or taller than the brand font, lines rewrap when the real font lands and the page jumps. The fix is to make the fallback take up the same space.

Start with the basics. Always end your font stack with a generic family such as sans-serif or serif. Google's guide to fixing CLS notes that without one, the browser uses its default font, which is Times on Chrome, a poor match for most brand fonts.

Then tune it. size-adjust is a @font-face descriptor that scales a font's glyphs and metrics by a percentage. You declare a local font as a named fallback and scale it to match:

@font-face {
  font-family: "Brand fallback";
  src: local("Arial");
  size-adjust: 104%;
}
h1 { font-family: "Brand", "Brand fallback", sans-serif; }

The 104% is only an example. The right number depends on your font, so try values in the browser until the fallback lines break in the same places. Three more descriptors, ascent-override, descent-override and line-gap-override, adjust the height above and below the text. MDN lists size-adjust as widely available in browsers since September 2023.

Fonts in Webflow

Webflow handles the files for you, so the work is in the settings. All of it is under Site settings, Fonts tab, per Webflow's help pages:

  • Upload WOFF2. Webflow accepts several formats but recommends WOFF2. The limit is 4 MB per font file.
  • Use a variable font if the design needs several weights. Webflow supports variable fonts in TTF, OTF, WOFF and WOFF2.
  • Set font display. Each uploaded font has a font display setting. Webflow's tip is that swap can prevent a flash of invisible text.
  • Edit the fallback. Webflow creates a fallback for each family you upload, and you can choose which font it falls back to.
  • Rename fonts that share a name with a Google font. If you upload Montserrat or Roboto under the same name, Webflow may keep loading it from Google's servers.
  • Remove what you do not use. Deleting a font in settings is not enough. It stays in the published CSS until no class or tag uses it.

Webflow's font optimisation page adds that its health scan flags sites with more than ten web fonts. For the rest of a Webflow speed pass, see how we get 90+ on mobile and our guide to Core Web Vitals on Webflow.

Fonts in Astro, and what our own site does

In Astro you have full control, so you make every choice above yourself. Astro's docs list fonts among the files that suit the public/ folder, which is copied to the build untouched. Astro also has a Fonts API that downloads fonts and serves them from your own site, can add preload links and tries to generate matched fallbacks.

This site is built in Astro and takes the simple route:

  • Three families, Bricolage Grotesque, Geist and Geist Mono, each as one variable WOFF2 file per script, so there is no separate file per weight.
  • The files sit in public/fonts and are served from our own domain. No font CDN.
  • Each file is split into Latin and Latin Extended with unicode-range, so a page only downloads the extended file when it has a character from it.
  • The @font-face rules are in the page head with font-display: swap.
  • Only two files are preloaded: the heading font and the body font. The mono font loads when a page uses it.

It is the same list as this post, applied once in the layout so every page gets it.

What to do next

  1. Open the Network tab, filter by Font and count the files and their sizes.
  2. Convert anything that is not WOFF2.
  3. Cut families, weights and styles the design does not use.
  4. Set font-display: swap.
  5. Preload the heading font, with crossorigin.
  6. Match the fallback font, then check the layout shift number again.
  7. Test on the mobile setting before and after.

Want it done for you? Font work is part of every build we do in Webflow and Astro. Send us your site and we will tell you what its fonts cost.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Webflow, font-display

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

They can. A browser may hold back text until the font file arrives, and the swap from the fallback font can shift the layout. Fewer, smaller files that load early keep both problems small.

WOFF2. Google's web.dev guide says it has the widest browser support and the best compression, and Webflow's help pages recommend it for uploaded fonts.

Swap shows text at once and always changes to the web font when it loads. Optional avoids the late change, but a slow font may not show on that visit. Use swap when the brand font must appear, and match the fallback font to keep the shift small.

No. One variable file can replace several weight files, but web.dev notes a variable font is usually larger than a single static file. It pays off when a design uses several weights of the same family.

Self-hosting removes the extra connection to another server and keeps visitor IP addresses on your side. It is not faster by default, so serve the files from a fast host with long cache times and preload the key one.

Yes, for fonts you upload. In Site settings, Fonts tab, each custom font has a font display setting and a fallback font you can edit. Webflow's help page suggests swap to avoid invisible text.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.