News for hackers. Stuff that matters.
Re:REM vs. EM – The Great Debate by hetfeld on Saturday March 12, 2016 @03:55PM (#11274510)
This blog has 3 FOUTs - first - the default fonts appear, next - all fonts disappear and after this everything appears as it was at the first time and only after it the correct fonts are loaded.
Re:REM vs. EM – The Great Debate by wanda on Saturday March 12, 2016 @04:06PM (#11274552)
That's Typekit for you, I guess.

This is why

    font-display: < auto | block | swap | fallback | optional >
is going to be useful.

More info: https://tabatkins.github.io/specs/css-font-display/

----------

Alternatively, something I've been trying is loading fonts in an embedded stylesheet (<style></style>) in the <body> element, loading critical CSS in the <head>.

This results in content being displayed in a base/system font initially, and then when the web font is loaded in the body, it replaces the base font, but without blocking render and at the same time resulting in only one brief FOUT.

Re:REM vs. EM – The Great Debate by kjaer on Saturday March 12, 2016 @07:48PM (#11275540)
There's also over half a megabyte that could've been saved if he had scaled and compressed his images losslessly, probably up to 1MB with a bit of lossy compression.