• Online Statistics
• Offline Statistics
• Raw Log files

Many other providers only provide a daily update. But at ProExe we believe in supplying the information when the site owner needs it.

With a faster turn around, the statistics can be more meaningful. For example a client is interviewed on the radio, and their website is promoted. By having quicker access to the statistics, the almost real-time impact can be seen.

Because of the number of sites hosted and the variable amount of time it takes to process logs for each site, the exact time that your stats will be regenerated cannot be determined.

Counters offer less information, and don't make your site look professional.

ProExe are often asked about remotely hosted counters, using a hidden image technique. We don't recommend these either. A lot of these companies profile your site, store a cookie on the visitors computer and slowly, but surely, build up a profile of your visitors, which they then sell on, hence making money from you without sharing revenue. We don't recommend this kind of counter at all.

Also counters can be faked, and the shown information, can't always be trusted. This can be counter productive to your website audience.

A counter simply counts the number of times anyone visits the page the counter is on.  That means if you went back to the main page five times during your one visit to the site, the counter would show five ticks.  Counters are notoriously inaccurate for this reason; some webmasters have been known to keep reloading their page to make their website more seem more popular than it really is.  Worse still, if you have one on your site, and it only shows ten ticks on the counter, this advertises that no one is coming to your site.

So long as you have a fixed IP address we add this to a configuration file, which will then not record your own activity on your own site. In fact ProExe also adds our fixed IP to the configuration, so when we are say maintaining, or developing your site; our traffic does not skew the statistics.

If you have satellite offices, or home as well as office use, we can also block this traffic being recorded as well.

The raw log files aren't affected by this method, so full logging of all activity on the website is always maintained.

Summary: specified traffic can be blocked from showing in the online website statistics.

In terms of measuring website traffic, hits are not particularly useful. Instead, you need to be thinking in terms of the number of visits your site receives.

If we take a moment to look at what a hit is, compared to what counts as a visit, you will hopefully see why this difference is important.

A hit is recorded every time a web browser (such as Internet Explorer or Firefox) requests a file from your web server. The file that is requested might be a page of text, an image, a banner advert, a piece of JavaScript, or any other file.

The majority of web pages are made up of more than one file. For example, the page you are looking at right now is produced from a main hypertext (dynamic HTML) file, plus another file containing the side menu, a graphic file for the ProExe logo, a file that contains our footer menu, and a few more files besides.

As a result, when you view this page you generate around ten hits on our web server.

A visit, on the other hand, is recorded every time someone looks at a page on a website, regardless of how many files have to be downloaded as part of that process.

So, by reading this page you have only caused one extra visit to be recorded in our web logs, but something in the region of ten hits.

If we accept that this 1:10 ratio is fairly typical, then you can see that the person who talks about having had 100 hits on his website has probably only had about 10 actual visitors. Not quite so impressive!

So, if you want to get a proper measure of how many people are looking at your web site, and avoid over-exaggerating the popularity of your site, you really need to look at the visitors figure in your web stats rather than the number of hits.

Visits are also grouped by time. Webalizer* does this by looking at the IP address of the browser and calculates the amount of time since a visitor's last request (if any). If the time difference is greater than a pre-configured 'visit timeout' value (or has never made a request before), it is considered a 'new visit'. The default timeout value is 30 minutes. So, if a browser visits your site at 2:00pm and then returns at 4:00am it will be reported as 2 visits.

* In the 'Top Sites' table, the visits total** should be discounted on 'Grouped' records, and thought of as the "Minimum number of visits" that came from that grouping instead.

**Visits only occur on PageType requests, that is, for any request whose URL is one of the 'page' types defined with the PageType option. Due to the limitation of the HTTP protocol, log rotations and other factors, this number should not be taken as absolutely accurate, rather, it should be considered a pretty close "guess".