Open a command prompt window and try using the pathping command to gather statistics of amount time it takes between each "hop" along the route. This will help determine if any one or more "hops" (i.e. each hop represents a router) along the way is causing some/all/most of the delay. Example command usage and output statistics to google. In this case shows consistent/good times between hops and 0% packet loss at each hop (also helpful to know to understand why speed may be slow)
Code:
pathping www.google.com
Tracing route to www.l.google.com [64.233.161.147]
over a maximum of 30 hops:
0 XP-PRO2 [192.168.1.2]
1 192.168.1.1
2 172.xx.xx.xx
3 mart-h1.chi-mart.il.cable.rcn.net [207.229.191.130]
4 tge3-1.border2.eqnx.il.rcn.net [207.172.19.159]
5 207.172.9.134
6 209.85.254.128
7 209.85.248.222
8 64.233.175.111
9 216.239.48.190
10 od-in-f147.google.com [64.233.161.147]
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 XP-PRO2 [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% 172.xx.xx.xx
0/ 100 = 0% |
3 16ms 0/ 100 = 0% 0/ 100 = 0% mart-h1.chi-mart.il.cable.rcn.net [207.229.191.130]
0/ 100 = 0% |
4 24ms 0/ 100 = 0% 0/ 100 = 0% tge3-1.border2.eqnx.il.rcn.net [207.172.19.159]
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% 207.172.9.134
0/ 100 = 0% |
6 17ms 0/ 100 = 0% 0/ 100 = 0% 209.85.254.128
0/ 100 = 0% |
7 62ms 0/ 100 = 0% 0/ 100 = 0% 209.85.248.222
0/ 100 = 0% |
8 70ms 0/ 100 = 0% 0/ 100 = 0% 64.233.175.111
0/ 100 = 0% |
9 71ms 0/ 100 = 0% 0/ 100 = 0% 216.239.48.190
0/ 100 = 0% |
10 70ms 0/ 100 = 0% 0/ 100 = 0% od-in-f147.google.com [64.233.161.147]
Trace complete.
C:\Program Files\Support Tools>