Gentlefolk,
Another approach to investigate bottlenecks which sometimes works is to do a Traceroute to say BBC.
This isn't always as useful as it might sound as some ISPs have less decipherable node names, and some nodes are hidden anyway.
However if you record the logs you can compare timings at least on the line entries you can see, even if you're not able to decipher where they are. I would also suspect the over-loaded pipes are buried deep inside the network bowels of the network.
As an example I've copied below the output I get on my NTL / Virgin Media cable connection, but have edited out my IP address in line 2.
Traceroute has started ...
traceroute to bbc.co.uk (212.58.224.138), 64 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 1.526 ms 0.907 ms 0.765 ms
2 aa.bbb.ccc.d (aa.bbb.ccc.d) 9.771 ms 8.215 ms 8.048 ms
3 glfd-t2cam1-b-ge912.network.virginmedia.net (80.4.30.213) 19.931 ms 13.881 ms 27.615 ms
4 glfd-t3core-1b-ge-010-0.network.virginmedia.net (195.182.175.249) 34.721 ms 11.867 ms 28.195 ms
5 gfd-bb-b-ge-220-0.network.virginmedia.net (213.105.175.89) 10.868 ms 8.983 ms 11.140 ms
6 redb-ic-1-as0-0.network.virginmedia.net (62.253.185.78) 10.713 ms 10.604 ms 10.973 ms
7 212.58.239.249 (212.58.239.249) 8.893 ms 25.241 ms 11.952 ms
8 212.58.238.149 (212.58.238.149) 19.827 ms 10.295 ms 11.833 ms
9 * * *
10 * *
Kind regards,
Walter