Asynchronous Google Analytics is Better but Not Faster

calendarJuly 29, 2010 in Firefox , HTTP , HttpWatch , Internet Explorer , Javascript , Optimization

In December 2009, Google launched the asynchronous version of the Google Analytics script. The update aimed to address potential script blocking problems that have been extensively researched and reported by Steve Souders at Google.

Steve’s blog post about the new asynchronous loading of Google Analytics identified three potential benefits:

  1. Your pages should load faster
  2. Availability or performance problems at Google should have less impact on your site
  3. Analytics data is more likely to be collected if a user leaves a page early

Before applying the change to our web site we decide to compare the new and old versions of the Google Analytics scripts using HttpWatch 7.0 .

The following sections describe what has changed in the asynchronous Google Analytics script and the tests we performed to compare it to the traditional synchronous version.

What has Changed?

Google Analytics collects data using two components on a page:

  • A javascript file script file that is loaded from
  • A 1×1 pixel image beacon ( that passes data back to Google in query string parameters

You enable Google Analytics on a web page by calling a page tracking function in ga.js. This function automatically gathers analytics data, such as operating system and browser versions, then generates the call to the image beacon.

The difference between the two ways of loading Google Analytics is in the way that the script file is loaded. In the traditional synchronous version, two small script tags are added at the end the page’s <body> tag:

  <script type="text/javascript">
    var gaJsHost = (("https:" == document.location.protocol) ?
    "https://ssl." : "http://www.");
    document.write(unescape("%3Cscript src='" + gaJsHost +
    "' type='text/javascript'%3E%3C/script%3E"));
  <script type="text/javascript">
    var pageTracker = _gat._getTracker("XX-XXXXXX-X"); // Your GA id

The first script tag ensures that the correct HTTP or HTTPS version of the qa.js file is loaded. The second script tag then calls into the javascript file triggering the beacon image download.

These two script tags are placed at the end of the body tag to ensure that they don’t hold up the download of any other resources on the page. The disadvantage of doing this is that the analytics call may not be triggered if the user exits the page before it has completely downloaded.

The asynchronous version of the Google Analytics loading code uses a single script tag at the end of the page’s <head> :

    var _gaq = _gaq || [];
    _gaq.push(['_setAccount', 'XX-XXXXXX-X']);
    (function() {
      var ga = document.createElement('script');
      ga.type = 'text/javascript';
      ga.async = true;
      ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www')
        + '';
      var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);

It sets up the parameters required to make the call into ga.js but doesn’t invoke the function directly. A script element is added to the document allowing asynchronous download without blocking other elements of the page. The HTML 5 async attribute is also set on the script tag for browsers that support it.

Once the ga.js file is loaded and executed it looks for an array variable called _gaq and executes the function with the previously specified arguments.

Do Pages Load Faster With Asynchronous Google Analytics?

To try this out we created a version of our Download page using both versions of the Google Analytics loading code. We first tried the synchronous version with an empty cache in IE to simulate a new visitor to the page:

Synchronous GA Test With Empty cache in IE

And then with the asynchronous version:

Asynchronous GA Test With Empty cache in IE

The page load times were dominated by other components on the page. Using the asynchronous version of Google Analytics didn’t really make any difference.

We tried the same tests with a primed cache to see if there would be a greater impact when the page was loaded during a repeat visit. First the synchronous version:

Synchronous GA Test With Primed cache in IE

and then the asynchronous version:

Asynchronous GA Test With Primed cache in IE

Again there was practically no difference in the page load time of the page allowing for variability in our tests.

The reason for that is that calls to Google Analytics are incredibly fast (usually around a 100ms or less) and the download of the image beacon doesn’t block other components because it uses a different hostname.

We tried Firefox 3.6 and got almost the same results.

Conclusion: Google Analytics is so fast that you won’t see any significant improvement with the asynchronous loading version.

Would Google Performance Problems Have Less Impact With Asynchronous Google Analytics?

For this test we needed to simulate performance problems at Google. We did this by modifying the standard script snippets to call our own ASP.NET versions of the Google files that served the same content but added a 5 second delay.

For example, here’s the ASPX file we used to serve up a local copy of ga.js:

<%@ Page Language="C#" Debug="true" %>
<%@ Import Namespace=System.IO %>
  Response.AddHeader("Content-Type", "text/javascript");
  Response.WriteFile( ".\\ga.js");

We did something similar with the Google __utm.gif file so that we could add delays to either component.

Using our slow simulation of ga.js in IE 8 we found that the page’s onload event was delayed with the synchronous version of the Google Analytics:

Slow ga.js in IE with Synchronous Google Analytics

This caused the IE 8 to display the spinning icon in the current tab:

Spinning Tab Icon in IE 8

and a “Waiting…” message in the status bar:

Waiting message in IE 8 Status bar

indicating to the user that the page was not fully downloaded.

We then tried using the slow version of the __utm.gif image file. This didn’t cause a problem in IE 8 as the page loaded successfully but continued to download the image beacon in the background even with the synchronous version of Google Analytics:

Slow __utm.gif with synchronous Google Analytics

Firefox 3.6 didn’t cope as well. Delaying the download of the beacon file with the synchronous loading code had the same effect as delaying the ga.js file – the page load was delayed, the spinning tab icon was displayed and the status line indicated that it was waiting for data.

We then tried the asynchronous version of the analytics loading code. Delaying either the ga.js or utm.gif file had no effect on the loading of the page in IE; effectively hiding the issue from the web site visitor:

Slow ga.js in IE with asynchronous Google Analytics

Surprisingly, the asynchronous version of the analytics code made no difference to Firefox 3.6 when we simulated slow downloads of the Google components:

Slow ga.js loading in Firefox with asynchronous Google Analytics

Conclusion: Using the asynchronous load made IE 8 more robust to performance problems in the loading of qa.js. Otherwise it made no difference. In reality, ga.js is often cached anyway making it the less likely of the two components to be subject to performance problems.

Is Data More Likely to be Recorded by Asynchronous Google Analytics During Early Page Exits?

To test this potential benefit we changed our test pages to include a slow loading script file at the top of the body tag. The idea was to emulate what might happen on your page if a third party component, such as an ad script, started to slow down.

The script tag we added called an ASPX file than delayed 6 seconds before returning an empty script block:

  <script type="text/javascript" src='http://veryslowdownload/ad.aspx'></script>

This stopped our page being displayed for six seconds.

Using the synchronous version of the loading code in IE 8 and Firefox 3.6, we found that the Google Analytics beacon image was not downloaded if the user gave up and went elsewhere:

Early page exit in IE 8 with synchronous Google Analytics

The asynchronous loading of Google Analytics solved this problem in both browsers. The image beacon was downloaded almost immediately even though the page was blocked by the slow script tag:

Early page exit in Firefox 3.6 with asynchronous Google Analytics

Conclusion: The asynchronous version of Google Analytics helps to ensure that analytics data is gathered in IE and Firefox when the user leaves a page early.

Should I Use the Asynchronous Version of Google Analytics?

Yes, but not for the reasons you might expect. It’s unlikely to make any difference to how quickly your pages load.

The main reason to use it is that you are more likely to get analytics data if a user leaves a page early.

9 thoughts on “Asynchronous Google Analytics is Better but Not Faster

  1. Brian Kuhn says:

    Async GA will make your pages faster on pages that have scripts and other content that will load in parallel. Your download page is a particularly bad test page for this. It contains no script tags other than ga.js and contains only one image tag. This is a very non-typical edge case where there isn’t much room for improvement.

  2. Brian,

    Thanks for your comment. Our download page requires 13 network round trips to load (ignoring GA). There’s no other scripts but there are 11 image files.

    Actually, a relatively lightweight page like this would tend to highlight any benefits of the async GA loading model because GA has a larger impact that it would on a more complex page .

    The point is that the calls to GA are so fast that you’re unlikely to save more than a 100 ms even if async removed any overhead.

    Have you seen a web page where sync GA adds a significant overhead and async GA would make a difference?

  3. Brian Kuhn says:

    Your connection speed is another consideration. Resources like GA may not load as quickly in other locations or for other connection types like mobile. The goal of async is to make the perceived latency of GA the same in all of those situations.

  4. Yes, our second batch of tests did aim to investigate whether there was any benefit of async GA if GA suffered much slower download times.

    We only saw a tangible benefit with IE 8 if ga.js was slow, otherwise async GA didn’t offer any advantage.

    It would be interesting to see how async GA performed with the same test in other browsers and on mobile devices.

  5. lenel says:

    If don’t put the sync snip near the ;problem will become acute cause by slow ga.js downloading.

    And if you have some task when domready event, the sync snip also block it.

    so async snip avoid a SPOF(single point of failure) from your system may import by 3rd party content.

  6. Great testing! Brian is right, though, this doesn’t really test the performance benefits of the GA async snippet. To understand why this is so, we start by defining what “async” means. Here, GA is trying to avoid the way many browsers block when loading scripts. IE8 and Firefox 3.6 don’t have this blocking behavior, so the async snippet doesn’t have much affect (as you found). However, IE 6&7 both block when loading scripts. If you ran your test on one of these browsers, you’d see a performance gain, esp. in the worst case scenarios. Since IE 6&7 are still a significant slice of the user pie, web sites will see a performance gain when they adopt the GA async snippet.

  7. I came across this article while looking for an explanation for Google’s slow data update. Some days while I’m @ 96 absolute unique visitors, the data could suddenly jump to 160 uniques in 2 hours without any explanation or traffic boost @ all.

    I’m using the asynchronous version. Do you have an explanation for this?

  8. Web India says:

    If you are moving from fast to fastest then each ms would make a difference. I agree with Steve that several other browsers [especially want to mention mobile mini browsers and others] would see major difference. It also depends on testing bed/measures we are relying on!

  9. Josh Habdas says:

    IIRC browsers like Chrome may also do optimistic preloading of page assets before arriving at your page from a SERP such as Google, meaning the async version could be downloaded and cached in the browser before the visitor even lands on your page. Please feel free to correct me here.

Got Something to Say?

Your email address will not be published.

Ready to get started? TRY FOR FREE Buy Now