[wp-trac] [WordPress Trac] #41071: Twenty Seventeen Theme Font Creates a Single Point of Failure

[WordPress Trac]

#41071: Twenty Seventeen Theme Font Creates a Single Point of Failure
--------------------------------------------+-----------------------------
 Reporter:  jhabdas                         |      Owner:
     Type:  defect (bug)                    |     Status:  new
 Priority:  normal                          |  Milestone:  Awaiting Review
Component:  Themes                          |    Version:
 Severity:  normal                          |   Keywords:
  Focuses:  ui, accessibility, performance  |
--------------------------------------------+-----------------------------
 In attempting to develop locally using the Twenty Seventeen theme I have
 noticed the round trip to Google to pull down a Web Font creates a single
 point of failure. Steve Souders did quite a bit of work in this area
 several years ago:

 https://www.afasterweb.com/2015/08/15/avoiding-a-single-point-of-failure/

 For Web Fonts the problem is quite bad because they cannot be deferred
 like scripts without creating a FOUT/FOUC. So I'm curious, why not simply
 host the Web Fonts locally? Why create a SPOF by relying on an external
 stylesheet to load the Web Font?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/41071>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform