Slow web pages

[c1hundred]

Hi

Since the outage on Sunday evening I am still experiencing some pages that are very slow to load or fail to load.

An example would be linkedin (www.linkedin.com) this takes a very long time to come up and then only with the bare text and links (all the graphics are missing)

Tried this on several PCs and both ie8 and firefox
Also tried rebooting the router.

01296 Aylesbury exchange.

Any ideas?

[Steve]

It's ok for me,suggest flushing the browser cache and also the Windows dns cache i.e ifconfig flush all from command prompt.

[Glenn]

Fine here too, I agree with what Steve has suggested.

[esh]

I think steve means "ipconfig /flushdns" (ifconfig is linux!)

If these don't help, what does pinging these 'slow' sites look like? Any packet loss?

[Steve]

   Sorry I've been messing with a linux box recently. Thanks esh.

[c1hundred]

Tried that .... same result.

[Steve]

Have you tried a BT Speedtest? if it's working.

[c1hundred]

Yep results are about usual - 

Download speedachieved during the test was - 2946 Kbps
For your connection, the acceptable range of speedsis 1200-4000 Kbps.
Additional Information:
Your DSL Connection Rate :0 Kbps(DOWN-STREAM), 0 Kbps(UP-STREAM)
IP Profile for your line is - 3000 Kbps
The throughput of Best Efforts (BE) classes achieved during the test is - 12.39:22.7:64.91 (SBE:NBE:PBE)
These figures represent the ratio while sententiously passing Sub BE, Normal BE and Priority BE marked traffic.

The results of this test will vary depending on the way your ISP has decided to use these traffic classes.

[Steve]

What's the trace routes looking like i.e from command prompt  tracert www.linkedin.com

[c1hundred]

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

C:\Users\Allan>tracert www.linkedin.com

Tracing route to www.linkedin.com [64.74.98.80]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    74 ms    27 ms    27 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    34 ms    33 ms    27 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4    27 ms    27 ms    27 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
  5    27 ms    27 ms    30 ms  te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50.117]
  6   106 ms   105 ms   104 ms  te0-0-0-5.ccr22.ymq02.atlas.cogentco.com [154.54.42.46]
  7   136 ms   128 ms   127 ms  te0-2-0-6.ccr21.ord01.atlas.cogentco.com [154.54.30.238]
  8   134 ms   155 ms   127 ms  te0-1-0-3.ccr22.ord03.atlas.cogentco.com [154.54.1.2]
  9   129 ms   127 ms   130 ms  38.104.102.102
10   152 ms   128 ms   128 ms  border2.te7-1-bbnet1.chg004.pnap.net [64.94.32.19]
11   140 ms   136 ms   128 ms  linkedin-10.border2.chg004.pnap.net [64.94.34.154]
12   140 ms   128 ms   128 ms  www.linkedin.com [64.74.98.80]

Trace complete.

[Rik]

Tracert doesn't look bad for an American server.