Meadowbank is a Wi-Fi microcosm. New-build flats around the old stadium site, older maisonettes down toward Willowbrae and Restalrig, four-in-a-block conversions off London Road, and, at almost every doorstep, a fibre-to-the-premises box the ISP swapped in over the last two years. Nearly every household we see here has more speed than they can practically use. And yet more calls come from Meadowbank about “browsing feels really slow” than about actual disconnections. Almost every one of them turns out not to be a Wi-Fi problem at all — it’s a DNS problem, and the speed test on Speedtest.net or fast.com will not show it, because those tools deliberately don’t use DNS the way a browser does.
If you’d rather we came out and looked at it, that’s exactly what a Meadowbank slow-computer visit covers — and DNS is the first thing we test, before anything else. Otherwise, this is the order we work through “the internet feels slow but the number is fine” on the bench, why the speed test lies to you about it, and the five-minute change that resolves most of these calls without touching the router.
1. Why the Speed Test Says You’re Fine
A speed test on Speedtest.net or fast.com is doing exactly one thing: filling the pipe. It picks a server near you, opens several parallel TCP connections, downloads and uploads a big chunk of nothing, and reports the peak throughput. That measures your bandwidth — how fat the pipe is when it’s wide open. It does not measure any of the things a browser cares about when it’s opening a real web page.
A real page load starts with a DNS lookup: the browser has to translate a domain name (bbc.co.uk) into an IP address (something like 151.101.0.81) before it can open a single connection. If that lookup takes 900 milliseconds instead of 20, the whole page is late before any of the fast pipe is even used — and when the page then loads dozens of secondary domains (fonts, analytics, images, scripts), every one of those needs its own lookup too. The speed test doesn’t suffer from that because it embeds the server’s IP addresses directly and skips DNS entirely. Which is exactly why the number can look perfect while the browsing feels dreadful.
2. What Actually Happens Between “Click” and “Page”
When you click a link to, say, gov.uk, in order: Windows asks its resolver for gov.uk, the resolver asks the DNS server your machine is configured to use, that DNS server either has the answer cached or has to go and ask the authoritative name servers for the domain, and the answer comes back to Windows. Only then does the browser open the TCP handshake, then the TLS handshake, then finally requests the HTML. Modern browsers do a lot in parallel and preconnect where they can, but the very first hit on any new domain waits on DNS.
On a fibre line running well, the DNS lookup should be around 20–40 milliseconds. Under 100 is fine. Once you’re past 200 milliseconds the human brain notices the pages feel “heavy”. Past 500, everything feels like the internet is broken. And past a second, which is what we see on a specific class of failing ISP resolver, pages either hang on “Resolving host” or start with a two-second white flash before anything renders. All of it is invisible to a speed test, and all of it is completely fixable in about five minutes.
3. Where DNS Goes Wrong on a Home Connection
The default DNS server your machine uses at home is almost always the router, and the router itself just forwards to whichever DNS resolver your ISP hands out on the DHCP lease. That’s the weak link. ISP resolvers are shared across huge numbers of subscribers, they are almost never the fastest option even on a good day, and on a bad day they do one of three things: they slow down under load in the evenings when everyone gets home, they return stale or partial results, or — the classic — they drop AAAA (IPv6) queries and force your machine to wait for the timeout before it asks again for the A (IPv4) record instead.
That last one is the sneakiest failure mode we see in Meadowbank. Windows 11, Chrome and Edge all prefer IPv6 by default. If the ISP resolver takes 1.9 seconds to respond “no AAAA record” instead of an instant answer, that’s two seconds tacked onto the very first hit of every new domain. The pipe stays 640Mbps. The browsing sits at rubbish. And nothing in Windows’ own diagnostics tells you the resolver is the bit that’s slow.
4. The 30-Second Test: Is DNS Actually the Problem?
You do not need to guess. Open PowerShell (right-click the Start button, pick Terminal or Windows PowerShell). Type Resolve-DnsName bbc.co.uk and press Enter. Type it again. Type it a third time with a domain you’ve never used, like Resolve-DnsName plumbworld.co.uk. Watch how long each takes. If any single lookup takes more than half a second, or if the first hit on a fresh domain regularly takes multiple seconds, DNS is the problem — and every browser on the machine is sitting through the same delay on every new page.
For a second data point, do the same command with the resolver forced: Resolve-DnsName plumbworld.co.uk -Server 1.1.1.1. That bypasses your ISP entirely and asks Cloudflare directly. If Cloudflare’s answer comes back in 30 milliseconds while your default takes two seconds, that’s the whole diagnosis in one line of output. In Chrome and Edge you can also open DevTools (F12) → Network tab → hard-reload a page → hover over the top request and read the “DNS Lookup” row of its timing waterfall. Anything more than about 200ms on that row is a smoking gun.
5. The Fix: Switching DNS on Windows Properly
The reliable, five-minute fix is to point your Windows machine at a fast public resolver rather than the router’s default. Cloudflare (1.1.1.1) and Quad9 (9.9.9.9) are both good; Cloudflare is usually the fastest for consumer traffic in Scotland, Quad9 additionally filters known malicious domains as it resolves, which is a small but genuine security benefit and the option we set up for a lot of small businesses.
Open Settings → Network & Internet → Wi-Fi → click your current network. Scroll to DNS server assignment and click Edit. Change Automatic to Manual, turn on IPv4, and put 1.1.1.1 as Preferred and 1.0.0.1 as Alternate (or 9.9.9.9 and 149.112.112.112 for Quad9). Turn on IPv6 as well and put 2606:4700:4700::1111 and 2606:4700:4700::1001 (Cloudflare’s IPv6 pair) — because if IPv6 stays on ISP defaults, that IPv6 delay we mentioned is still there and the fix only half-works. Save it, close the panel, and flush the Windows resolver cache with ipconfig /flushdns in an admin Terminal, because Windows caches even a bad answer for at least the domain’s TTL and negative answers for five minutes by default. Then reload the pages that felt slow.
6. Why the Router’s Default DNS Is Often the Weakest Link
Setting DNS on each Windows machine one at a time is fine for a single desktop, but on a household with three laptops, two phones, a smart TV and a games console, doing it at the router is faster and covers everything. Sky, BT, Virgin, TalkTalk and Hyperoptic routers all support an override in their admin settings — the wording differs (DNS servers, DNS override, manual DNS) but the field is the same. Set the router’s DNS to 1.1.1.1 / 1.0.0.1 and every device that gets its DHCP lease from the router inherits that setting from the moment it reconnects.
There is one caveat that matters. Some ISP-supplied routers ignore the manual DNS setting for their own resolver and only pass the change to DHCP clients. Others silently revert the field back to the ISP resolver after a firmware update. And a small number of ISPs’ hubs (the older BT Smart Hub 2 firmware is notorious for this) do their own DNS caching internally on top of forwarding to the ISP, which means even after you change the field, the router serves stale answers from its own cache until it reboots. When we’re called out to look at a whole-household slow-browsing problem in a place like Meadowbank, changing DNS at both the router and any critical Windows machine belt-and-braces is the pragmatic move — and this is one of the calls we cover under networking and Wi-Fi or, for a small office, business IT support.
7. What We Check on the Bench When Someone Says “Browsing Is Slow”
DNS is the first thing we look at, but it is not the only thing. On a machine that comes in for “slow browsing but the connection tests fine”, we run the DNS timing test above; if it’s clean, we then check the Windows negative cache, look for a stuck WFP filter left over from a VPN uninstall that’s slowing every outbound socket, check whether the network adapter’s Receive-Side Scaling and Large Send Offload are enabled at the driver level (a common Realtek driver update in the last year quietly turns them off and cripples throughput on browsing without moving the peak-throughput number), and check that the machine isn’t routing through a leftover proxy or PAC file in Internet Options.
We also look for the software side: Chrome extensions that inject a request through a remote server (some ad-block variants and “privacy” extensions do this, honestly or otherwise), a corporate VPN client left running from a hybrid-work laptop that’s tunnelling everything to a server in Slough, or Windows’ own Delivery Optimisation background traffic pulling updates for the whole subnet through your connection. Any of those can look exactly like a slow line if you only measure with a speed test. This is the kind of thing a short software troubleshooting pass sorts, and it’s the pass we do before ever recommending anyone change their broadband package.
8. When It Isn’t DNS — the Other Common Causes
If DNS is fast, the pattern is different every time. The commonest three we still see: an older router doing NAT at 100Mbps line speed even though the fibre is 500 (you’ll see the CPU peak-out under real load, but never on a single-flow speed test), an evening congestion pattern that’s actually a shared 2.4GHz Wi-Fi channel rather than the line (covered in the Marchmont evening Wi-Fi slowdown guide), or a laptop that’s connected fine but has a background sync process saturating its own upstream (OneDrive after a big drop, iCloud Photos on a new phone, Windows Update on Delivery Optimisation).
The one setup change that catches most of those without diagnosis: put the Windows machines on a good public resolver as above, put anything critical on a wired connection where a cable run is possible, and, if the router is more than four years old and the ISP hasn’t swapped it, look at what a modern router does for the same money as another year of “why is browsing slow” calls. For a hybrid worker’s laptop that flips between home and the office, our video-calls-dropping guide covers the neighbouring pattern — DNS-fine but call-quality flakey — and often the two are the same underlying network sitting behind different symptoms.
If your Meadowbank flat is showing 400Mbps on a test and half a second on every click, the fix is almost certainly a fifteen-minute DNS change on your Windows machine and a matching setting on the router, and no new hardware. If you’d rather someone came out and did it while checking the rest of the network at the same time, a short visit around Meadowbank, Willowbrae, Restalrig, Piershill or up toward Portobello is normally same-day. Ring, WhatsApp or drop into home-visit Meadowbank and we’ll be along.
Last updated: 1 October 2026