Testing my site with Google's pagespeed

[tom12c]

And I've come across a situation where I'm trying to figure out the best way to address it.

It tells me this...

The following resources are explicitly non-cacheable. Consider making them cacheable if possible:

And then lists a long list of files which are not cached. I'm trying to figure out...why isn't it being cached?

I have add expires headers on the various file extensions that it shows (in apache). The cache works on other pages (although these files might not be includes in the other pages).

What concerns me is that it says they are explicitly non-cacheable.

Any ideas?

If you need more information, please let me know. Thanks!

[phranque]

which HTTP Response headers are being sent with the non-cacheable objects?

[JS_Harris]

explicitly non-cacheable would also mean that when you search Google for your pages they would not have a link to view a cached copy in the serps, is this so?

Is there a meta tag stating no-cache by chance? (sometimes answers are obvious thus hard to spot)

[phranque]

the robots noarchive meta tag (and the equivalent X-Robots-Tag HTTP Header) would only affect the cache link in search results.
these are part of the robots exclusion protocol and would have no effect on browser or proxy server cacheing, which is the performance factor of which i believe google pagespeed would be referring.

[tom12c]

phranque: how would i check that?

[phranque]

the only thing that can make an object "explicitly non-cacheable" is a response header, so i would look at your response headers for those objects.

there are many ways to do this such as the "LiveHTTPHeaders" [livehttpheaders.mozdev.org] add-on for firefox.