« Fixing Healthcare Starts With Doctors
Exclude Administrator from Woopra Analytics »

After having bounced around between Google Analytics, WordPress.com Stats, and Woopra Analytics, I’m choosing to side with Woopra’s service for a few reasons:

• All the statistics one could ever want
• Real-time site views
• Ability to chat with site viewers
• OS X, Linux, and Windows desktop clients
• Online interface (real time) for web-based access
• Still in the beginning stages of development, so a lot more is to come.

With any analytics software, webmasters are worried about the strain the additional Javascript will have on their site’s performance. As part of Woopra’s installation process, you place the following code before the </body> of your site’s footer: <script type="text/javascript" src="http://static.woopra.com/js/woopra.js"></script>

The problem with this method is that whenever your page is loaded, an additional HTTP request (for the Woopra JS) must be made on an additional domain (Woopra’s site). Rather than doing this, if you’ve already got JavaScript files loading regularly on your site, simply add the minified Woopra JS to the end. For example, on RK.md, I’ve got several JavaScript functions loaded into a “main.js” file. I just appended the minified code to the bottom. This saves you both the extra HTTP request and domain request.

Legal

As a third year medical student at Baylor College of Medicine, my posts are intended to educate others and share my experiences from this incredible journey without violating patient privacy at all costs. These blurbs are not to serve as a replacement for recommendations provided by licensed physicians under any circumstance.