3 ms·

They could at least gzip the damn thing or whatever their own pagespeed tool says is wrong with every asset loaded from Google

• singlow 9y ago
  It complains about the cache expiration time being too short. But there are good reasons they can't cache it longer. The short cache has no significant effect on page performance, as long as it is loaded async, but there is no way the performance tool can determine that unless it white listed it which would not be fair to someone else's tracking script.
• manigandham 9y ago
  Pagespeed is a subpar tool that really shouldn't be used much. Follow the best practices and don't try to fix every possible little complaint. As far as Google serving files though, its about as optimized as it gets. The JS file is gzip'd, served by Google's cloud network and on chrome it even uses their own QUIC protocol which is faster. It's also likely cached by the sheer amount of usage across the web so it'll probably be the fastest loading thing on your entire site.
  • corobo 9y ago
    But I want the number to be green :( Fair point, I think I've been accidentally gamified when it comes to the pagespeed test. Good call.
• untog 9y ago
  If you're very concerned about it, you can implement your own solution sending HTTP calls to GA: https://developers.google.com/analytics/devguides/collection/protocol/v1/ https://developers.google.com/analytics/devguides/collection...