Tobias T–

Get back to Notes expressing the moment

Comment Zach Leatherman in…

Zach Leatherman in Critical Web Fonts

Two Scoped Classes for the Flash of Faux Text (FOFT): This method complicates things a little bit more and uses two different stages of scoped classes. The first stage loads only the Roman font, then any variations of that are loaded in the second stage: Bold, Italic, Bold Italic.

Ok, let me clarify one thing first: from a research perspective this is kind of brilliant and I'm wondering why nobody did try this before. It's just the next logical step and Zach made a great case for it.

But: I really cannot get my head around this. Why would I ever want do that? I can see that someone wants to have their content as beautiful as possible – and that is supposed to be as fast as possible, but for what reasons? We save some bytes to perform just another network request, which might take several seconds, fail completely and after all will drain my battery even faster. It has been best practice to request as few resources as possible and now the future points into separate CSS, JavaScript and even Web Fonts for each individual page of our websites, just because the critical might be completely different.

Just another thing we can automate with our build tools, which we now need to run for each and every page we publish. Just to have a font which for most of the people looks exactly like all the other ones.

I don't know which talk it was I've seen at the Fronteers Conference in Amsterdam, but I remember the gist: if we remove some code, and it looks almost the same as before, maybe the code shouldn't have been there in the first place.

Also available at