Add Google Analytics on solving far future caching issue, and rapidly update it (under the same URL) #1670

laukstein opened this Issue Aug 4, 2013 · 9 comments


None yet
6 participants

laukstein commented Aug 4, 2013

Google Universal Analytics
Old Google Analytics


ryankirkman commented Aug 5, 2013

Hmm, not sure I see the point of hosting the Google analytics code? I
imagine it could cause some problems with the collection process too?

On Sun, Aug 4, 2013 at 12:46 PM, Binyamin Laukstein <> wrote:

Google Universal Analytics
Old Google Analytics

Reply to this email directly or view it on GitHub


laukstein commented Aug 5, 2013

There are multiple articles about speeding up Google Analytics by serving it locally with far future caching and on using cron job to keep it updated. And Google more likely would not do anything to solve that issue.

The current browser caching is 12 hours. It is not enough to speak about performance.


petecooper commented Feb 16, 2014

This is tricky from a maintenance point of view, too. There's no obvious versioning in the .js file, and there's nothing to stop Google tweaking the file as often as they like; they don't suggest/recommend locally-hosted copies, as far as I know, so there's no onus to keep the users updated on what's going on.

That said, I'd be happy to be involved with an experiment to see how, if at all, it affects load times and data collection.


petecooper commented May 14, 2014

I've given this some more thought, and it's going to be very tricky from a maintenance point of view with the lack of versioning involved. With that in mind, I'm going to close this issue for now, @laukstein - if things change and there is scope for a cdnjs hosted GA file, I'll reopen for reference.

@petecooper petecooper closed this May 14, 2014


laukstein commented May 18, 2015

@petecooper, any updates forwarding to this issue? is outdated and discontinued.
The only relevant JavaScript file: additional issue: weak signature algorithm:

This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.


thomasdavis commented May 18, 2015

Don't think we will continue serving GA, doesn't really make sense for our setup and probably best in general to use Google's cdn as it is very widely used.


drewfreyling commented May 18, 2015

I agree with @thomasdavis


laukstein commented Jun 13, 2016

Related issue, as you can see unfortunately GA managers doesn't consider to fix their future caching issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment