When running a blog it is interesting to see who is visiting ones website, where these visitors come from and what they do onsite. Since all versions of WordPress do not come with any visitor statistics so far, every blogger or blog owner has to implement his own solution to track visitors and display statistics.
Different kinds of WordPress visitor statistics are available: External tools such as Goole Analytics or Woopra, WordPress internal plugins such as StatPress Reloaded, CyStats or WassUp and mixtures of internal and external tools, such as the WordPress.com stats plugin, that stores and computes all data on the WordPress.com servers but can easily be integrated into ones blog.
This blog post is about the blog integrated plugin StatPress Reloaded. I will start with a description of the plugin in general, then point out its advantages and disadvantages and finish by giving a conclusion.
The StatPress Reloaded WordPress plugin is maintained by Manuel Grabowski. It is based on StatPress, which was originally developed by Danielle Lippi. It is not very flexible but it offers the mostly used standard statistics directly in the dashboard:

Further statistics are available in the “details” page of the StatPress Reloaded menu:
A special “visitor statistics” page delivers further insights to where the last visitors came from and what they have done on the blog.
The current version of StatPress Reloaded is 1.5.21. Following Manuels posts in the StatPress Reloaded support forum, he’s planning an entirely new version of StatPress Reloaded. StatPress Reloaded can easily be downloaded from the WordPress.org plugin directory.
Since StatPress Reloaded is entirely part of the WordPress installation, all data is owned by the owner of the blog. StatPress Reloaded comes in multiple languages (about 18…), is easy to install and delivers lots of different statistics.
The most important disadvantage of StatPress Reloaded is its database structure. As long as there are only about one hundred visitors per day taking a look at the blog, there is no problem. But as soon as the number of visitors rises the performance of StatPress Reloaded decreases; luckily especially in the administration panel only.
Another disadvantage of StatPress Reloaded is that there are a lot of browsers, operating systems, spiders, etc. StatPress Reloaded does not know. The only chance to correctly assign these is to add them manually to specific files in the plugin’s directory or to pray that they are part of the next version of the StatPress Reloaded plugin. There is no webserverice or something similar that can be asked for updates.
As said, the most important statistics are available, but there’s no easy way to take a look at the development of visits or hits over the last weeks for example. Additionally, the dashboard is not customizable.
Taking a look from a programmer’s perspective, the plugin’s program code lacks a good structure and does not seem to be well maintainable and expandable. This might be a sign that one should not wait for too huge improvements of the current version.
StatPress Reloaded should be good enough for WordPress blogs that do not have too much visitors and do not require too complex web analytics. If the new version of StatPress Reloaded (StatPress Reloaded Reloaded?) will ever be finished, it might be a huge improvement and overcome the current disadvantages.
Autor: Andre Kolell
Datum: Mittwoch, 20. Mai 2009, um 11:04 Uhr
Thema: (Web) Development
Trackback: Trackback-URL | Feed zum Beitrag: RSS 2.0
Ich war ja etwas abgeneigt gegen diese Plugin, da ich Google Analytics nutzen. Aber nun werde ich mir das Plugin doch einmal anschauen.
Hey, danke dafür! Werd’s mal ausprobieren.
Na, aber gerne! Hab auch schon Benni inforiert das ich wohl über einige verschiedene Plugins dieser Art in nächster Zeit berichten werde.
Und danke nochmal für die Gravatar.com-Empfehlung; hab einen Avatar für mich angelegt und die Avatare auch in den Blog eingebunden (ggf. Stylesheets aktualisieren).
Lol immer ich Ihr Blog zu besuchen muss ich haben “Google Translate” offen auf ein anderes Register!
Why, this article is written in English?! Google Translate is not that good (or is my English that bad)?! ;)