: Why not split it out and leave it on Akamai? Moving to jQuery / jQuery UI on Google is going to bring in the overhead of a DNS lookup for Google, TCP slow-start (although Google 'cheat'

@Sent6035632

Why not split it out and leave it on Akamai?

Moving to jQuery / jQuery UI on Google is going to bring in the overhead of a DNS lookup for Google, TCP slow-start (although Google 'cheat' at this with a higher initial congestion window)

Are jQuery / jQuery UI a single file on the Google CDN or multiple ones - in which case there's the latency of the extra requests?

Based on something I read (which I can't find now) apparently the odds of finding a matching version of jQuery in the browser cache is lower than expected - mainly due to all the different version numbers in use and the limited size of browser caches.

Could you do some A/B testing, say push 10% traffic down the Google CDN route and measure real-user page load times?

Edit:
Here's a post that looks at the versions of jQuery in use from Google's CDN and comes to the conclusion that using jQuery from Google's CDN isn't likely to benefit your first-time visitors much - statichtml.com/2011/google-ajax-libraries-caching.html

Vote Up Vote Down

Login to post a comment!