Cache static content: F
|
02-06-2013, 01:40 AM
Post: #2
|
|||
|
|||
RE: Cache static content: F
The issues won't be related to the delay in the first view, the requests get loaded anyway but it will make later repeat views slower. It looks like you are running the content through Page Speed Service as well which is adding a layer of obfuscation to your actual headers (I think they may have a default of 5 minutes if the origin doesn't specify an expires).
In W3C there is a tab in the settings for using the browser cache. You need to change the setting to something like cache-control: public (with an expires time). I believe the default setting makes the static resources not cacheable. |
|||
02-06-2013, 02:30 AM
Post: #3
|
|||
|
|||
RE: Cache static content: F
Thank you very much!
I removed the google page speed service, I was not sure if the website was loading better or not. I tried to run the test again and the result is much worse, please take a look http://www.webpagescreenshot.info/img/39...01362333PM In my browser cache settings "Cache control headers" is not checked. http://www.webpagescreenshot.info/img/99...01362749PM Do you think I can improve the loading time and speed test result if I just enable the cache control headers? Is there any other advices? |
|||
02-07-2013, 02:46 AM
Post: #4
|
|||
|
|||
RE: Cache static content: F
Looks like the cache headers your YOUR actual content is fine but there is a bunch of 3rd-party content that is not (juiceadv.com in particular).
|
|||
02-07-2013, 11:16 AM
Post: #5
|
|||
|
|||
RE: Cache static content: F
Most of the No-Max Age requests are for ads which by nature aren't cached and shouldn't be. You're never really going to have a perfect cache static score if you have ads on your site.
|
|||
01-05-2014, 01:33 AM
(This post was last modified: 01-05-2014 01:36 AM by ozguy61.)
Post: #6
|
|||
|
|||
RE: Cache static content: F
(02-07-2013 11:16 AM)Chris Stark Wrote: You're never really going to have a perfect cache static score if you have ads on your site. That would depend on the type of "ads". If your using, say, static banners and feeding them from your own domain or a CDN then it shouldn't be an issue. Where this seems to become an issue, is accessing content dynamic, fonts etc from another url. While my Cache content is not an F, it's a C and the urls causing the issue are: FAILED - (163.6 KB, compressed = 110.8 KB - savings of 52.9 KB) - themes.googleusercontent.com/static/fonts/ubuntu/v4/nsLtvfQoT-rVwGTHHnkeJj8E0i7KZn-EPnyo3HZu7kw.woff FAILED - (157.4 KB, compressed = 111.0 KB - savings of 46.3 KB) - themes.googleusercontent.com/static/fonts/ubuntu/v4/hHs22WBTTzMhSqc5uBBDKg.woff I've given up trying to fix it. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)