You're always limited to doing detective work based on looking each line up in DNS/whois/Google. Use mtr to get more accurate, averaged round-trip times, and try tcptraceroute if some hops don't show up. You can make some inferences based on the round-trip time, but bear in mind that a router might take significantly longer to send the failure packet than to forward onto the next hop, so they're an upper bound only. Unfortunately, you'll also have to work against the fact that TalkTalk haven't set useful hostnames, and are using various routes inside their network. Here's[1] an example of how hostnames can help if they're set correctly.
From the hop time, my guess would be that the uselessly named box at hop 2 is the router at the other end of an ADSL connection. TalkTalk may well be using LLU in this case, but if they were using BT infrastructure this hop would be tunnelled all the way across BT's network, and there'd no way of determining how it travelled there.
Hop 5 is somewhere in an exchange in London, given the next hop is apparently allocated to Google.
Hop 4 is probably TalkTalk's internal interface inside the exchange in London.
Hop 3, which actually has a hostname, is therefore probably a large PoP for TalkTalk near London (Brentford?), and is an aggregation router of some sort. This is probably geographically between you and the exchange in London, but saying more would require more knowledge of how TalkTalk's network is set up.
Hop 6 will be Google's side of the exchange in London.
Hops 7 and 8 also belong to Google, and are not in Mountain View, despite what the allocation says. I can't ping them from my connection, so they're route-specific, and probably the two ends of a link between the exchange and the Heathrow datacentre.
Hop 9 is an IP in Heathrow belonging to Exponential-E. This will be Google's server.
As tgreer has said, all of this is educated guesswork, but you can learn more by trying to reach the IPs above from different parts of the world, to build up a picture of how the networks are arranged. Trying to traceroute backwards (from a looking-glass server to your IP) is usually interesting.
Mark