Get the most out of your Centmin Mod LEMP stack
Become a Member

WebPerf Fixing Font Awesome's fonts

Discussion in 'All Internet & Web Performance News' started by eva2000, Dec 20, 2016.

  1. eva2000

    eva2000 Administrator Staff Member

    55,180
    12,250
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,828
    Local Time:
    5:53 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Interesting article of optimising Font Awesome font sizes etc Saving the internet 2000 terabytes a day: fixing Font Awesome's fonts – Pixelambacht


     
  2. buik

    buik “The best traveler is one without a camera.”

    2,033
    525
    113
    Apr 29, 2016
    Flanders
    Ratings:
    +1,677
    Local Time:
    9:53 AM
    Theoretical you could save a few KB's download traffic with optimized forked Fonts, but as millions of sites are using a CDN to deliver Fonts. Most CDN delivered Fonts are already browser cached in your own browser.

    Serving fonts that are cached are much faster then downloading your own unique forked Fonts (because not present in browser cache).

    I tested it once with Font Awesome.
    . Its 88 ms for own Fonts vs 2 ms for Fonts that are already cached (Google fonts, Cloudflare CDN (cdnjs)) etc.
     
  3. eva2000

    eva2000 Administrator Staff Member

    55,180
    12,250
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,828
    Local Time:
    5:53 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Indeed it is the case for cached/CDN fonts. Still reducing the origin font + using a cdn is nice :)