At risk of being downvoted, I reject the advice in this article and instead advocate designers sticking to “core fonts” (Tahoma, etc) or CSS’s built-in family names.

I accept that brochure-style websites genuinely benefit from being able to use the corporate identity’s prescribed typeface for prose, but for non-branded content-heavy pages such as blogs and, uh, “content” the actual utility provided is, in this commenter’s opinion, overrated.

A great argument against custom fonts on the web is that the “core fonts” have been designed for the screen, especially low-DPI environments - whereas I imagine a typical latter-day web-designer will be using a Retina-screen on a Mac - causing them to lose empathy for their 96dpi brethren who have to suffer with blurry and misaligned fonts on their webpages that were clearly designed for print, not screen, use.

I filter web fonts in my main Chrome profile and I’m in no hurry to re-enable that functionality.

Is it just the case for me or does that page itself suffer from FOIT?

It's quite visible when refreshing without cache (Ctrl+F5 on FF under Linux/Windows).

I block custom fonts everywhere:

- They make the page loading slower and consume bandwith

- It does not look the way I like it

- It can cause security issues