Cache validator for Google Webfonts

user1537415 picture user1537415 · Jun 29, 2013 · Viewed 17.5k times · Source

So I'm creating an ultra optimized site, and my page load speed with https://developers.google.com/speed/pagespeed/ is 99 (out of 100).

The only thing keeping me away from full hundred is this:

By specifying a cache validator - a Last-Modified or ETag header - you ensure that the validity of cached resources can efficiently be determined.

What?! I don't know what should I do. How do I set a cache validator for google webfonts?

I've the webfont like this: <link href='http://fonts.googleapis.com/css?family=Open+Sans:400,800' rel='stylesheet' type='text/css'>.

I'm on ubuntu with apache2 if that matters.

Downloading the webfont to server and using it from there drops the score to 96 so that won't help either.

Answer

Anthony Hatzopoulos picture Anthony Hatzopoulos · Jul 3, 2013

You can't do anything about it. You can't control what headers google server sends.

I would even go so far as to say it is reporting a false positive that you should fix.

http://redbot.org/?uri=http%3A%2F%2Ffonts.googleapis.com%2Fcss%3Ffamily%3DOpen%2BSans%3A400%2C800

As you can see the resource is cached, has a max age header and is even compressed.

You site is fast enough! I wouldn't worry about getting 100. You can probably stop optimizing it.

But if you want to tinker some more, here's a few ideas on improving things, I ran a report: http://www.webpagetest.org/result/130703_H7_15KM/