search

wthidden / googlefontdirectory

Automatically exported from code.google.com/p/googlefontdirectory
0 stars 0 forks source link

Page Speed Issues #51

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
This is a low prio issue, but I thought it'd be worth noting.

I'm embedding the fonts via @import from my stylesheet at 
http://www.manuel-strehl.de .

Then the Google Page Speed addon (1.10.2, FF3.6) complains about the following 
points:

* "Minify CSS": No whitespace compression of the CSS
* "Leverage browser caching": Expires header is less than 1 week in the future
* "Specify a cache validator": No Cache validator, like ETag or Last-Modified

I think, the first one could easily be solved, and be it by introducing a GET 
parameter ?c=1 for compression or something similar.

Original issue reported on code.google.com by bolde...@gmail.com on 11 Apr 2011 at 8:01

GoogleCodeExporter commented 8 years ago 
Google font (URL: http://themes.googleusercontent.com/static/fonts/...) getting 
highest load time in my site!!!

Original comment by kazancex...@gmail.com on 24 Jan 2012 at 5:21

GoogleCodeExporter commented 8 years ago 
On the contrary to the OP, I think this is a high priority bug.
The expires headers are set in the past, meaning that fonts from 
fonts.googleapis.com never gets cached.

Original comment by jon.ronn...@gmail.com on 29 Jun 2013 at 5:00

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi Jon! That is the CSS file, which shouldn't be cached so that when the fonts 
are updated, you get the URLs for the latest ones; the font files themselves 
are cached, though.

Original comment by dcrossland@google.com on 30 Jun 2013 at 2:36

GoogleCodeExporter commented 8 years ago 
There are no expire headers for the font css, which hurts pagespeed.

Original comment by aurorawe...@gmail.com on 9 Aug 2014 at 7:39

GoogleCodeExporter commented 8 years ago

Original comment by pathum...@gmail.com on 26 Aug 2014 at 10:16

GoogleCodeExporter commented 8 years ago 
Hi dcrossl...  This makes sense if the fonts gets updated regularly. This might 
be the case but in most instances, I doubt it. The main issue with not caching 
the CSS file is that it might block further download of stylesheets (if @import 
is used) and most devs will include the font stylesheets first to avoid FOUC, 
meaning that the site styling won't be downloaded until the 
fonts.googleapis.com CSS file is downloaded. Even if @import is not used (and 
we get parallel downloads), this one HTTP request can be very noticeable on 
mobil connections.
I'm in no position to say whether or not, caching of the CSS file is warranted, 
as I don't know how often the font files change.
But I just wanted to explain the issue in more detail.

Original comment by jon.ronn...@gmail.com on 27 Aug 2014 at 11:56