7,659,622Rank in United Kingdom
1,304,574Worldwide Rank
Monthly pages viewed | 17,464 | |
Monthly visits | 15,876 | |
Value per visitor | -- | |
Estimated worth | £5,646.55 | |
External links | 59 | |
Number of pages | 90 |
Last Updated: 06/04/2018 . Estimated data, read disclaimer.
Visitors
Country | Country Rank | Users % | Pageviews % |
United States | 210,951 | 100.00% | 100.00% |
---|
Most visitors are from United States.
Traffic History 90 Day Average | ||
Worldwide Rank | 1,096,281 | -393,348 |
---|---|---|
Daily Visitors | 342 | +30% |
Daily Visitors Rank | 833,818 | -327,239 |
Daily Pageviews | 300 | +30% |
Daily Pageviews Rank | 1,928,458 | -565,432 |
Pageviews Per User | 1.10 | -1.82% |
Content
www.C1ms.com
- Popular pages
- cowboys.c1ms.com Dallas Cowboys
- trailblazers.c1ms.com Portland Trail Blazers - 2011 E-Brochure
- rosebowl.c1ms.com Rosebowl Stadium
- oilers.c1ms.com Edmonton Oilers - 2011 Draft
- packers.c1ms.com Green Bay Packers
The site has about 374 users daily, viewing on average 1.10 pages each.
Links- Links out
- mediatemple.net Web Hosting by Media Temple | Quality Hosting Plans, Built to Scale
- kb.mediatemple.net (mt) Media Temple KnowledgeBase Home
- mediatemple.net Contact Media Temple Web Hosting Solutions
- kb.mediatemple.net (dv) Backing up and restoring your files
Server Location | |
Media Temple Inc. California United States 37.300275, -93.339844 |
Its IP Number is 205.186.138.224. Its web server is located at Media Temple Inc. California. It has 2 DNS records, ns1.mediatemple.net, and ns2.mediatemple.net.
IP: 205.186.138.224
PING www. (205.186.138.224) 56(84) bytes of data. | |
64 bytes from (205.186.138.224): icmp_req=1 ttl=50 | 36.5 ms |
64 bytes from (205.186.138.224): icmp_req=2 ttl=50 | 36.3 ms |
64 bytes from (205.186.138.224): icmp_req=3 ttl=50 | 36.3 ms |
--- www. ping statistics --- | |
3 packets transmitted, 3 received, 0% packet loss, time 2002ms | |
rtt min/avg/max/mdev = 36.303/36.400/36.546/0.105 ms | |
rtt min/avg/max/mdev = 36.303/36.400/36.546/0.105 ms |
Pinging the server, resulted in a 36.5 ms response.