I don't think so somehow.
When you go to google.com, does it redirect you to the UK ? If it does not, then your ISP may have an incorrect listing on their geolocation database which means your browser is talking to servers further away.
Secondly, as others have said, if you don't feel the need for autocomplete, disable it. It will speed things up when your browser doesn't have to waste time on all that nasty AJAX Javascript bloat-ware.
What sort of firewall setup do you have ? Are you using a hardware firewall of some description ? Is the software up to date ?
Are your web browsers up to date ? Is your OS up to date on patches ?
Have you double checked all your DNS settings ? You may have a broken DNS server somewhere on your list, which would mean under round-robin you'll see delays when you hit that one as resolver.
Finally, please stick up a trace route and ping to google.com here, it may be an ISP network issue (although fairly unlikely). If you're on the Uk/EU servers, the route taken will look something like the below (although your return times will probably be higher and you'll have more hops than me).
Code:
>tracert google.com (or "traceroute google.com" on mac)
1 <1 ms <1 ms <1 ms XXXXXXXXX
2 <1 ms <1 ms <1 ms XXXXXXXXX
3 <1 ms 1 ms 1 ms XXXXXXXXX
4 1 ms 1 ms 1 ms google1.lonap.net [193.203.5.136]
5 2 ms 1 ms 1 ms 209.85.255.76
6 3 ms 4 ms 3 ms 209.85.253.92
7 7 ms 7 ms 7 ms 72.14.232.134
8 7 ms 7 ms 7 ms 72.14.236.191
9 7 ms 7 ms 7 ms 209.85.243.81
10 7 ms 7 ms 7 ms ww-in-f147.1e100.net [209.85.229.147]
Trace complete.
>ping google.com
Pinging google.com [209.85.229.147] with 32 bytes of data:
Reply from 209.85.229.147: bytes=32 time=7ms TTL=55
Ping statistics for 209.85.229.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 8ms, Average = 7ms