No Mod Required

Results From My Home Page Redesign

Remember when I redesigned my home page? No? I made some changes based on the guidelines provided by usability.gov. Basically I cut down the amount of prose text and clarified the site choices available.

Well, not quite a month has passed, but I wanted to share the preliminary results with everyone anyway. By the metrics that I was targeting on that page (bounce rate and % of exit) the redesign was a resounding success. Here are the numbers:

Metric Before Redesign After Redesign Difference
Time on Page 00:00:47 00:00:38 -20.30%
Bounce Rate 35.19% 23.95% -31.94%
%Exit 33.61% 23.40% -30.38%

So people are spending less time trying to figure out what to do, are less likely to immediately leave (bounce) and are less likely overall to make my home page the last page they visit on the site. I’ll take improvements like that any time. Big ups to the Research-Based Web Design & Usability Guidelines :)

Once I get my laptop back from HP, I’ll be looking to see if I can experiment with a few more nuggets from that excellent resource. I’m definitely eying adjustments to some of the navigation pages around here. I’ll be sure to publish the results as I get them.

Books 2007 #11 Google Analytics

Google Analytics: an excellent introduction/reference for the ubiquitous Google Analytics web site statistics package. I learned a ton and will refer to the book for a long time to come as I continue to tinker with both my own tracking and the lower tier statistics package we’ll be offering clients at work. Highly recommended for web professionals of all stripes.

Automatically Track Outgoing Links in Google Analytics with Javascript

I’m currently reading the O’Reilly Google Analytics book, so of course I’m going to sandbox some stuff (albeit not here at this site.) One of the first things I seized on was the ability to track outgoing links by calling the urchinTracker() function onclick. Taking a few minutes out of my morning I put this together:

//window.onload we run this
var anchors=document.getElementsByTagName("a");
for (i=0;i<anchors.length;i++) {
    anchors[i].onclick=trackOutBoundLinks;
}

the trackOutBoundLinks function looks like this:

function trackOutBoundLinks(){
var thelink=this.href;
if (thelink.indexOf(location.hostname) ==-1 ){
   urchinTracker('outgoing:'+thelink+'');
   document.location.href=''+thelink+'';
   return false;;
   }
}

And with that you get fancy entries in your content list like this:

"/outgoing:http://www.dccomics.com/graphic_novels/?gn=7679"

Of course, the above will skew your page views, etc. so you’ll need to apply some filters and/or create a new profile, if you want to track page views in the default way in addition to tracking outgoing links, etc. but all that’s a Google Analytics matter*. The biggest JavaScript caveat is that if you’ve got any other onclick events on your anchor tags the above will muck with them. But if not, it’s that simple to start tracking outgoing links. Pretty cool, I think.

Here’s a zip file with a small script file that will insert the above into any page it’s attached to. I might write a more generic version of this that will work in any environment if I get the time, but for now if people are interested here it is to play around with. Simply upload the analytics.js to your server and attach it to the page in question and it should work:

<script src="/your-path-to/analytics.js" type="text/javascript"></script>

*albeit a pretty big one. I can’t stress enough that this code will completely skew your content reports. You need to have two profiles- one which filters against outgoing: and one which doesn’t. The one which does will track page views in the normal way, the one that doesn’t will have all the fancy outgoing links interspersed with the content reports. I am not savvy enough with analytics to solidly answer questions about that side of this business, so if you’re unsure look to some Google Analytics expert for sage advice on the ins and outs of profiles and filters. Maybe after reading the rest of this book and sandboxing these techniques for a month or two I’ll be more certain about some of these things, but for now I’m a javascript nerd who’s just exploring the GA landscape.

Quantcast and Compete report similar findings, why is Alexa so far off?

drunkenfist.com ranks 105,631 with Quantcast

Interestingly, they also provide demographic information:

“This site reaches approximately 14,368 U.S. monthly uniques. The site attracts a more African American, more affluent, slightly more male than female, teen and young adult audience.”

Compete ranks me 92,116 with 15,802 US visitors.

Those numbers, at least in terms of visitors, are reasonably close to my actual numbers (according to Google Analytics.)

So why does Alexa rank me 525,696 (290,588 latest. But the above numbers are for May anyway and my traffic has increased since)? What are the other two sites doing that Alexa isn’t? Is it something to do with the demographics of the Alexa user?