Skip to content

Technical SEO

Web Fonts and Page Speed: Fixing Slow, Flashing Text

By Shayan Ahmad · · 7 min read

Web Fonts and Page Speed: Fixing Slow, Flashing Text (WhiteLinko blog banner)

Custom fonts make a site look like itself, and they are a frequent cause of slow, flashing text. The browser has to download the font files before it can paint the words in the typeface you chose. If those files are large, or if they arrive late, visitors see a blank space, a fallback font that suddenly swaps, or a delayed page. You can keep the brand typeface and still make this much cheaper.

Why Web Fonts Slow a Page Down

A font file is just another asset, but it sits on a critical path. Text is usually the main content of the page. If the browser waits for the font before showing that text, the visit feels broken. If it shows a fallback first and then swaps, you get a flash of unstyled text, often called FOUT, or a flash of invisible text, FOIT, when the words are hidden until the font arrives.

The usual causes of a slow swap are easy to recognise:

  • The family includes weights and styles you never use, such as extra-light, black, or rarely used italics.
  • The files contain glyphs for languages your site does not write in.
  • The font is hosted on a third-party domain, so the browser has to open another connection before the download starts.
  • The CSS waits too long, or not long enough, before it shows a fallback.
  • Several families are loaded for a single template, when two would have done.

None of this means you should drop back to system fonts on every site. It means each family you add should earn its place, and each file should be as small as you can reasonably make it.

Subset the Files So They Only Contain What You Use

Most commercial and open fonts are shipped as a full set of characters. A marketing site that only ever publishes in English does not need every accented character for every language, and it often does not need old-style figures, rarely used symbols, or extra typographic sets.

Subsetting builds a smaller file that contains only the characters you need. Many foundries and font hosting services already offer this, and there are build tools that can generate subset files as part of a front-end pipeline. For a typical English-language site, a well-subset font file is often a fraction of the original size.

If you publish in more than one language, you can still subset, just more carefully. Serve a Latin subset to pages that only need it, and a wider subset where you actually use those characters. Do not ship one giant file to every page "in case".

Also drop the weights you do not use. If the design only calls for regular and bold, do not load medium, light and extra-bold as well. Each weight is another file, and each file can block or delay text on the first visit.

Host, Preload and Decide How Text Should Appear

Once the files are smaller, the way you deliver them still matters.

Host the fonts yourself when you can

A third-party font host is convenient, but it adds a connection to another domain and can bring extra CSS you do not need. Self-hosting the subset files on your own domain, or on a CDN you already use, is usually faster and gives you more control. Check the licence first, because some foundries restrict self-hosting or require their own kit.

Preload only the critical font files

Preloading tells the browser to fetch an important file early. That is useful for the one or two font files used by the heading or body text in the first screen. It is not useful for every weight and every family. Preloading too many fonts competes with the hero image and the main stylesheet for early bandwidth.

Preload the regular body weight, and perhaps one heading weight if it appears in the first screen. Leave the rest to load normally. Make sure the preload URL matches the file the CSS will actually request, including the format, or the browser will download the font twice.

Choose a font-display value on purpose

The font-display setting in your CSS tells the browser how long to wait, and whether to show a fallback in the meantime. The details vary by browser, but the practical choices are:

  • swap shows a fallback quickly, then switches to the custom font when it arrives. People can read immediately. They may see a brief change in shape or spacing.
  • optional is more restrained. If the font is not already available, the browser may stick with the fallback on that first visit. This avoids a late swap and is often a good choice when speed is more important than a perfect first paint of the brand typeface.
  • block hides the text for a period while it waits. This is what creates invisible text, and it is usually the wrong default for a content or commerce site.

For most sites, swap is a sensible default. Pair it with a fallback font that is close in size and width, so the swap does not shove the layout around. If you have never set font-display at all, you are leaving this behaviour to the browser, and it may not be the behaviour you want.

Cut the Number of Families

Two typefaces, used with some discipline, are enough for almost every marketing site. A heading font, a body font, and a system fallback will usually do. Icon fonts are another cost. If you only need a handful of icons, a small SVG set is often lighter than a full icon font.

Look at the network panel on a cold load and list every font file. If you see families you do not recognise, they often come from a theme, a page builder, a chat widget, or a landing-page tool that ships its own typography. Remove the ones that are not part of the design. This is a common finding in technical SEO reviews, sitting alongside image and script work.

Then test. A lab run in PageSpeed-style tools will show font files on the critical path and will flag text that stays invisible for too long. Compare a first load with a repeat load, because fonts cache well once they have been downloaded. The first visit is the one to judge.

If your site is built on WordPress, a theme or a page builder is often where the extra families come from. That is worth a pass in itself, and our WordPress SEO work includes this kind of template and asset cleanup. For a wider view of how we tackle front-end performance as part of SEO, there is a useful comparison in our technical SEO notes against Impression.

A Short Order of Work

  1. List every font file requested on the homepage and one inner template.
  2. Remove families and weights that the design does not use.
  3. Subset the remaining files to the characters you actually publish.
  4. Self-host them if the licence allows, on the same CDN you already use.
  5. Preload only the one or two files needed for the first screen.
  6. Set font-display, usually to swap, and choose a fallback that is close in size.
  7. Retest a cold load on mobile and confirm the text is visible quickly.

Do this once on the main templates, then make it part of the design system so a new landing page cannot quietly add three more families.

FAQs

Are system fonts better for SEO?

System fonts are faster, because there is nothing extra to download. They are a good choice when brand typography is not essential. A well-subset, well-delivered custom font can still perform well. Search systems care about the result, not about whether you used a custom typeface.

Does a flash of unstyled text hurt rankings?

A brief, well-matched swap is usually acceptable. Long periods of invisible text, large layout shifts when the font arrives, and heavy font files that delay the main content are the problems worth fixing. Those show up in lab and field speed data.

Should I preload every font weight?

No. Preload only the files that are needed to render the first screen. Preloading the rest steals early bandwidth from the hero image, the stylesheet and the main content.

Is a font-loading JavaScript library still necessary?

Rarely, for a typical site. CSS font-display, subset files and a sensible preload usually give you enough control. A library adds more script to a problem that is often better solved by sending smaller files sooner.

Want Your Font Files Checked Against the Rest of the Page?

If the text on your homepage still flashes or arrives late, it is often one extra weight, a third-party host, or a hero fighting the font for bandwidth. I can look at the first load and tell you which files to keep, subset or drop. Request a free SEO audit and we will start there.

  • web fonts
  • page speed
  • font-display
  • preload
  • technical seo

Have a question about this for your own site?

A 15-minute call is usually enough to tell whether it applies to you and what to do first.

Book a 15-min callGet My Free SEO Audit

Related posts

All blog posts →

Talk to WhiteLinko

Want this applied to your site?

Book a 15-minute call to talk through your goals, or start with a free SEO audit: a prioritised list of fixes, reviewed by a specialist.

Free PDF · 2026 edition

The WhiteLinko SEO Checklist

Six pages of tick boxes: technical, on-page, content, local, links, AI search and GA4.

Get the checklist
Free SEO Audit