A fast speed test with a slow-feeling connection almost always means the problem isn't bandwidth. A speed test measures how much data you can move to a nearby server for a few seconds. Slow pages, laggy games and freezing calls usually come from latency (especially when the line is busy), packet loss, slow DNS, a slow or distant server, or the device you're using.
Match the symptom to the likely cause
| What you notice | Most likely cause |
|---|---|
| Pages pause before they start loading, then load fast | Slow DNS lookups or a VPN/proxy |
| Everything lags when someone uploads or downloads | Latency under load (bufferbloat) |
| Calls drop words, games rubber-band | Packet loss or jitter, often on Wi-Fi |
| One site or app is slow, others are fine | That service's servers, or the route to them |
| Only one device feels slow | That device's Wi-Fi, software or adapter |
| Slow mainly in the evening | Congestion at your provider or the service |
Why a good speed test can miss the problem
It tests to a close server. SpeedMetric, like most speed tests, measures against a server near you. A game server in another country or a website hosted far away can be much slower than that, and the test can't see it.
It runs when the line is idle. SpeedMetric reports idle ping, the delay when nothing else is using the connection. Many connections are fine when idle and slow down badly as soon as someone starts a big upload. That extra delay under load is called bufferbloat, and SpeedMetric doesn't measure it.
It doesn't measure packet loss or DNS. Our test shows download, upload, idle ping and jitter. Lost packets and slow name lookups won't show up in those numbers, but you'll feel them.
It measures bandwidth, not responsiveness. Loading a web page involves dozens of small requests. Each one waits for a round trip, so 50 ms of extra delay can matter more than doubling your Mbps.
Narrow it down in this order
1. Test under load yourself
Run a speed test and note the ping. Then start something heavy on another device (a large upload, a cloud backup, or a game download) and test again. If ping jumps from, say, 20 ms to several hundred, you've found bufferbloat. The usual fixes are pausing the big transfer, setting upload limits in backup apps, or enabling Smart Queue Management (SQM) or a similar feature on a router that supports it.
2. Check for packet loss
Use your computer's built-in ping tool to a reliable address:
- Windows: open Command Prompt and run
ping -n 100 1.1.1.1 - macOS or Linux: open Terminal and run
ping -c 100 1.1.1.1
At the end, look at the "lost" or "packet loss" figure. As a rule of thumb, a wired connection should show 0% or very close to it. Loss that keeps appearing on a cable is worth reporting to your provider. If loss only appears on Wi-Fi, the problem is in your home. Packet loss and lag explains what different amounts mean.
3. Rule out DNS
If pages hesitate for a moment before anything appears, then load quickly, DNS is a likely suspect. Try switching the device or router to a different public DNS resolver and compare. Does DNS affect internet speed? explains what DNS can and can't change. It speeds up the start of a connection, not the download itself.
4. Turn off VPN and proxy settings
A VPN adds distance and an extra hop to every request, so each page waits longer for its first byte even when bandwidth is fine. Disconnect it and compare. If speed and responsiveness come back, pick a closer VPN server or use split tunnelling for everyday browsing.
5. Compare devices and connections
Test on a second device, then on Ethernet if you can. If only one device is slow, our guide to internet that's slow on one device covers Wi-Fi bands, drivers and background apps. If everything is slower on Wi-Fi than on a cable, the fix is in your Wi-Fi coverage, not your plan.
6. Check the service itself
If one app, site or game is slow and everything else is fine, the problem is probably on their side. Check the service's status page, or try another server region in the game's settings. You can't fix a slow website by changing your router.
When it is your provider
If ping is high even when the line is idle, packet loss appears on a wired connection, and the slowdown hits every site at the same times of day, contact your provider. Bring evidence: dated speed test results, the ping-test output with packet loss, and the times it happens. For a broader checklist, see why is my internet slow?
What a speed test is still good for
A good speed test result isn't useless. It rules out the most common problem, a plan or line that can't deliver its speed, and it points you toward latency, loss and the far end instead. Keep a few results from different times and devices. They make the next step much easier to choose.
Common questions
Can my ISP make a speed test look faster than real use?
Speed tests usually hit a server close to you, often inside or near your provider's network, so they show the best case. Routes to distant sites can be slower, and that's not visible in a nearby test.
Will a faster plan fix it?
Only if your Mbps is actually the limit. If the speed test already clears what your apps need, a faster plan won't fix latency, packet loss, DNS or a slow website.