1. Home
  2. Knowledge Base
  3. Web Hosting
  4. Webalizer Server Statistics Definitions

Webalizer Server Statistics Definitions

The Linux server Plan and Custom Plan hosting accounts come default with Webalizer server statistics. If enabled for your server the URL is usually:
(if you need them enabled for your server contact support@estreet.com)

The following describes the terminology used in the statistics report. For a complete description of what all the numbers mean in the output, see the Webalizer README file: ftp://ftp.mrunix.net/pub/webalizer/README and addition definitions may also be found here:


This is another link to the same info:


Common terms used in Webalizer web statistics

Any request made to the server which is logged, is considered a ‘hit’. The requests can be for anything… html pages, graphic images, audio files, CGI scripts, etc… Each valid line in the server log is counted as a hit. This number represents the total number of requests that were made to the server during the specified report period.

Some requests made to the server, require that the server then send something back to the requesting client, such as a html page or graphic image. When this happens, it is considered a ‘file’ and the files total is incremented. The relationship between ‘hits’ and ‘files’ can be thought of as ‘incoming requests’ and ‘outgoing responses’.

Pages are, well, pages! Generally, any HTML document, or anything that generates an HTML document, would be considered a page. This does not include the other stuff that goes into a document, such as graphic images, audio clips, etc… This number represents the number of ‘pages’ requested only, and does not include the other ‘stuff’ that is in the page. What actually constitutes a ‘page’ can vary from server to server. The default action is to treat anything with the extension ‘.htm’, ‘.html’ or ‘.cgi’ as a page. A lot of sites will probably define other extensions, such as ‘.phtml’, ‘.php3’ and ‘.pl’ as pages as well. Some people consider this number as the number of ‘pure’ hits…. Some other programs refer to this as ‘Pageviews’.

Each request made to the server comes from a unique ‘site’, which can be referenced by a name or ultimately, an IP address. The ‘sites’ number shows how many unique IP addresses made requests to the server during the reporting time period. This DOES NOT mean the number of unique individual users (real people) that visited, which is impossible to determine using just logs and the HTTP protocol (however, this number might be about as close as you will get).

Whenever a request is made to the server from a given IP address (site), the amount of time since a previous request by the address is calculated (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’, and this total is incremented (both for the site, and the IP address). The default timeout value is 30 minutes, so if a user visits your site at 1:00 in the afternoon, and then returns at 3:00, two visits would be registered. Note: 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. Note: Since only pages will trigger a visit, remotes sites that link to graphic and other non- page URLs will not be counted in the visit totals, reducing the number of false visits. 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”.

Amount of data transferred from the server to visitors’ Web browsers. This measures how much outgoing traffic a Web site is generating.
Note: A kilobyte is 1024 bytes, not 1000 🙂

Pages leading visitors to your Web site. This helps track which search engines people are successfully reaching your site through, as well as other sites that are linking to you.

What kinds of browsers your visitors are using. This helps your Web builder determine the level of technology used by people accessing your Web site.

Which pages in your site are most popular. This helps track which pages are popular—and which ones need work.

Response Code
Codes that begin with a 2 or 3 – for example, Code 200 – do not indicate problems. However, a Code 404 signifies that someone tried to access information on your Web site that could not be found. This could be because you’ve deleted a page or have a problem on your site. It could also indicate that the server is overloaded with traffic or that the user was having an access problem.

Entry/Exit pages
Those pages that were the first requested in a visit (Entry), and the last requested (Exit). These pages are calculated using the Visits logic above. When a visit is first triggered, the requested page is counted as an Entry page, and whatever the last requested URL was, is counted as an Exit page.

Based on the top level domain of the requesting site. This is somewhat questionable however, as there is no longer strong enforcement of domains as there was in the past. A .COM domain may reside in the US, or somewhere else. An .IL domain may actually be in Isreal, however it may also be located in the US or elsewhere. The most common domains seen are .COM (US Commercial), .NET (Network), .ORG (Non-profit Organization) and .EDU (Educational). A large percentage may also be shown as Unresolved/Unknown, as a fairly large percentage of dialup and other customer access points do not resolve to a name and are left as an IP address.

Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact E Street Support