Why should I host my site in Australia ?
Since you're probably a small Australian business trying to keep your head above water amongst these multinationals you need to be that step ahead of the competition.
One way you can maximise your chances of doing this is by having your site load faster than the next guy who hosts his site in the United States of America.
When your website is on an Australian server, the data has much fewer steps to take from the server to your valuable customers, and in most cases it's less than 10 to 12 steps. On a USA based server, not only do you have to take many more steps, the simple fact that it is delayed by such a huge jump across the Pacific Ocean whenever website data is transferred.
A much more technical demonstration can be obtained via the several traceroute sites, such as the Telstra Network site.
www.oih.com.au
traceroute to oih.com.au (203.56.37.130), 30 hops max, 40 byte packets
1 TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net (203.50.80.1) 0 msec 4 msec 0 msec
2 Bundle-Pos3.chw-core2.Sydney.telstra.net (203.50.11.14) 16 msec 16 msec 12 msec
3 Pos0-0-0-0.woo-core1.Brisbane.telstra.net (203.50.6.202) 24 msec 24 msec 24 msec
4 TenGigabitEthernet7-2.cha30.Brisbane.telstra.net (203.50.50.40) 28 msec 28 msec 28 msec
5 as4826-qld.lnk.telstra.net (165.228.157.242) 28 msec 28 msec 28 msec
6 as24238.bne01.qld.VOCUS.net.au (114.31.195.38) 32 msec 32 msec 32 msec
7 www.oih.com.au (203.56.37.130) 28 msec 28 msec 28 msec
|
A site hosted by a "LOCAL" website host.
|
traceroute to logancountrychamber.com.au (204.10.105.210), 30 hops max, 40 byte packets
1 TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net (203.50.80.1) 0 msec 0 msec 0 msec
2 Bundle-Pos3.chw-core2.Sydney.telstra.net (203.50.11.14) 16 msec 16 msec 12 msec
3 Bundle-Ether1.oxf-gw2.Sydney.telstra.net (203.50.6.90) 16 msec 16 msec 16 msec
4 TenGigabitEthernetx-0.syd-core04.Sydney.reach.com (203.50.13.18) 16 msec 16 msec 16 msec
5 i-10-0-0.syd-core03.bi.reach.com (202.84.221.85) 16 msec 16 msec 16 msec
6 i-14-1-0.sydp-core01.bi.reach.com (202.84.249.13) 16 msec 16 msec 16 msec
7 i-14-1-1.wil-core03.bx.reach.com (202.84.140.162) 168 msec 168 msec 168 msec
8 i-1-2.eqla01.bi.reach.com (202.84.251.174) 176 msec 176 msec 176 msec
9 cogent-peer.eqla01.pr.reach.com (134.159.63.198) 168 msec 168 msec 168 msec
10 te4-2.mpd02.lax01.atlas.cogentco.com (154.54.6.189) 168 msec
11 te3-8.mpd01.iah01.atlas.cogentco.com (154.54.2.197) 204 msec
12 te4-1.ccr01.iah01.atlas.cogentco.com (154.54.1.86) 204 msec
13 te3-2.ccr02.mia01.atlas.cogentco.com (154.54.25.73) 232 msec
14 te8-8.ccr01.mia03.atlas.cogentco.com (154.54.3.126) 232 msec
15 Webhostingdotnet.demarc.cogentco.com (38.112.7.230) 236 msec 236 msec 236 msec
16 64.71.225.26 232 msec 232 msec 228 msec
17 204.10.105.210 232 msec 228 msec 228 msec
|
The key items to note is to compare the ping times (the three groups of numbers at the end of each line, with the lower the number, the faster your site will load).
The second example slows right down at step/hop number 7. Ultimately the last step to the actual webhost is around TEN (10) times slower than in the first example.
