Should you change from urchin.js to ga.js?

Google Analytics recently added the option to choose "Legacy urchin.js" tracking code or the new "ga.js" tracking code.

What are the advantages of GA.js over Urchin.js?

• Faster, smaller source file - which will allow for a faster download time


• Object oriented - instead of using functions


• Automatic detection of HTTPS


• Increased namespace safety

One thing to note,

If you install the new code, you must do it over your entire website all at once as the legacy code is not compatible.

Do you need to upgrade?

The experts are predicting that Google Analytics will continue to support urchin.js for another 12-18 months. No need to rush, but something to plan for.

Speed Up Google Analytics Loading Time

Every file your webpages pulls when loading adds Loading Time to your customers experience.

When you add Google Analytics code to every webpage on your website part of that code pulls a 21kb Javascript file that powers the tracking functions from Google-Analytics.com. These days, 21kb isn't a lot to worry about for your customers to download.

The problem however isn't the size of the download, it's the fact that this Javascript file, Urchin.js, (required for Analytics to function) has to be pulled from Google's website while your website is loading which can create some lengthy delays.

The solution:

Install Urchin.js on your website's server and create a CRON job to automaticaly pull the most up to date version from Google daily. Detailed instruction on Speeding Up Google Analytics.