This is important for SEOs concerned about site speed (who isn’t, these days?), because it means your analytics will no longer prevent your page from loading while it tries to connect to Google’s servers. Also, if you have a slow site and you’re missing a lot of credit where it’s due (because your analytics code is at the bottom of the page, waiting patiently to execute), asynch is right up your alley. Many SEOs struggle to prove their worth when sites are slow and analytics never actually executes, missing those visits you worked so hard to bring about.
The Google Analytics asynch code fixes these issues by allowing analytics to cue up events that work themselves out on the side, while the rest of your site takes care of itself. It’s like having a nice, little pack of oompa-loompas helping you out with your tracking while your site gets to breathe a little easier and load a little faster. And for the SEOs who aren’t getting credit, asynch ensures that the queue of messages to be sent to Google Analytics continues to process, even as users navigate away from the landing page. Smart oompa-loompas!
The change does require some work, though. The syntax for calling page views and events has changed a little bit to allow for these calls to be queued-up, rather than executed immediately while the world waits. But this is great news and it’s absolutely how new implementations should be carried out to maximize site speed and make analytics less invasive and more accurate.
Opinions expressed in this article are those of the guest author and not necessarily Search Engine Land. Staff authors are listed here.