Skip to content

Optimize Google Fonts #119

@TedGoas

Description

@TedGoas

Harry Roberts wrote about how referencing Google Fonts from Google's CDN might be the best way to go. I've been self-hosting because I thought that's the best performance, however I've noticed FOUT on my own production site. If anyone's gone have my site chawed, it's me, and I'm still seeing the FOUT!

Let's test out Harry's idea. I've always liked the idea of referencing Google because you get extra font-hinting that makes type look better. Also, it's simple to implement and easy to maintain.

Harry recommends this at the end of his article:

<!--
  - 1. Preemptively warm up the fonts’ origin.
  -
  - 2. Initiate a high-priority, asynchronous fetch for the CSS file. Works in
  -    most modern browsers.
  -
  - 3. Initiate a low-priority, asynchronous fetch that gets applied to the page
  -    only after it’s arrived. Works in all browsers with JavaScript enabled.
  -
  - 4. In the unlikely event that a visitor has intentionally disabled
  -    JavaScript, fall back to the original method. The good news is that,
  -    although this is a render-blocking request, it can still make use of the
  -    preconnect which makes it marginally faster than the default.
  -->

<!-- [1] -->
<link rel="preconnect"
      href="https://fonts.gstatic.com"
      crossorigin />

<!-- [2] -->
<link rel="preload"
      as="style"
      href="$CSS&display=swap" />

<!-- [3] -->
<link rel="stylesheet"
      href="$CSS&display=swap"
      media="print" onload="this.media='all'" />

<!-- [4] -->
<noscript>
  <link rel="stylesheet"
        href="$CSS&display=swap" />
</noscript>

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions