# How To Make Fonts Non-Render Blocking

> The new "font-display" directive will make fonts non-render blocking. Here's how to use it with screenshots, along with other useful advice!

- Author: [Bhagwad Park](https://www.namehero.com/blog/author/bhagwad-park/)
- Published: 2018-12-27
- Updated: 2018-12-27
- Category: [Website Performance](https://www.namehero.com/blog/category/website-performance/)
- Web page: https://www.namehero.com/blog/how-to-make-fonts-non-render-blocking/

A short while ago, I’d written about [how to load Google fonts locally](https://www.namehero.com/blog/how-to-load-google-fonts-locally-to-speed-up-your-site/) in order to speed up your site. While we’re on the matter of fonts, we should also consider what happens to text while the fonts haven’t been downloaded yet.

One of the key principles of page speed optimization is that the page should be displayed as soon as possible. That means deferring or inlining CSS whenever possible. We inline all the CSS for “above the page” content and defer the rest.

## The Problem with Fonts

However, this approach doesn’t work too well with fonts because of one simple reason – font files are too large to inline into the HTML, and we can’t defer them because they’re needed to render the page! In the recent page speed testing tools, Google has started calling out this problem in the form of the following warning:

[![Warning about webfont Load](https://www.namehero.com/blog/wp-content/uploads/2018/12/Warning-about-webfont-Load.png)](https://www.namehero.com/blog/wp-content/uploads/2018/12/Warning-about-webfont-Load.png)

### The Challenge

What we want in an ideal solution is the following:

1. The text should be shown with a “default” font immediately
2. The font should be downloaded in the background
3. As soon as the font is available, the browser should swap out the default with the new one

Previously, there were all sorts of complicated Javascript solutions to make this happen. It was quite a mess.

## Using the “font-display” Directive

In CSS files, the “@font-face” descriptor is used to specify a font. Like this:

```
@font-face {
  font-family: 'Arvo';
  font-display: auto;
  src: local('Arvo'), url(...) format('woff2');
}
```

The [“font-display” directive](https://developers.google.com/web/updates/2016/02/font-display) is a new part of “@font-face” that make the magic above happen automatically. It has five possible values:

1. auto
2. block
3. swap
4. fallback
5. optional

We use it like this:

```
font-display: optional;
```

So adding “font-display” to the above block of code would look like this:

```
@font-face {
  **font-display: optional;
**  font-family: 'Arvo';
  font-display: auto;
  src: local('Arvo'), url(...) format('woff2');
}
```

## Values of “font-display”

Here’s an explanation of the different values of “font-display”.

### block (font-display:block)

“Block” is the most restrictive kind of option, and one that we want to avoid unless absolutely necessary. Basically it means that the text will be invisible against the page and will only show up when the necessary font has been downloaded.

This should be used only when having the text in a particular font is necessary, and it simply will not do to have it shown any other way.

### swap (font-display:swap)

“Swap” means that the font will be drawn immediately on the page with a fallback font. There is zero “block” time, meaning that the page will not wait at all for the font to load. However, as soon as the required font is available, the browser will “swap” out the fallback text in favor of the new font.

### fallback (font-display:fallback)

“Fallback” blocks the browser rendering for a *very* short period of time – like 100ms. If the font hasn’t yet been downloaded by the time it’s over, the browser will show the fallback font. When the font has finished downloading, it will be swapped out instead of the fallback font.

*However*, if the font takes *too much time* to download, then the fallback font will always be used!

### optional (font-display:optional)

“Optional” is like fallback, except that it leaves the choice to the browser to decide whether or not to download the font. It’s a good option for low Internet speed users for example.

### auto (font-display:auto)

“Auto” simply leaves the option to the browser. This is a bad idea because most browsers currently use “block” as their default!

## Support for “font-display”

font-display is supported across [all major browser versions](https://caniuse.com/#feat=css-font-rendering-controls). There are a few holdouts like Edge (as of this writing), but it should be quite safe to use for the present and the future.

## Impact on Google Page Speed Results

We include the new directive in the @font-face CSS rules like this:

[![Inserting the font-display CSS Directive](https://www.namehero.com/blog/wp-content/uploads/2018/12/Inserting-the-font-display-CSS-Directive.png)](https://www.namehero.com/blog/wp-content/uploads/2018/12/Inserting-the-font-display-CSS-Directive.png)

It makes Google happy as in the screenshot below:

[![Google PageSpeed Check for webfont Loads](https://www.namehero.com/blog/wp-content/uploads/2018/12/Google-PageSpeed-Check-for-webfont-Loads.png)](https://www.namehero.com/blog/wp-content/uploads/2018/12/Google-PageSpeed-Check-for-webfont-Loads.png)

A reminder: This is a great reason to [load your Google fonts using local CSS](https://www.namehero.com/blog/how-to-load-google-fonts-locally-to-speed-up-your-site/), since it allows you to do stuff like this. So go out there and update your web fonts!

## Related posts

- [How to Eliminate Render-Blocking Resources in WordPress (& Why You Should)](https://www.namehero.com/blog/how-to-eliminate-render-blocking-resources-in-wordpress-why-you-should/)
- [4 Caching Strategies That Will Speed Up Your Website](https://www.namehero.com/blog/4-caching-strategies-that-will-speed-up-your-website/)
- [How to Track Competitor Website Traffic in 2025](https://www.namehero.com/blog/how-to-track-competitor-website-traffic/)