The short answer: the slow part is usually beyond your home
If almost everything you do online is quick but one website, one game server or one download crawls, your broadband line and router are very likely doing their job. BT's own help pages put the first check simply: try a different website, and if that works, "your set-up is okay and the fault is with the website you were originally trying to visit".
That does not always mean the website is broken. Between your home and any server there is a chain of networks, and the slowdown usually comes down to one of four things:
- The server itself is busy, overloaded or being worked on.
- Distance: the server is a long way away and the site has no nearby copy of its content.
- The route: your traffic is taking a long or congested path across other networks to reach it.
- A fault in your provider's network that affects only some destinations. The least common, but the one your provider can fix.
Similar-sounding problems have their own guides: why broadband slows down in the evening (everything slow at busy times), why one device is slower than the rest, why streaming keeps buffering and what to do when a website is blocked.
How your traffic actually reaches a website or game server
Your broadband provider runs one network. The website or game you want sits on another. To get from one to the other, your provider has to hand your traffic over, and the London Internet Exchange (LINX) describes two main ways of doing that:
- Peering: two networks connect and exchange traffic with each other directly. LINX describes peering as voluntary, and says most peering arrangements are settlement-free, meaning no money changes hands.
- IP transit: a paid arrangement in which a transit provider carries a network's traffic to and from the rest of the internet.
Because peering is a choice each network makes, every provider ends up with its own set of peering partners and transit suppliers. That is our reading of why two providers can reach the same server by quite different paths, and it fits the routing faults described further down, which hit customers of one provider while everyone else was fine.
Internet exchanges: where networks meet
A lot of peering happens at an internet exchange point (IXP), which LINX defines as "a physical location where different networks connect and exchange internet traffic directly". At an exchange, LINX says, traffic is exchanged locally rather than travelling long distances. In the UK, LINX lists exchanges in London (two of them, LON1 and LON2), Manchester, Scotland and Wales; it runs nine exchanges in all across the UK, the US and Africa (checked October 2026).
Why the route makes a difference
Without an exchange, LINX says, data often travels a longer path through several third-party networks, and each extra one adds delay and increases the chance of congestion, which results in higher latency: the delay between data being sent and received, measured in milliseconds (ms). LINX calls these intermediate networks hops. In a traceroute (see below) each hop is a single router instead, so one network usually shows up as several lines.
LINX's explainer on latency names the physical distance data must travel and the number of hops between origin and destination among the things that drive it, and says latency can be reduced by peering. Its peering explainer adds that when networks do not peer, data often travels long distances through third-party transit providers.
Cloudflare adds that latency can never be eliminated completely, and that bandwidth (what your package's Mbps figure describes) and latency measure different things. Our guide to latency, ping and jitter explains the difference in more depth.
So a faster package rarely cures one slow site: more Mbps gives you a wider pipe, not a shorter journey.
Why big websites usually feel fast: content delivery networks
The busiest websites and apps rarely serve everyone from one building. Most use a content delivery network (CDN). Mozilla's developer documentation describes a CDN as a group of servers spread over many locations that store duplicate copies of data, so each request is answered by the servers closest to the user. Akamai, one of the large CDN companies, explains that edge servers in many places hold copies of content from the origin server, cutting latency by shortening the distance it travels.
A site without a CDN serves everyone from its origin servers, wherever they are. A small forum, niche shop or independent game server may be hosted in another country, so it can feel sluggish next to the giants even when nothing is wrong.
CDNs have a downside too: Mozilla points out that if a CDN goes down or is blocked in a region, websites relying on it malfunction, so a batch of unrelated sites can misbehave at once.
When the problem is at the other end
Sometimes the server simply can't keep up. Two error codes you may see in your browser tell you this directly:
- 503 Service Unavailable: the server is not ready to handle the request. Mozilla says common causes are maintenance or overload, and some server software rejects requests once memory, processor or connection limits are reached.
- 429 Too Many Requests: the site is rate limiting, deliberately turning away requests it thinks are coming too fast.
Neither is a broadband fault, and your provider can't fix either. The wider internet can also clog up: thinkbroadband lists congestion on the wider internet among the causes of slow speeds, saying it "can happen on some routes and is especially likely during busy events". A big game's launch day or a popular ticket sale could do it (examples only).
If you suspect the far end, wait a while and check the site's or game's status page or official social accounts.
Symptom checker
What you see | Most likely cause | What to do |
|---|---|---|
One site slow or showing 503 or 429 errors, on every network you try | The site's own servers | Wait, and check the site's status page or social accounts |
One small or overseas site always a bit sluggish, nothing else affected | Distance to its server, no nearby copy | Usually nothing to fix; it is how the site is hosted |
Certain sites or servers slow or timing out on your broadband, fine on mobile data, and other customers of your provider report the same | A routing or peering problem in or near your provider's network | Gather evidence and report it to your provider |
Everything slower, mainly in the evenings | Busy-time congestion | See our guide to evening slowdowns |
Every site slow on one device only | That device or its Wi-Fi connection | See our guide to one slow device |
When it is your provider's network: routing and peering faults
Occasionally one of your provider's links to the wider internet goes wrong, and only traffic heading that way suffers. These faults are not common, but they are real, and UK providers have had them over the years:
- TalkTalk, 18 March 2025. Some TalkTalk customers couldn't reach certain websites, including sites on github.io, with pages timing out. ISPreview reported that it appeared to be a peering or routing problem, though at first it could not rule out TalkTalk's network-level filtering (such as parental controls), and that sites on several CDN platforms were affected. TalkTalk then said its investigation "identified a traffic routing issue that affected a small number of customers and websites", and that it had been resolved.
- Giganet (a brand since folded into Cuckoo), 25 July 2023. ISPreview reported customers finding that "some online sites and servers may be fine, while others might be sporadically slow or fail completely". Giganet said its teams had identified a potential issue with its transit providers, and service was later restored.
- Be Broadband and O2 home broadband (both bought by Sky in 2013), April 2012. Some websites were slow and others wouldn't load; the provider blamed a problem at one of the third-party peering platforms it used.
The pattern each time: particular sites slow or failing for one provider's customers while working for everyone else. If that matches what you see, report it.
Why changing DNS won't fix a routing fault
DNS (the Domain Name System) is the internet's lookup service: it turns a name like a website address into the numeric address your device actually connects to. Swapping DNS provider is a common tip for "slow internet", but ISPreview noted during the Giganet incident that using a third-party DNS provider has no impact on this sort of issue. DNS finds the address; it does not choose the path your traffic then takes to get there.
DNS problems look different. A DNS fault tends to stop sites loading at all rather than making one site slow. BT's advice is that if no sites work, you should check your device is set to obtain its IP and DNS server addresses automatically. Our guide to what DNS is and whether to change your DNS server covers the pros and cons properly. If you think one kind of traffic is being deliberately held back, see whether your provider can slow down or block websites.
How to work out where the slowdown is
Work through these checks and write down what you find: it turns a vague complaint into something your provider can act on.
- Try other sites and services. If other websites load normally, BT's logic says your set-up is fine and the problem lies with that destination or the route to it.
- Try another device on the same connection. If the site is slow on one laptop but fine on a phone using the same Wi-Fi, the device is the more likely culprit.
- Switch off any VPN and test again. The Electronic Frontier Foundation explains that a VPN routes all your web traffic through an encrypted tunnel to the VPN company's server, so the route to the site changes completely. Proton VPN notes that a VPN can even occasionally bypass a problem elsewhere on the internet, so a site that is slow without your VPN but fine with it is one more hint that the route, not the site, is at fault. See our guide to using a VPN on home broadband.
- Try a different network. Turn off Wi-Fi on your phone and load the same site or game over mobile data. Your traffic then takes the mobile network's route rather than your broadband provider's. It is a pointer, not proof (and uses your data allowance), but if the site is reliably fast on mobile and slow on broadband, your provider's route to it becomes a suspect.
- Check your line with a wired speed test. Plug a computer into the router by cable and run our broadband speed test. A normal result is useful evidence that the line is healthy, though a speed test only measures the path to its own server: ISPreview's informal 2021 test found results vary with the test server's location. Our guide to why speed tests give different results explains why.
- Repeat at different times. If the slowdown only appears in the evening and affects other sites too, you are probably looking at busy-time congestion rather than one bad route.
- Ask around. Friends on other providers reaching the same server fine, or other customers of your provider reporting the same issue, strengthen the case for a provider routing problem.
Running a traceroute
A traceroute shows the path your traffic takes to a destination, one router at a time. It sounds technical, but on a Windows PC it takes a minute:
- Open the Command Prompt (tracert is a command-line tool).
- Type tracert, a space, then the website address (for example, tracert followed by the site's name) and press Enter.
- Wait for it to finish. Adding /d after tracert stops it looking up a name for each router, which Microsoft says can speed up the results.
Microsoft's reference explains the output. The first column is the hop number, each hop being an intermediate device such as a router. The three middle columns are round-trip times in milliseconds from your computer to that router and back. The last column is the router's address, or its name if one can be found. Some routers don't answer the messages tracert relies on, and a row of asterisks appears for that hop; on their own, asterisks are not proof of a fault. Microsoft also points to a second command, pathping, which reports latency and packet loss (data that fails to arrive) for each router and link along the path.
You needn't interpret the results yourself: keep a copy run during the problem (and one when it isn't) to send to your provider.
Extra checks for games
As our guide to latency, ping and jitter explains, game lag depends on latency and how steady it is (jitter), not raw speed. Community Fibre lists route changes among the causes of jitter (packets taking different paths experience different delays) and stuttering and lag spikes in games among its symptoms. Before blaming the route, rule out the home end: wire the console or PC and pause big background downloads. Our guide to broadband for online gaming covers the home set-up, and if your problem is joining or hosting games rather than lag, it explains NAT types too.
Reporting it to your provider
Openreach says your broadband provider, not Openreach, is the place to start with slow speeds, and the same goes here: your provider runs the connections between its network and the rest of the internet.
It is worth reporting when the same site or server is slow on your broadband but fine on another network, a wired speed test shows your line is otherwise fine, and the problem has lasted more than a day or keeps coming back. It is not worth it when the site shows 503 or 429 errors, is slow everywhere or has announced an outage: that is the site's problem.
When you get in touch, have this ready:
- the exact website address, or the game and server or region name;
- dates and times you saw the problem, and what happened (slow, timing out, high ping);
- your result on mobile data or another network;
- a wired speed test result;
- your traceroute output, if you ran one.
Say at the start that other sites work normally, then ask whether there is a known routing or peering issue to this destination, whether the case can go to the network team with your traceroute attached, and whether they will tell you when it is fixed. The TalkTalk and Giganet incidents above were both put right once the provider found the fault. See how to report a broadband fault and, if the response stalls, how to complain about your broadband provider.
If it keeps happening: would a different provider help?
Because each provider chooses its own peering and transit arrangements, a routing problem that is specific to your provider will not necessarily follow you to another one. But there is no guarantee, and we have found no published data comparing how well UK providers reach particular sites or game servers, so treat claims that one provider is "better for gaming routes" with caution.
Be realistic about your rights, too. Under Ofcom's voluntary broadband speeds code, the guaranteed minimum speed relates to the download speed to your router, not to how quickly any single website responds, and we have not found any rule that lets you leave a contract over one slow site.
If you are near the end of your contract anyway, or a problem keeps coming back despite reports, look at your options:
- check when your minimum term ends in your contract summary or account;
- see whether full fibre and other fibre broadband deals are available at your address;
- read up on the companies on our broadband providers hub, including smaller full fibre networks;
- then compare broadband deals at your postcode to see live prices and speeds from providers that cover your home.
If you do move, Ofcom's One Touch Switch process means you contact only the new provider; your current provider must then send you the switching information, including any early-termination charges. Switching won't speed up a site that is overloaded or far away, though, so check your tests point to your provider's route first.
Slow website and game server FAQs
Why is one website slow when everything else on my broadband is fast?
Usually because the slowdown is beyond your home. The site's server may be busy, it may be far away without a nearby copy of its content, or the route from your provider's network to it may be long or congested. BT's advice is that if other sites work, your own set-up is fine. Occasionally the cause is a routing fault in your provider's network.
Will changing my DNS make a slow website faster?
Not if the problem is the route or the server. DNS only looks up the address of a site; it doesn't decide the path your traffic takes. During a 2023 routing fault at Giganet (a brand since folded into Cuckoo), ISPreview noted that using a third-party DNS provider had no impact on that sort of issue. DNS problems usually stop sites loading altogether rather than making one site slow.
Why is a game laggy for me but fine for my friends?
If you are on different providers, your traffic may reach the game server by a different route. LINX explains that when networks do not peer, data often travels long distances through third-party transit providers. Rule out your home set-up first with a wired connection and no background downloads; if others on your provider see the same lag, report it.
Should I report one slow website to my broadband provider?
Report it if the site is slow only on your broadband, works on another network, and the problem lasts or keeps coming back, especially if other customers of your provider see the same thing. Don't expect a fix if the site shows 503 or 429 errors or is slow everywhere, because those point to the site's own servers. Contact your provider, not Openreach.
What is peering, and why does it affect my broadband?
Peering is when two networks exchange traffic directly, often at an internet exchange point such as those LINX runs in London, Manchester, Scotland and Wales. The alternative is IP transit, which is paid for. LINX says peering can cut the number of hops data takes and reduce latency, so your provider's connections affect how quickly particular sites respond.
Will a faster broadband package fix a slow website or laggy game?
Rarely. Bandwidth and latency measure different things, and Cloudflare notes that distance to the server is a principal cause of latency. More Mbps won't shorten the path to a distant server, fix a routing fault or speed up an overloaded website, so test where the problem is before paying for an upgrade.



