|
|
Posted by Ed Mullen on 11/28/07 20:31
Mika wrote:
> "Ed Mullen" <ed@edmullen.net> wrote in message
> news:J4CdnTgQ47DFR9HanZ2dnUVZ_vzinZ2d@comcast.com...
>
>>> Sadly there is little we can do about delays on your hops towards our
>>> site, aside from relocating the server to the USA, and then we lose our
>>> majority audience which are UK based.
>> Tracing route to superhigstreet.com [208.69.32.130]
>> over a maximum of 30 hops:
>
> Thanks Ed, this is helpful.
>
>> 1 * * * Request timed out.
>> 2 * * * Request timed out.
>
> These are your most local hops, and they are timing out. I would take this
> up urgently with your ISP, explaining they were hops towards a UK server.
> That would explain your extended delay.
Have to agree with BTS that this is insignificant as it happens on
virtually every tracert I do. Also, as I mentioned earlier, I can get
to most every UK site I tested in just a couple of seconds. And the
largest times are when the tracert leaves the US and starts hitting
ntt.net in the UK:
19 46 ms 39 ms 39 ms xe-7-2.r04.asbnva01.us.bb.gin.ntt.net
[129.250.9.113]
20 40 ms 47 ms 40 ms ae-1.r21.asbnva01.us.bb.gin.ntt.net
[129.250.2.180]
21 228 ms 219 ms 240 ms po-3.r05.asbnva01.us.bb.gin.ntt.net
[129.250.2.87]
22 90 ms 255 ms 235 ms fa-0.opendns.asbnva01.us.bb.gin.ntt.net
[129.250.12.114]
23 35 ms 38 ms 35 ms nxdomain.guide.opendns.com [208.69.32.130]
Still, 219-255 ms is fine. So, the only conclusion I can make is that
the load time is dependent upon the amount of "stuff" coming down the
pipe to create your page. I suppose it's also possible that the way
your page is built could be contributing but I honestly can't say. Hey,
I'm not complaining, just discussing.
--
Ed Mullen
http://edmullen.net
http://mozilla.edmullen.net
http://abington.edmullen.net
And whose cruel idea was it to put an S in the word Lisp?
Navigation:
[Reply to this message]
|