Hi all, I'm soon to launch www.workoutbox.com and have been running a few tests on its performance. I'm based in the UK but as the site is hosted on the west side of the US when I ping it I get a ping of 170ms!! To me this seems unnormally high, even though its 1000's of miles away, what do you think? Any chance a few people stateside could ping www.workoutbox.com and let me know the results? How are everyone else's sites performing? People getting low ping's under 10ms? Since were all on shared hosting, are our sites just going to be slow and there's nothing we can do about it? Look forward to hearing from you guys. Simon
Ping doesn't tell you how the server is responding, that's a measure of the total trip. You need to run a traceroute, that will show you where the latency is. https://support.discountasp.net/KB/a320/general-network-troubleshooting-tools-ping-traceroute.aspx We also have servers in London, so you may want to consider migrating if most of your audience is outside the U.S.
I deploy a site www.puntaforsale.com last month and the speed is very slow, to download a 500kb page sometime depend on the traffic delay more than 10 second. Why is that? How can I fix that?
This is the traceroute from puntaforsale.com. I hope this help to fix this performance issue. C:\Users\alex.INTRARAY>tracert puntaforsale.com Tracing route to puntaforsale.com [64.79.160.13] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.1 2 21 ms 19 ms 19 ms uni1bras1.antel.net.uy [200.40.22.2] 3 19 ms 19 ms 19 ms ibb2uni1-2-3-90.antel.net.uy [200.40.22.33] 4 * * * Request timed out. 5 703 ms 723 ms 724 ms sl-st22-mia-8-2-1.sprintlink.net [144.228.25.153 ] 6 703 ms 670 ms 658 ms sl-crs1-mia-0-8-0-1.sprintlink.net [144.232.28.7 5] 7 741 ms 766 ms 785 ms sl-crs1-fw-0-2-0-2.sprintlink.net [144.232.19.84 ] 8 767 ms 737 ms 742 ms sl-crs1-ana-0-6-2-0.sprintlink.net [144.232.19.1 98] 9 792 ms 794 ms 786 ms sl-st21-la-0-0-0.sprintlink.net [144.232.20.206] 10 753 ms 759 ms 786 ms sl-internap-96007-0.sprintlink.net [144.232.154. 206] 11 793 ms 782 ms 743 ms border1.po1-2g-bbnet1.ext1.lax.pnap.net [216.52. 255.22] 12 747 ms 778 ms 799 ms hostcollective-4.border1.lax.ext1.pnap.net [216. 52.253.94] 13 789 ms 754 ms 754 ms 96-31-33-196.discountasp.net [96.31.33.196] 14 795 ms 796 ms 781 ms 96-31-33-227.discountasp.net [96.31.33.227] 15 714 ms 738 ms 777 ms web114.discountasp.net [64.79.160.13] Trace complete.
This is the ping.txt of puntaforsale.com Pinging www.puntaforsale.com [64.79.160.13] with 32 bytes of data: Reply from 64.79.160.13: bytes=32 time=235ms TTL=109 Reply from 64.79.160.13: bytes=32 time=236ms TTL=109 Reply from 64.79.160.13: bytes=32 time=235ms TTL=109 Reply from 64.79.160.13: bytes=32 time=236ms TTL=109 [snip] Reply from 64.79.160.13: bytes=32 time=237ms TTL=109 Reply from 64.79.160.13: bytes=32 time=236ms TTL=109 Reply from 64.79.160.13: bytes=32 time=234ms TTL=109 Reply from 64.79.160.13: bytes=32 time=240ms TTL=109 Reply from 64.79.160.13: bytes=32 time=235ms TTL=109 Ping statistics for 64.79.160.13: Packets: Sent = 500, Received = 500, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 233ms, Maximum = 1344ms, Average = 259ms
That's a network problem, judging by your traceroute: 1 1 ms 1 ms 1 ms 192.168.1.1 2 21 ms 19 ms 19 ms uni1bras1.antel.net.uy [200.40.22.2] 3 19 ms 19 ms 19 ms ibb2uni1-2-3-90.antel.net.uy [200.40.22.33] 4 * * * Request timed out. 5 703 ms 723 ms 724 ms sl-st22-mia-8-2-1.sprintlink.net [144.228.25.153] You can see that it times out on the 4th hop, then it's just degraded tovery badperformance that carries through the rest of the hops. You'll have to talk to your ISP about that. Send them a copy of that traceroute.
