• Dan Charlesworth, almost 8 years ago

    I swear the last three articles I've seen about web font performance have loaded like this:


    4 points
    • Gajus Kuizinas, almost 8 years ago (edited almost 8 years ago )

      Thats cringeworthy. However, if you look at the source code, the page is not using the technique described in the post. It is using https://typekit.com/, which is probably what most blogs use nowadays. And thats not a bad thing. Blog is just a medium to share thoughts. It is not supposed to implement every thought/technical architecture it describes.

      2 points
    • Jonathan SuhJonathan Suh, over 7 years ago

      It's better than the alternative, FOIT, where the text goes invisible until the font is loaded. On mobile and spotty connections, the time the text is invisible is more noticeable—sometimes several seconds to indefinitely.

      2 points
    • Mike HeitzkeMike Heitzke, over 7 years ago

      Painful, sure, but I appreciate that the fonts aren't blocking render. I don't have the stomach to do it on my own properties

      0 points
  • Dan DiGangiDan DiGangi, over 7 years ago

    Image alt

    Me waiting for HTTP2 to get standardized so we can eliminate these issues entirely and focus on bigger problems.

    2 points
  • Ed AdamsEd Adams, over 7 years ago (edited over 7 years ago )

    I hope we get this soon, or at the very least a polyfill.

    Is this even something a polyfill could do in the mean time?

    0 points
  • Askar HussainAskar Hussain, over 7 years ago

    I still wonder why there's a simple solution to counter this issue so far. This pushed me to try a few web font providers to see who can do better and so far Google Web Fonts seem to be better in terms of that (ugly!) lag. TypeKit and FontDeck's javascripts are considerably laggy to give me a headache. Are we on 2015 or what?

    0 points
  • Mike HeitzkeMike Heitzke, over 7 years ago

    I don't disagree that would help, but there are numerous issues at play here.

    • Being able to customize the delivery of these fonts at a more granular level would be good. Typography.com sending me a bunch of huge data-uri is kind of a bummer for performance.

    • At our current state of internet speeds, allowing for more concurrent steams would help assets fetching/download (for desktop anyway). Http2 allows for unlimited concurrent steams by default vs ~8 we can do now. (from what I understand anyway)

    0 points
    • Ed AdamsEd Adams, over 7 years ago

      Typography.com sending me a bunch of huge data-uri

      That's their crappy anti-piracy measures. They are happy to have your site be slow so long as their precious fonts don't get stolen. It totally sucks.


      Ideally, yes.

      0 points