Here's the difference we measured when using optimized fonts:

[kexej28769@nongnue]

This is where your developers can get into arguments with your designers if you're not careful. Everyone wants to see a beautifully designed website, but if you're not careful about bringing that design live, it can cause major unintended speed issues. Here are some tips on how to keep your fonts on a diet:

Use inline svg for icon fonts (like Font Awesome). This way benin number data will reduce the path of the critical chain and avoid empty content when the page first loads.
Use Fontello to create font files. This way, you can only include the glyphs you actually use, resulting in smaller files and faster page speeds.
If you're going to use web fonts, check to see if you need all the glyphs specified in the font file. If you don't need Japanese or Arabic characters, for example, see if there's a version with just the characters you need.
Use the Unicode range to select the glyph you need.
Use woff2 when possible because it is already compressed.
This article font optimization .


After reducing our font files from 131kb to 41kb and removing one external resource (use proof), the full load time on our test page dropped from 5.1 to 2.8 seconds . That’s a 44% improvement and will definitely make Google smile (see below).