FTB = F - w/ CDN and Caching plugin - Traceroute Help

Web Performance Discuss Test Results
1

I am not very technical when it comes to reading Traceroute nor do I know what is the “norm” so I am posting todays Traceroute results… does this indicate that its my server? I think it has been them all along… any help or analyzing help is appreciated.

traceroute to www.pictureperfectkeepsakes.com (66.96.134.49), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 1.673 ms 1.003 ms 0.601 ms
2 76.33.128.1 (76.33.128.1) 9.232 ms 7.076 ms 7.116 ms
3 network-024-160-225-036.wi.rr.com (24.160.225.36) 9.291 ms 6.918 ms 8.785 ms
4 tge1-2.brfdwijana-swt401.wi.rr.com (24.160.230.24) 8.237 ms 8.898 ms 8.833 ms
5 network-024-160-225-064.wi.rr.com (24.160.225.64) 8.880 ms 12.059 ms 9.409 ms
6 tge3-1-0.tr00.chctilwc.mwrtn.rr.com (24.160.229.77) 9.472 ms 14.193 ms tge0-1-0.tr00.chctilwc.mwrtn.rr.com (24.160.229.190) 8.515 ms
7 ae-6-0.cr0.chi30.tbone.rr.com (66.109.6.206) 10.348 ms 58.304 ms 10.208 ms
8 ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155) 10.109 ms 12.008 ms 11.584 ms
9 te0-2-0-7.ccr22.ord03.atlas.cogentco.com (154.54.11.145) 10.510 ms 10.984 ms 9.840 ms
10 te0-0-0-1.ccr21.ord01.atlas.cogentco.com (154.54.1.1) 11.784 ms te0-4-0-1.ccr22.ord01.atlas.cogentco.com (154.54.6.209) 9.347 ms te0-2-0-1.ccr22.ord01.atlas.cogentco.com (154.54.29.21) 10.824 ms
11 te0-2-0-2.ccr22.bos01.atlas.cogentco.com (154.54.43.194) 38.313 ms te0-4-0-6.ccr22.bos01.atlas.cogentco.com (154.54.45.218) 38.276 ms te0-1-0-6.ccr22.bos01.atlas.cogentco.com (154.54.43.206) 38.537 ms
12 endurance-international-group.demarc.cogentco.com (38.97.106.34) 37.875 ms 38.754 ms 39.344 ms
13 238.252.148.207.static.yourhostingaccount.com (207.148.252.238) 39.283 ms 46.348 ms 51.951 ms
14 49.134.96.66.static.eigbox.net (66.96.134.49) 39.003 ms 39.839 ms 38.353 ms

2

no help? was this a dumb question… I am sorry it looks like my server is taking too long but I am not sure what cogentco.com is… it looked like the problem starts there? I am sorry guys … I am not trying to ask lame questions.

3

You don’t usually need a traceroute to see if it is a networking problem. When you run a test the socket connect time is the same round trip time that you would get in the traceroute (for the most part). The round trip time is the basis used to calculate the TTFB so even if it was really long it wouldn’t be the reason you’d get an F.

More often than not an F is because of a combination of the hosting (slow server or database) and the application logic (lots of database calls or calls to external services).

4

My thoughts exactly! I usually use traceroute as a last resort.