Max Rozen

Prefetch your Google Fonts for Performance Gains in Gatsby

October 10, 2019 • ☕️ 2 min read

Why is Google Fonts an issue?

The cost of using a call such as

@import url(',400,900');

is that the browser first has to download the CSS file, and parse it. Afterwards, the browser downloads your fonts. This process is particularly syncronous, so we can’t download your fonts until we ask Google for the location of the font files we need.

How do we speed things up?

We can get a large performance boost by self-hosting our fonts. To do this, you would need to:

  1. Use google-webfonts-helper to figure out which fonts you needed to download
  2. Check them into your repo
  3. Reference them in your CSS
  4. Ensure that CSS is in-lined in your HTML, and among the first CSS to be read by browsers

This is a bit involved, but totally worth it. At a previous employer I managed to shave 300ms off of page load time by self-hosting fonts.

Enter gatsby-plugin-prefetch-google-fonts

Now with gatsby-plugin-prefetch-google-fonts, you can save 3-400ms with a little bit of configuration.

  1. Install: yarn add gatsby-plugin-prefetch-google-fonts
  2. Configure gatsby-config.js:
      resolve: `gatsby-plugin-prefetch-google-fonts`,
      options: {
        fonts: [
            family: `Lato`,
            variants: [`300`, `400`, `900`],



Before prefetching Google Fonts WebPageTest result

If you look at the time spent by Resource 8, 10, and 11, you can see we’re waiting quite a bit just to get the page’s fonts loaded.

It’s also not the first thing the browser does, so we’re likely going to see a flash of missing font. This also depends on what your font-display setting is in CSS.


After prefetching Google Fonts WebPageTest result

After adding the prefetch plugin, we can see Resource 2, 3, and 4 being immediately loaded once we fetch the page.

I was so impressed with these results that I wrote this blog post!

If this post helped you, I'd really appreciate a share on Twitter.

Max Rozen

Thoughts on the Web.