When we talk about increasing website traffic, we're really talking about several different things, including increasing hits, increasing pageviews, increasing sessions, and increasing unique visitors. For some sites, increasing pageviews will be the immediate goal because the concern is that the vast majority of visitors view only one page of the site, then leave. For others the immediate goal will be to increase the number of unique and return visitors.
Because there are multiple metrics available to webmasters when reporting traffic, a great deal of confusion surrounds the whole affair. Many webmasters refer to website hits when they report their traffic. While many people have asked about increasing hits, website hits are not a very good measure of the success of a site.
First, let's take a hypothetical tour of the process of measuring website traffic. Imagine Hypothetical Jim visiting the home page of a new website he learned about on Google.com. Hypothetical Jim visits the home page, then visits the "About Us" page, which he bookmarks. Later, Hypothetical Stu visits the home page, then leaves the site. Later that evening, Hypothetical Jim returns to the "About Us" page using his bookmark, and clicks on the link to the "Contact Us" page. After looking over the page, he leaves the site.
From the text description above, you can determine that: (1) the site has had 2 unique visitors, Hypothetical Jim and Hypothetical Stu; (2) the site has had three unique visitor sessions (two for Jim and one for Stu); and (3) the site has had 5 pageviews (4 by Jim and 1 by Stu). You may wonder wether to count Hypothetical Jim's second visit to the "About Us" page as a second pageview. Count it.
What you cannot determine from the description above is the number of website hits. A hit is measured every time a specific unique file (HTML files, image files, script files, frames, etc.) is downloaded. In other words, many people refer to the total number of HTTP Requests a user makes as the number of hits the site receives. Since a single web page can be made up of any number of unique files (hundreds even), measuring hits is often meaningless in measuring the success of a website.
In this hypothetical example, the homepage consists of 24 files, so web analysis software will count 24 hits every time a visitor downloads the home page. There are 21 total images, 1 script, and one CSS file (plus the index html file itself). The "About Us" page consists of 14 files, so web analysis software will count 14 hits. There are 11 images, 1 script, and one CSS file (plus the about html file itself). The same goes for the "Contact Us" page.
As you can see, website hits do not consistently correlate with unique visitors, sessions, or pageviews. The only reason to look at hits is to measure the number of HTTP requests that a browser has to make in order to view your page. Generally speaking, the larger the hit count, the slower the download. For that reason, it is best to reduce the number of hits/page until the download speed is optimized.
Because there are multiple metrics available to webmasters when reporting traffic, a great deal of confusion surrounds the whole affair. Many webmasters refer to website hits when they report their traffic. While many people have asked about increasing hits, website hits are not a very good measure of the success of a site.
First, let's take a hypothetical tour of the process of measuring website traffic. Imagine Hypothetical Jim visiting the home page of a new website he learned about on Google.com. Hypothetical Jim visits the home page, then visits the "About Us" page, which he bookmarks. Later, Hypothetical Stu visits the home page, then leaves the site. Later that evening, Hypothetical Jim returns to the "About Us" page using his bookmark, and clicks on the link to the "Contact Us" page. After looking over the page, he leaves the site.
From the text description above, you can determine that: (1) the site has had 2 unique visitors, Hypothetical Jim and Hypothetical Stu; (2) the site has had three unique visitor sessions (two for Jim and one for Stu); and (3) the site has had 5 pageviews (4 by Jim and 1 by Stu). You may wonder wether to count Hypothetical Jim's second visit to the "About Us" page as a second pageview. Count it.
What you cannot determine from the description above is the number of website hits. A hit is measured every time a specific unique file (HTML files, image files, script files, frames, etc.) is downloaded. In other words, many people refer to the total number of HTTP Requests a user makes as the number of hits the site receives. Since a single web page can be made up of any number of unique files (hundreds even), measuring hits is often meaningless in measuring the success of a website.
In this hypothetical example, the homepage consists of 24 files, so web analysis software will count 24 hits every time a visitor downloads the home page. There are 21 total images, 1 script, and one CSS file (plus the index html file itself). The "About Us" page consists of 14 files, so web analysis software will count 14 hits. There are 11 images, 1 script, and one CSS file (plus the about html file itself). The same goes for the "Contact Us" page.
As you can see, website hits do not consistently correlate with unique visitors, sessions, or pageviews. The only reason to look at hits is to measure the number of HTTP requests that a browser has to make in order to view your page. Generally speaking, the larger the hit count, the slower the download. For that reason, it is best to reduce the number of hits/page until the download speed is optimized.
0 comments:
Post a Comment