Speedtest.net vs Cox's Speed check - Why is there such a huge difference?

It is a wired connection.   The other sites are all about the same with a 50% loss of the paid speed, while Cox speed check is usually about 95% of the paid speed.  Very interesting of the Cox displayed speed.

I have a direct wired connection to Netgear CG4500BD.  

These speed test were done consecutively (Mbps):

Cox SpeedCheck (PHX Market) = 117.03 down, 11.98 up.  Latency 7 ms

Speedtest.net = 33.25 down, 11.94 up. Latency 14ms

Traceroute:

tracert cox.net

Tracing route to cox.net [68.99.123.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 7 ms 7 ms 10.52.128.1
3 6 ms 7 ms 8 ms 172.21.0.212
4 10 ms 10 ms 11 ms 70.169.77.248
5 8 ms 8 ms 9 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 52 ms 52 ms 55 ms dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
7 51 ms 51 ms 51 ms 68.1.15.234
8 * 51 ms 51 ms 68.99.123.4
9 53 ms 51 ms 52 ms ww2.cox.com [68.99.123.161]

Trace complete.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Mccammr>tracert usabmx.com

Tracing route to usabmx.com [67.199.115.204]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 6 ms 9 ms 10.52.128.1
3 8 ms 11 ms 7 ms 172.21.2.212
4 13 ms 11 ms 11 ms 70.169.77.248
5 7 ms 8 ms 9 ms 72.215.229.61
6 20 ms 19 ms 29 ms ae56.bar1.Phoenix1.Level3.net [4.31.188.61]
7 17 ms 19 ms 19 ms ae-1-60.edge1.LosAngeles9.Level3.net [4.69.144.1
0]
8 * 19 ms * ae-1-60.edge1.LosAngeles9.Level3.net [4.69.144.1
0]
9 33 ms 20 ms 22 ms los-brdr-01.inet.qwest.net [63.146.27.33]
10 * * * Request timed out.
11 40 ms 31 ms 41 ms 63.148.218.166
12 37 ms 33 ms 32 ms 216.197.122.66
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Mccammr>tracert dish.com

Tracing route to dish.com [66.170.250.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 7 ms 5 ms 10.52.128.1
3 7 ms 8 ms 7 ms 172.21.0.212
4 10 ms 7 ms 11 ms 70.169.77.248
5 8 ms 14 ms 7 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 19 ms 22 ms 25 ms ae56.bar1.Phoenix1.Level3.net [4.31.188.61]
7 * 18 ms 19 ms ae-3-80.edge1.LosAngeles9.Level3.net [4.69.144.1
38]
8 * 19 ms 20 ms ae-3-80.edge1.LosAngeles9.Level3.net [4.69.144.1
38]
9 19 ms 19 ms 19 ms 4.68.63.246
10 * * * Request timed out.
11 55 ms 59 ms 59 ms TenGigE0.7-0-2.GW5.DEN4.ALTER.NET [152.63.88.254
]
12 57 ms 55 ms 56 ms dishnetwork-gw.customer.alter.net [152.179.191.4
2]
13 63 ms 54 ms 62 ms midnightlounge.com [66.170.250.4]

Trace complete.

C:\Users\Mccammr>

Hi @MichaelJ - I posted the trace route, now what?  Is there any solution?