The ping times are a bit on the high side. Another trick is to do a traceroute to a specific site. Use Google for example and see the ping times to the various points along the route. Higher ping times will indicate where the bottlenecks are. Here is a traceroute from my own connection. Use this for comparison as it will give you a lot more information than a speed test can.
Tracing route to
www.l.google.com [209.85.135.99]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.xxx.xxx
2 45 ms 67 ms 46 ms xxx-xxx.static.cytanet.com.cy [81.x.xxx.xxx]
3 46 ms 45 ms 46 ms 195.14.128.242
4 45 ms 44 ms 45 ms lyk-3-g1.cytanet.com.cy [195.14.134.68]
5 45 ms 46 ms 45 ms latsiart-0-ge7-0.cyta-ip.net [195.14.157.9]
6 134 ms 134 ms 135 ms ldn-s2-rou-1021.UK.eurorings.net [134.222.109.18
2]
7 140 ms 134 ms 134 ms ldn-s2-rou-1003.UK.eurorings.net [134.222.231.22
6]
8 128 ms 132 ms 146 ms 195.66.224.125
9 129 ms 128 ms 128 ms 209.85.252.42
10 168 ms 147 ms 153 ms 209.85.248.80
11 147 ms 155 ms 148 ms 72.14.238.118
12 154 ms 156 ms 153 ms 72.14.233.106
13 158 ms 155 ms 155 ms 66.249.94.85
14 158 ms 155 ms 170 ms 72.14.239.58
15 196 ms 154 ms 155 ms mu-in-f99.google.com [209.85.135.99]
