Website load speed

Every host offers bandwidth, disksize, uptime, etc. but none have a "quickness" measurement. I am probably an idiot, but I don't understand how to tell if a webhost is going to offer quickly loading pages. What do you look for in a webhost to make sure your site is going to be loaded quickly.

Thanks...

 

See how fast the hosts page loads and only prepay for a year if you've used the host before.

I found this host about a year ago and have stuck with them since.

totalchoicehosting.com

Very fast servers.

 

Your load speed is only as fast as your slowest leg in the route it take to get to you.

The host in question must host other web pages visit a few of them, time them and check their size.

You can also ask for their server specs.

 

Your own machine may not be as fast as you think it is when it comes to networking. For example, it is possible to be sitting on a 1 Mbps link and get less than 50 KBps transfer speeds (instead of 90+ KBps) if your TCP receive window is too small. On this page, click the TCP Analyzer link and scroll to bandwidth * delay product:

http://www.speedguide.net/networktools.php

... and how many virtual websites they have running on these specs. I have seen some hosts running as many as 300-400 sites on a single mid-range machine. Needless to say that your speed would depend on the time of day you test.

J.D.

 

Cool, thanks for the ideas.

 

That's it? The hosting companies I've worked for had a minimum of a 1000 per machine. Unix boxes usually had 2000+, windows boxes no less than 1000.

 

The keyword was mid-range machines

J.D.

 

Do a traceroute and see how many hops they are from a major backbone. For example, it takes me 6 hops just to get off bellsouth but if I were on a server sitting in Level3's datacenter in Atlanta, I'd be one hop off Mae east.

 

It's like your talking a different language. heh!

So is this good?

1 63-217-30-94.sdsl.cais.net (63.217.30.94) 0.308 ms 0.238 ms 0.234 ms
2 pos1-0.cr01.ash01.pccwbtn.net (63.216.0.57) 0.376 ms 0.370 ms 0.403 ms
3 pos5-3.cr01.ash01.pccwbtn.net (63.218.94.2) 0.335 ms 0.294 ms 0.276 ms
4 ge-6-14-0-108.car3.Washington1.Level3.net (209.244.219.133) 0.963 ms 1.010 ms 0.864 ms
5 ae-1-55.bbr1.Washington1.Level3.net (4.68.121.129) 0.964 ms 1.161 ms 1.086 ms
6 ae-0-0.bbr1.Chicago1.Level3.net (64.159.1.33) 20.375 ms as-2-0.bbr2.Chicago1.Level3.net (209.247.10.129) 20.396 ms ae-0-0.bbr1.Chicago1.Level3.net (64.159.1.33) 20.336 ms
7 so-5-0.ipcolo2.Chicago1.Level3.net (4.68.112.210) 20.458 ms 20.321 ms so-7-0.ipcolo2.Chicago1.Level3.net (4.68.96.30) 20.347 ms
8 4.79.66.18 (4.79.66.18) 21.937 ms 20.661 ms 20.564 ms
9 mail.nozonenet.com (205.218.64.6) 20.425 ms 20.598 ms 20.420 ms

 

Let's analyze it and see.

Got to a major backbone in 3 hops. Sweet.

Didn't have any time to do any sightseeing in D.C. but it looks like weather delayed our flight into O'Hare some..

Must have relatives in the windy city because we spent a lot of time there.

But it didn't really matter cuz it was just small trip from there to our destination.

All in all, I'd say that looks pretty good.

 

Only last few entries really matter - the rest shows how good his DSL connection is.

J.D.