Absolutehealth.co.nz
Absolutehealth is ranked 1,256,929 in the United Kingdom. 'Absolute Health New Zealand, Meadowbank, Auckland Ph 09 5218920.'
1,256,929Rank in United Kingdom
18,499,729Worldwide Rank
Monthly pages viewed | < 300 | |
Monthly visits | < 300 | |
Value per visitor | £0.40 | |
Estimated worth | £357.82 | |
External links | 15 | |
Number of pages | 540 |
Last Updated: 05/04/2018 . Estimated data, read disclaimer.
Visitors
Traffic History 90 Day Average | ||
Worldwide Rank | 15,545,991 | 3,043,766 |
---|---|---|
Daily Visitors | 11 | 0% |
Daily Visitors Rank | 14,250,715 | -803,472 |
Daily Pageviews | 0 | -65.79% |
Daily Pageviews Rank | 17,351,544 | 6,916,977 |
Pageviews Per User | 1.00 | -65.52% |
Content
www.Absolutehealth.co.nz
- Popular pages
- absolutehealth.co.nz Sneaky's Recipes for Fussy Eaters - buy now from Absolute Health ..
- absolutehealth.co.nz Certificate in Diet & Nutrition Correspondence Course - enrol now ..
- absolutehealth.co.nz Buy: Nutrition for Sporty Kids from Absolute Health New Zealand ..
- absolutehealth.co.nz Certificate in Diet and Nutrition Correspondence Course - enrol ..
The site has about 12 users daily, viewing on average 1 page each.
ServerServer Location | |
Iconz Internet Service Provider Auckland New Zealand -36.87, 174.77 |
Its 2 nameservers are ns2.freeparking.co.nz, and ns.freeparking.co.nz. Absolutehealth.co.nz's server IP number is 210.48.108.247. Its web server is located at Iconz Internet Service Provider Auckland.
IP: 210.48.108.247
PING www. (210.48.108.247) 56(84) bytes of data. | |
64 bytes from zombie.freeparking.co.nz (210.48.108.247): icmp_seq=1 ttl=49 | 195 ms |
64 bytes from zombie.freeparking.co.nz (210.48.108.247): icmp_seq=2 ttl=49 | 194 ms |
64 bytes from zombie.freeparking.co.nz (210.48.108.247): icmp_seq=3 ttl=49 | 194 ms |
--- www. ping statistics --- | |
3 packets transmitted, 3 received, 0% packet loss, time 1998ms | |
rtt min/avg/max/mdev = 194.311/194.775/195.022/0.487 ms | |
rtt min/avg/max/mdev = 194.311/194.775/195.022/0.487 ms |
Pinging the server, resulted in a 195 ms response.