Web Performance Optimization & Lighthouse · Aula

Otimização do carregamento de fontes

Implemente `font-display`, pré-carregamento e criação de subconjuntos para garantir que as fontes da Web sejam carregadas com eficiência, sem causar mudanças de layout.

Otimização do carregamento de fontes é uma aula grátis de Web Performance Optimization & Lighthouse no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Web Performance Optimization & Lighthouse, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Web Performance Optimization & Lighthouse inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Why Optimize Fonts?

Web fonts make websites beautiful and unique, but they can also be a major source of performance bottlenecks. Large font files mean longer download times, which directly impacts your site's overall speed and user experience.

Slow font loading can lead to issues like 'Flash of Unstyled Text' (FOUT) or 'Flash of Invisible Text' (FOIT). In this lesson, we'll learn practical techniques to load fonts efficiently.

Control Font Loading with `font-display`

The font-display CSS property gives you control over how web fonts load and display. It tells the browser what strategy to use while a font is still downloading, helping to prevent jarring visual shifts.

auto: The browser's default behavior.
block: Short block period (invisible text), then infinite swap.
swap: Very short block period (invisible text), then infinite swap.
fallback: Very short block, then short swap, then permanent fallback.
optional: Very short block, no swap, permanent fallback.

`font-display: swap` in Action

font-display: swap is a popular choice for balancing performance and aesthetics. It tells the browser to use a fallback font immediately. Once your custom web font is downloaded, it 'swaps' in, replacing the fallback.

This ensures text is always visible, prioritizing content readability over font styling during the initial load.

@font-face {
  font-family: 'MyWebFont';
  src: url('mywebfont.woff2') format('woff2');
  font-display: swap;
}

`optional` and `fallback` Strategies

Other font-display values offer different trade-offs:

fallback: Gives the custom font a very short block period (around 100ms) and a short swap period (around 3s). If the custom font isn't ready within these times, it uses a fallback font permanently.
optional: Similar to fallback, but the browser decides if the custom font is downloaded at all, based on network conditions. If the font is not downloaded quickly, the fallback is used permanently, avoiding any layout shift.

Preloading Critical Fonts

Normally, browsers discover fonts when they parse your CSS. However, you can tell the browser to fetch a resource *earlier* than it would normally discover it using preloading.

For fonts, <link rel="preload"> means the browser can start downloading them even before the CSS that uses them is fully parsed. This significantly reduces the time until text is displayed with the correct font.

How to Preload a Font

You can preload fonts by adding a <link> tag in your HTML's <head> section. It's crucial to include as="font" and crossorigin to ensure the font is fetched correctly and to prevent double downloads.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Preload Font Example</title>
  <link rel="preload" href="mywebfont.woff2" as="font" type="font/woff2" crossorigin>
  <style>
    @font-face {
      font-family: 'MyWebFont';
      src: url('mywebfont.woff2') format('woff2');
      font-display: swap;
    }
    body {
      font-family: 'MyWebFont', sans-serif;
    }
  </style>
</head>
<body>
  <h1>Hello CoddyKit!</h1>
  <p>This text uses a preloaded web font.</p>
</body>
</html>

Reducing Font Size with Subsetting

Font files often contain hundreds, or even thousands, of characters. Many of these, like special symbols or characters for different languages, might not be used on your specific website.

Font subsetting is the process of creating a smaller version of a font file that only includes the specific characters (glyphs) your website actually needs. This drastically reduces the file size.

Why Subset Your Fonts?

Subsetting has a direct and significant impact on your website's performance:

Faster Downloads: Smaller font files download much quicker, leading to improved page load times.
Reduced Bandwidth: This saves data for your users, which is especially important for those on mobile plans.
Better User Experience: Less waiting means users see your content, styled correctly, much faster.

Tools like Font Squirrel's Webfont Generator or Google Fonts can help you subset.

Test Your Font Knowledge

Which of the following are effective strategies for optimizing web font loading and performance?

Font Loading Recap

We've covered essential techniques for optimizing web font loading:

font-display: This CSS property controls how fonts render during download, preventing FOUT and FOIT.
Preloading: Using <link rel="preload"> in your HTML fetches critical fonts earlier, speeding up their availability.
Subsetting: Reduces font file size by including only the characters your website actually needs.

By applying these strategies, you can significantly improve your website's perceived performance and deliver a smoother user experience.

Perguntas Frequentes

A aula “Otimização do carregamento de fontes” é grátis?

Sim — o texto completo de “Otimização do carregamento de fontes” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Web Performance Optimization & Lighthouse, atualize para CoddyKit PRO. O curso de Web Performance Optimization & Lighthouse inclui 4 aulas no total.

O que vou aprender em “Otimização do carregamento de fontes”?

Implemente `font-display`, pré-carregamento e criação de subconjuntos para garantir que as fontes da Web sejam carregadas com eficiência, sem causar mudanças de layout. Você pratica Web Performance Optimization & Lighthouse com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Web Performance Optimization & Lighthouse?

Nenhuma experiência prévia é necessária. Web Performance Optimization & Lighthouse no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Otimização do carregamento de fontes”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Web Performance Optimization & Lighthouse?

Sim. Cada aula de Web Performance Optimization & Lighthouse inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

← Voltar para Web Performance Optimization & Lighthouse