The January Numbers


It is getting a bit harder to figure out what the statistics are for Serendipity35 these days. Now that Tim moved the blog to new server digs at NJIT and also to a new beta server off-campus, we actually have 3 URLs, so traffic is spread around.

Our original URL was http://devel2.njit.edu/serendipity but that server also has some other sites (including the wiki Tim & I created)

The new NJIT location is http://dl.njit.ed/serendipity, which is our "official" URL, looks the same (a "mirror") and our beta off campus at http://www.serendipity35.net is really just a way for us to play with our future. It does look different and it's a bit behind since it pulls posts from the other site for now.

So what are the hits for all these locations for January 2009?

# 1,735,189   #2  2,257,567  #3  28,710

These numbers are inconceivable to me. That's a lot of views. Of course, "hits" is also somewhat deceptive. If we were a for-profit site, we'd be more interested in "unique visitors" and other things.

I'm actually very happy to see that 88.96% of the traffic to the site comes from educational .edu addresses.That means that we are hitting our "target audience."

But I am also very happy for those 686 visitors from Kazakhstan last month, and Hello to that one person from Greece!



 


Trackbacks

Trackback specific URI for this entry

Comments

Display comments as Linear | Threaded

No comments

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.
BBCode format allowed
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.
To leave a comment you must approve it via e-mail, which will be sent to your address after submission.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA