Taking Woopra for a test drive

John Pozadzides sent me a Woopra invite several weeks ago and I eventually signed up last week so it’s been collecting stats on this website for a while. John did an interview with Cali Lewis of Geekbrief which goes some way into explaining why Woopra is worth checking out. It was after watching that video that I decided to sign up.

Woopra has a neat Java based desktop interface but initially I only used the web interface. That’s not so bad, but it’s static and doesn’t have all the bells and whistles of the desktop app. I have to confess, I was slow to install the desktop client, simply because I have a “Oh no, Java is too much trouble” switch in my brain from long ago when I attempted to install the JRE. This time it was much easier, thanks to Ubuntu’s repositories.

$ sh woopra_unix.sh
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.6.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
You can also try to delete the JVM cache file /home/donncha/.install4j
$ rm -fr .install4j
$ aptitude install sun-java6-jre
$ sh woopra_unix.sh

After installing the Java runtime, installation of Woopra was simple. I’ve been looking at it now for a few hours and it’s nice. The ticker tape stats at the bottom are a neat touch, especially the up and down markers that give an indication of how your traffic compares with the day before.

Unfortunately I don’t obsess about traffic stats any more. If I did, I would absolutely love this application. If I was targeting a particular keyword and honing the SEO aspects of my site then I would find this Woopra invaluable. Like Google Analytics, I’m confident Woopra will become a useful tool I’ll come back to when it’s needed. It doesn’t even use that many resources. I barely see it ping home for new data and the Java app is reasonably light.

Oh yeah, I haven’t obscured any of the stats in the screenshots. This blog gets several thousand hits a day if you’re interested, although none from Turkmenistan apparently. I guess if I had Woopra running when Turkmenbashi died it may have showed a blip or two of traffic from that region!

Author: Donncha

Donncha Ó Caoimh is a software developer at Automattic and WordPress plugin developer. He posts photos at In Photos and can also be found on Google+ and Twitter.

5 thoughts on “Taking Woopra for a test drive”

  1. Hey Donncha,

    Glad you finally had the time to check it out! 🙂 I’m assuming that you are using the WordPress plugin right? Not just the JavaScript you plug in by hand? Because it makes a BIG difference!

    Check out Mark Ghosh’s comments and tips on things you need to know about Woopra. Once you’re using the plugin, it takes your Blog Voyeur to the next level!

    Ping me if you need anything as usual…


  2. Woopra is really nice, fast and going on.. for a beta status.. wow.

    More speed? Take a local .sh file to grab the woopra.js and setup a cron.. and change the woopra js code, of course, in your website..



    INSTALL_IN=/htdocssdsdsd(where to save)


    UA=”Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20070309 Firefox/″

    cd $MYTMP

    curl –header “Pragma:” -f -s -A “${UA}” -m 1800 –retry 15 –retry-delay 15 –max-redirs 8 -O $WOOPRA_JS_URL

    chmod 644 $MYTMP/woopra.js

    cp -r $MYTMP/woopra.js $INSTALL_IN

    cd $OLDPWD

    exit 0;


    INSTALL_IN=/htdocssdsdsd(where to save)

    change the part after =

    have a nice day 😉

  3. Just thought I’d give you a heads up. Woopra 1.3 RC1 is out and has been totally recoded under the hood. Hard to believe it can get prettier, but it is, and it continues to push Java Swing capabilities. Amazing stuff.

Leave a Reply