Panda Change History
Google’s Panda Becomes A Penguin
Posted 526 days ago

On April 19th last, Google released 3.5, an update to its Panda algorithm. On April 24th, the Penguin flew into town with a charmingly limited repertoire: a broad grin;…

Google's SSL Change
Google’s SSL Search Query Change
Posted 593 days ago

Google Panda 2.5.3 – Query Encryption
Right, oh yeah: on Tuesday, October 18th 2011 Google announced that signed-in users (users signed in their Google account) will, by default, be routed…

Google Algorithm Change History
Google Panda Change History
Posted 614 days ago

Launching fearlessly into a critique of things Google in order to get a grip on the molten lava that is the number of SERP formats growing in number and…

Did I Mention Panda?
Did I Mention Panda?
Posted 641 days ago

The world economic crisis? Oh, 2011, right, SEO, Panda, big changes.

Panda update in February, combined with the earlier algorithm shift that took place in January. Panda. Yeah, it was…

Google Freshness Algorithm
Google Freshness Algorithm
Posted 704 days ago

Ain't nobody dope as me, I'm dressed so fresh so clean.

Google recently announced 'a significant improvement' to its ranking algorithm that will affect about 35 percent of all searches.…

Google Caffeine
Google Caffeine
Posted 709 days ago

Launched in June 2010 across all data centers, regions, and languages, Google Caffeine was a revamp of Google’s indexing infrastructure – not the same thing as a change to…

Google Caffeine
The Provenance of Panda
The Provenance of Panda
Posted 734 days ago

Like all good bandits in the tumbleweed-strewn landscape that is the search engine morphological ecosystem (I'm coming down with a bad case of logorrhea, here, but you get my…

What is Google Panda
What is Google Panda?
Posted 742 days ago

Google Panda – this is the single biggest change since PageRank – Google has changed more in the last three years than they seem to have done in the…

What is Google Panda?
What is Google's Farmer Update?
What is Google’s Farmer Update?
Posted 742 days ago

Oh dear.
Dr. David Banner: physician; scientist. Searching for a way to tap into the hidden strengths that all humans have. Then an accidental overdose of gamma radiation alters his…

What is Google PageRank?
What is Google PageRank?
Posted 1126 days ago

Google describes PageRank as their measure of 'importance'. Authority, trust, whatever. And the PageRank score – or value – for a web page is just a number, an algorithm.

To…

What is Google PageRank?
PreviousNext

Google Tracking Code

by herestheskinny

in Web Analytics

Oh, do not ask, “What is it?” Let us go and make our visit.

Eh, right you are, Mr. Eliot. One moment please while we connect you…

A quick interjection here on asynchronous tracking code, because I think its worth migrating to asynchronous if your website is still using the traditional ga.js. And as for urchin … ah lads. Get. With. Program.

Unlike a traditional installation, asynchronous tracking optimizes how browsers load ga.js (that piece of JavaScript code that tracks your web pages) so its impact on user experience is minimized. It also allows you to put your Analytics snippet higher in the page without delaying subsequent content from rendering; this is now the Google default tracking code, unlike in the old days (ok, last year) when Google delivered up options like page tagging using a JavaScript snippet.

You’ll notice one key difference between placements of the asynchronous tracking code and the traditional tracking snippet:

  • the asynchronous snippet is placed at the bottom of the <head> section of your HTML file or template.
  • the traditional snippet is placed at the bottom of your page, just before the closing </body> tag.

Because the asynchronous tracking snippet can execute without blocking other code or content, you can place it at the bottom of the <head> section for the best tracking results.

Basically, in December 2010 Google Analytics announced an alternative tracking setup by using a “parallel rail” to execute JavaScript, meaning analytics wouldn’t slow down your site, and your site wouldn’t hold up analytics: asynchronous code; to maximize site speed and make analytics less invasive and more accurate.

This is important for your online business page load speed, because 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 the business.

  • Faster overall page load time.
  • Improved collection for short visits to rich media or script-heavy pages.
  • Collecting (and retaining) user clicks that occur before the tracking code loads.

If your site is a pillock and slow to load, analytics might not get the chance to execute, missing those visits you worked so hard to ensare: 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.

In short, if that’s possible, the Google Analytics asynch code does its thing in the lay-by while your website careers down the internet autobahn at a rate of knots; and then it catches up, like an unshakeable, long-limbed, well-trained puppy, eager and biddable.

Cute.

Previous post:

Next post: