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

C:\Users\Owner>tracert www.s2ki.com

Tracing route to www.s2ki.com [98.158.195.246]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home [172.16.1.254]
2 * * * Request timed out.
3 11 ms 10 ms 11 ms 207-47-195-230.ngai.static.sasknet.sk.ca [207.47
.195.230]
4 42 ms 44 ms 42 ms 142.165.0.130
5 42 ms 42 ms 42 ms te-9-4.car1.Toronto2.Level3.net [4.59.180.65]
6 41 ms 42 ms 42 ms 4.69.153.77
7 57 ms 56 ms 58 ms ae-9-9.ebr1.Chicago1.Level3.net [4.69.151.110]
8 55 ms 56 ms 60 ms ae-1-100.ebr2.Chicago1.Level3.net [4.69.151.178]

9 56 ms 66 ms 56 ms ae-5-5.ebr2.Chicago2.Level3.net [4.69.140.194]
10 77 ms 78 ms 80 ms ae-14-14.ebr1.Dallas1.Level3.net [4.69.151.118]

11 77 ms 79 ms 82 ms ae-61-61.csw1.Dallas1.Level3.net [4.69.151.125]

12 77 ms 78 ms 80 ms ae-63-63.ebr3.Dallas1.Level3.net [4.69.151.134]

13 87 ms 91 ms 90 ms ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]

14 90 ms 87 ms 88 ms ae-72-72.csw2.LosAngeles1.Level3.net [4.69.137.2
2]
15 87 ms 89 ms 90 ms ae-21-70.car1.LosAngeles1.Level3.net [4.69.144.6
7]
16 90 ms 89 ms 92 ms INTERNET-BR.car1.LosAngeles1.Level3.net [4.59.56
.162]
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.

C:\Users\Owner>

Looks greek to me. No offense to anyone. I have not experienced the issues folks are reporting. Looks like I have to go across the country and back, but I have not issues, with Firefox, ipad, iphone, idogit or IE 7

 

I have been, I gave up when it got to 41 on the tracert

 

Another from home, same ISP as at work but even fatter pipe. Nothing untoward here until you get to the router blocking ICMP but performance isn't affected.

~ jp$ traceroute s2ki.com
traceroute to s2ki.com (98.158.195.246), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.334 ms 0.128 ms 0.131 ms
2 10.223.88.1 (10.223.88.1) 12.397 ms 9.760 ms 8.021 ms
3 24-234-16-237.ptp.lvcm.net (24.234.16.237) 13.081 ms 12.603 ms 8.407 ms
4 24-234-6-193.ptp.lvcm.net (24.234.6.193) 7.883 ms
24-234-6-185.ptp.lvcm.net (24.234.6.185) 7.978 ms
24-234-6-193.ptp.lvcm.net (24.234.6.193) 15.798 ms
5 langbprj01-ae1.rd.la.cox.net (68.1.1.13) 19.408 ms 14.480 ms 13.952 ms
6 ge-11-2-0.mpr1.lax12.us.above.net (64.125.13.13) 13.622 ms
ge-11-1-9.mpr1.lax12.us.above.net (64.125.13.9) 23.060 ms 14.382 ms
7 xe-0-2-0.mpr1.lax7.us.above.net (64.125.30.9) 14.868 ms 15.600 ms 13.994 ms
8 64.125.69.86.available.above.net (64.125.69.86) 16.140 ms 18.512 ms 20.559 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *

 

This one is more interesting. It's from a server hosted on big bandwidth at Equinix in Chicago. Notice the 2nd above.net hop introduces a big delay however even 60ms shouldn't be enough to really hamper page loads with all the scripting going on.


jp@ded294:~$ traceroute s2ki.com
traceroute to s2ki.com (98.158.195.246), 30 hops max, 60 byte packets
1 208.99.65.25 (208.99.65.25) 2.362 ms 2.531 ms 2.708 ms
2 gige9-30.1000M.ar1.ord6.reflected.net (64.210.153.153) 0.536 ms 0.571 ms 0.607 ms
3 216.18.172.166 (216.18.172.166) 7.771 ms 216.18.172.254 (216.18.172.254) 7.609 ms 7.684 ms
4 xe-2-0-2-174.ar2.ord1.us.nlayer.net (69.31.110.137) 2.476 ms 69.31.105.5 (69.31.105.5) 3.156 ms xe-1-0-7-171.ar1.ord1.us.nlayer.net (69.31.110.101) 8.375 ms
5 ae1-40g.cr2.ord1.us.nlayer.net (69.31.111.137) 1.371 ms ae2-40g.cr2.ord1.us.nlayer.net (69.31.111.149) 1.417 ms 1.395 ms
6 mpr1.ord7.us (206.223.119.86) 1.759 ms 1.627 ms 1.590 ms
7 xe-1-3-0.cr1.ord2.us.above.net (64.125.30.142) 9.345 ms 8.458 ms 8.349 ms
8 xe-2-2-0.cr1.sjc2.us.above.net (64.125.26.137) 55.501 ms 55.680 ms 56.022 ms
9 xe-1-2-0.cr1.lax112.us.above.net (64.125.29.2) 57.889 ms 57.388 ms 57.396 ms
10 xe-0-0-0.cr2.lax112.us.above.net (64.125.30.234) 80.495 ms 80.485 ms 80.475 ms
11 xe-0-1-0.mpr1.lax7.us.above.net (64.125.30.5) 58.019 ms 57.983 ms 57.987 ms
12 64.125.69.86.available.above.net (64.125.69.86) 57.957 ms 58.233 ms 57.943 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
jp@ded294:~$

 

Robb, the issue is the number of external ad scripts and trackers being requested by the pages... See all these below!

 

With respect Ian, the issue of pages not connecting, then loading on a second click at normal speed, is not a problem with the scripts. It's either an issue with one of our 2 providers, or it's an issue within our own network. We're trying to pare down the possibilities so that we can know which way to look. Tracerts from people having the problem, are helpful in letting us determine whether it's a provider issue or an internal one.

Vadster, are your tracerts looking like ludedude's? or where do they stall? Could you share please?

 

Tracing route to s2ki.com [98.158.195.246]
over a maximum of 30 hops:

1 5 ms 8 ms 19 ms ip68-96-248-1.lv.lv.cox.net [68.96.248.1]
2 5 ms 8 ms 6 ms 24-234-16-69.ptp.lvcm.net [24.234.16.69]
3 31 ms 114 ms 5 ms 24-234-6-193.ptp.lvcm.net [24.234.6.193]
4 15 ms 11 ms 11 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
5 13 ms 10 ms 11 ms ge-11-1-9.mpr1.lax12.us.above.net [64.125.13.9]

6 13 ms 15 ms 15 ms xe-0-2-0.mpr1.lax7.us.above.net [64.125.30.9]
7 12 ms 15 ms 15 ms 64.125.69.86.available.above.net [64.125.69.86]

8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
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.

 

Traceroute on www.s2ki.com

1 vlan832.sw1.f1c11.iph.lon.as5587.net (212.69.192.3) 0.514 ms 0.617 ms 0.486 ms
2 821.gi0-1.rtr2.iph.lon.as5587.net (195.13.89.17) 0.318 ms 0.739 ms 0.596 ms
3 900.gi0-0-0.rtr2.tc9.lon.as5587.net (213.253.141.222) 2.740 ms 1.680 ms 1.738 ms
4 ge-2-1-3-xur1.lns.uk.cw.net (195.11.50.22) 2.220 ms 2.355 ms 9.477 ms
5 xe-0-3-0-xur1.lns.cw.net (194.70.97.66) 1.881 ms 5.998 ms 1.166 ms
6 xe-1-3-1-xcr1.lnd.cw.net (195.2.28.133) 2.439 ms xe-1-3-0-xcr1.lnd.cw.net (195.2.28.37) 2.237 ms xe-1-3-1-xcr1.lnd.cw.net (195.2.28.133) 2.374 ms
7 ge-3-3-0.mpr1.lhr3.uk.above.net (195.66.226.76) 2.406 ms 2.502 ms 2.144 ms
8 ge-5-1-0.mpr1.lhr3.uk.above.net (64.125.28.94) 3.015 ms 3.288 ms 2.978 ms
9 xe-4-3-0.cr2.dca2.us.above.net (64.125.24.41) 82.138 ms 83.962 ms 81.677 ms
10 xe-0-2-0.cr2.iah1.us.above.net (64.125.28.50) 107.973 ms 107.776 ms 107.447 ms
11 xe-2-0-0.cr2.lax112.us.above.net (64.125.25.18) 157.213 ms 157.140 ms 157.418 ms
12 xe-0-1-0.mpr1.lax7.us.above.net (64.125.30.5) 140.788 ms 168.767 ms 139.899 ms
13 64.125.69.86.available.above.net (64.125.69.86) 141.259 ms 142.707 ms 141.756 ms
14 * * *

 

It's the config on your load balancer/http server. If it was network related it would still be slow after the "2nd click" but once you wake it up with the second press it's speedy. Something in your config is screwing up the initial redirect.

 

King, I tend to agree with you, trying to make the network team agree it's their problem, is another issue. These tracers are helpful, thanks everyone!