Issue 863 in page-speed: PageSpeed complains about Google files wrt caching

[page-...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 863 by stevesou...@gmail.com: PageSpeed complains about Google
files wrt caching
http://code.google.com/p/page-speed/issues/detail?id=863

When I run PageSpeed on http://observer.com/ a medium priority is "Leverage
browser caching". When I open the details for that rule it complains about
8 files, 5 of which belong to Google:

http://static.chartbeat.com/js/chartbeat.js (expiration not specified)
http://newyorkobserver.disqus.com/count.js?... (10 minutes)
http://newyorkobserver.disqus.com/count.js?... (10 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (1 hour)
http://partner.googleadservices.com/gampad/google_ads.js (1 hour)
http://partner.googleadservices.com/.../google_service.js (1 hour)
http://www.google-analytics.com/ga.js (12 hours)

It's ironic that the main complaints found by this Google tools are about
Google content. Either this is a true negative - in which case the files
should be fixed by Google, or it's a false negative - in which case the
tool shouldn't highlight them as a problem.

[page-...@googlecode.com]

Comment #1 on issue 863 by bmcqu...@google.com: PageSpeed complains about

Google files wrt caching
http://code.google.com/p/page-speed/issues/detail?id=863

We currently expect static resources to be cacheable for 1 week if they are
on the same hostname as the main URL, and 24 hours otherwise. We have two
options here:

1. decrease the "other hostname" cache requirement to 12 hours, and
consider the ga.js case good enough. we would push on the other google
resources to increase their cache lifetimes to match.

2. get ga.js and the others to increase to 24h.

I do not think we should drop the threshold below 12h.

thoughts?

[page-...@googlecode.com]

Comment #2 on issue 863 by keen...@gmail.com: PageSpeed complains about
Google files wrt caching
https://code.google.com/p/page-speed/issues/detail?id=863

I know its an old issue, but I wanna get it up again.
I totally get the point, why Pagespeed is complaining about the 2 hours of
Analytics. But is there any other way to maybe use a special kind of lazy
load to prevent this? If this stays like it is, you could never ever
achieve 100% when you include Analytics, right?

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[page-...@googlecode.com]

Comment #3 on issue 863 by phi...@aspina.com: PageSpeed complains about

Google files wrt caching
https://code.google.com/p/page-speed/issues/detail?id=863

Page speed on my site http://ansop.com is still affected by Google
Analytics. I've read that the best method is to download the JS and add it
to a file on your server and read the script from there. Is that right?