From 37a1cd8dc1308bf94cc8eeb4fa4b862a92108d68 Mon Sep 17 00:00:00 2001 From: Harry Roberts Date: Sat, 30 Sep 2023 12:12:44 +0300 Subject: [PATCH] Add update to Google Fonts article --- _posts/2020-05-19-the-fastest-google-fonts.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/_posts/2020-05-19-the-fastest-google-fonts.md b/_posts/2020-05-19-the-fastest-google-fonts.md index 7bf7c9ef..ad6d6951 100644 --- a/_posts/2020-05-19-the-fastest-google-fonts.md +++ b/_posts/2020-05-19-the-fastest-google-fonts.md @@ -7,6 +7,20 @@ main: "https://csswizardry.com/wp-content/uploads/2020/05/filmstrip-foit.png" meta: "Google Fonts is fast. Now it’s faster. Much faster." --- +
+ +

Ten-Second Version: If you really can’t +be bothered going to all of the effort outlined in this post, there is a super +rough-and-ready, ten-second, alternative approach—place your Google +Fonts stylesheet at the closing </body> tag. This +means we don’t block rendering of the entire page just for the sake of web +fonts. Instead, we apply them after we’ve styled everything else.

+ +

Please note that this may have side-effects. If you want to be very +thorough, keep reading…

+ +
+ For the most part, web fonts nowadays are faster than ever. With more standardised FOUT/FOIT behaviour from browser vendors, to the newer `font-display` specification, performance—and therefore the user—seems to have