


How to Load Fonts in a Way That Fights FOUT and Makes Lighthouse Happy
Apr 02, 2025 am 04:07 AMWeb font implementation seems straightforward: select fonts, grab the code, integrate, and verify display. Many use Google Fonts daily, simply adding its <link>
tag. However, Lighthouse often flags this as problematic. Why? Let's explore eliminating render-blocking font stylesheets and creating an optimal setup that pleases Lighthouse while preventing the dreaded Flash of Unstyled Text (FOUT). We'll use only HTML, CSS, and JavaScript for broad applicability.
Render-Blocking Fonts Explained
Browser website loading involves creating a render tree from the DOM (HTML object model) and CSSOM (CSS selector map). This is part of the critical render path. The browser needs to load and parse the HTML and all linked CSS files.
A typical Google Fonts stylesheet looks like this:
<code>@font-face { ? font-family: 'Merriweather'; ? src: local('Merriweather'), url(https://fonts.gstatic.com/...) format('woff2'); }</code>
While seemingly small, these stylesheets, especially when loaded from external CDNs, cause delays. The browser must wait for the stylesheet and then the referenced font file to load, extending the render time. This makes the font file part of the critical render path.
Content is paramount. To prioritize it, minimize the critical render path to essential resources (HTML and critical CSS), deferring everything else, including fonts, until after rendering. This prevents users on slow connections from encountering frustrating blank screens while waiting for fonts to load.
Optimal Font Loading
Harry Roberts' approach is excellent:
- Preconnect: To the font origin.
- Preload: The stylesheet asynchronously, low priority.
- Asynchronous Loading: Load the stylesheet and font file after content rendering using JavaScript.
- Fallback Font: For users with JavaScript disabled.
Implementation:
<link crossorigin="" href="https://fonts.gstatic.com" rel="preconnect"> <link as="style" href="https://fonts.googleapis.com/css2?family=Merriweather&display=swap" rel="preload"> <link href="https://fonts.googleapis.com/css2?family=Merriweather&display=swap" media="print" onload="this.media='all'" rel="stylesheet">
The media="print"
attribute gives the stylesheet low priority, excluding it from the critical render path. onload
switches the media to all
after loading. Self-hosting fonts can also help, but CDNs often remain necessary.
This optimization, however, introduces FOUT.
Addressing FOUT
FOUT is the visible shift from fallback to web font. Mitigation involves:
- Suitable Fallback Font: Closely matching the web font.
- Matching Styles: Adjusting fallback font styles (size, line-height, etc.) to match the web font.
- Style Clearing: Removing fallback styles once the web font loads and applying web font styles.
The CSS Font Loading API helps detect web font loading. While libraries like Typekit's loader exist, they are outdated and unnecessary given our efficient asynchronous loading. The API's check()
function determines font availability:
document.fonts.check("12px 'Merriweather'");
Ensure an HTML element with the web font declaration exists (even hidden) for the API to track. The font name in check()
must match the CSS declaration.
A simple listener using this API smoothly transitions between fonts, minimizing FOUT. Error handling and a JavaScript-disabled fallback are crucial.
Implementation Details
The HTML includes a hidden <div> with the web font applied, essential for API tracking. CSS uses classes to manage styles for fallback and web fonts. JavaScript uses <code>setInterval
to periodically check font loading via the API, applying the appropriate styles and clearing the interval once loaded. Error handling ensures fallback styles are applied in case of API issues.
Gatsby Implementation
A Gatsby plugin simplifies this process, separating configuration (gatsby-config.js
), server-side code (gatsby-ssr.js
), and client-side code (gatsby-browser.js
). The plugin manages preload, preconnect tags, hidden font elements, and the font loading listener.
A pre-built gatsby-omni-font-loader
plugin is available for easy integration.
Conclusion
Prioritizing content is key. Asynchronous font loading, combined with a font loading listener and a carefully chosen fallback font, ensures a smooth user experience, eliminating render-blocking issues and minimizing FOUT. Consider using a pre-built plugin for simpler implementation in Gatsby.
The above is the detailed content of How to Load Fonts in a Way That Fights FOUT and Makes Lighthouse Happy. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
