“My internet is slow” is one of the most common complaints, but without measurements it is hard to tell whether the problem is your ISP plan, home Wi‑Fi, an overloaded router, or a single service. A speed test gives numbers — it does not explain why video buffers or a video call keeps dropping.
This guide covers how to check internet speed properly, which metrics matter, why connections slow down, and how to tell a general line problem from a local issue.
Where and how to run a speed test
Use 2–3 independent services and compare results:
- Speedtest by Ookla
- FAST.com
- Cloudflare Speed Test
- Yandex Internet Meter (useful in CIS regions)
Basic methodology:
- Stop downloads, torrents, cloud sync, and streaming on other devices.
- Run 3–5 tests in a row on one service and record the median, not the best run.
- Repeat at different times of day — evening load on ISP networks is usually higher.
- Test over Ethernet first (if possible), then over Wi‑Fi — that isolates the bottleneck.
If you use a VPN, compare before and after with the same method — see internet speed and ping: with VPN vs without.
Metrics that actually matter
A speed test reports several values. Each maps to real use cases:
| Metric | Meaning | Affects |
|---|---|---|
| Download (Mbps) | Incoming data rate | Streaming, file downloads, updates |
| Upload (Mbps) | Outgoing data rate | Video calls, live streams, cloud backups |
| Ping (ms) | Round-trip latency | Gaming, calls, remote desktop |
| Jitter (ms) | Latency variation over time | Voice/video call stability |
| Packet loss (%) | Dropped packets | Stutter, dropouts, robotic audio |
For everyday browsing, download dominates. For calls and games, low ping and stable jitter often matter more than peak download speed.
How much speed you need in practice
Rough plan guidelines (real throughput is often 10–30% below advertised):
- 1–5 Mbps — messaging, email, light sites; HD video will buffer.
- 10–25 Mbps — comfortable Full HD on one device, video calls.
- 50–100 Mbps — several devices at once, 4K on one screen.
- 100+ Mbps — large household, heavy downloads, local NAS, multiple 4K streams.
Upload is often much lower than download. If calls stutter while download looks fine, check upload specifically.
Main causes of slow internet
1. ISP network congestion
During peak hours (often 7–11 p.m.), many subscribers share the same capacity and speeds drop. If you get 90 Mbps at noon and 25 Mbps at night, the issue is likely upstream — not your laptop.
What to do: log tests at different times, save screenshots, and contact support with dates and results.
2. Weak or overloaded Wi‑Fi
Router in a corner, concrete walls, crowded 2.4 GHz channels, many connected devices — all cut throughput even on a good plan.
Signs: Ethernet is fine, Wi‑Fi is 2–5× slower; one or two signal bars; worse farther from the router.
What to do:
- Place the router centrally and elevated.
- Use 5 GHz (faster, shorter range) or mesh/repeaters.
- Update router firmware; change Wi‑Fi channel.
- Prefer Ethernet for PCs and set-top boxes when possible.
3. Outdated router or plan mismatch
An old router with 100 Mbps ports or 802.11n Wi‑Fi will not deliver a 300–500 Mbps plan. Cheap single-core units struggle with many clients.
What to do: match router specs to your plan; upgrade hardware or ask the ISP for a newer model.
4. Background downloads and updates
Windows Update, iCloud/Google Photos backup, Steam, torrent clients, security cameras — all consume bandwidth quietly.
What to do: close unnecessary apps, check Task Manager / phone network monitor, schedule heavy sync for off-peak hours.
5. ISP throttling and shaping
Some providers slow specific protocols, P2P, or traffic after quota use. Occasionally speed tests are shaped while other services look normal.
What to do: compare speed tests with a large file download from another source. If shaping is suspected, try different DNS, protocol, or VPN optimization if you already use VPN to work around limits.
6. Line problems to your home
Bad patch cable, corroded connector, damaged building wiring, faulty ONT/modem — cause instability, latency spikes, and packet loss.
Signs: frequent dropouts, jumping ping, low speed even on Ethernet straight into the router.
What to do: ISP technician visit, cable replacement, ONT/DSL modem check.
7. Malware and unwanted software
Botnets, cryptominers, or aggressive “speed booster” apps can load the link or hijack DNS.
What to do: antivirus scan, review startup items, change Wi‑Fi password. See internet security basics.
8. Issues with one site or service
If only YouTube is slow but speed tests show 100 Mbps, the problem is not “slow internet” globally — it is routing to a CDN, blocking, or server load.
What to do: test the same service on another device, mobile data, or VPN; see how website blocking works.
Other problems besides “low speed”
High ping
Latency above 50–80 ms hurts online games and sometimes calls. Causes: distant servers, congested Wi‑Fi, VPN, poor ISP routing.
Ping to your speed-test server and to your game server are different measurements. Test where you actually work or play.
Packet loss
Even 1–3% loss causes video stutter and voice dropouts. Often tied to Wi‑Fi, cabling, or an ISP hop — not raw Mbps.
Check packet loss on repeated speed tests; on Windows run ping -n 50 8.8.8.8 and read the “Lost =” line.
Unstable connection
Internet that comes and goes — overheating router, IP conflict, DHCP glitch, line fault. Rebooting the router helps temporarily but does not fix root cause.
Slow page loads with normal speed-test results
Often DNS: slow or hijacked resolver. Switch to 1.1.1.1 or 8.8.8.8 and compare. With VPN, check for DNS leaks.
“Internet works but pages won’t open”
Check: does IP work (ping 1.1.1.1)? Does a site open by IP? Is DNS broken? Is the resource blocked? Separating “no link” / “no DNS” / “blocked site” saves hours of guessing.
Step-by-step troubleshooting
- Speed test over Ethernet — 3–5 runs; median download/upload/ping/packet loss.
- Speed test over Wi‑Fi next to the router — compare to Ethernet.
- Speed test on phone over mobile data — is the issue local to home?
- Ping 50 packets to the router gateway and to 8.8.8.8 — look for loss.
- Check background traffic on all devices on the network.
- Reboot the router (power off 30 seconds) — not a permanent fix.
- If Ethernet speed is consistently below plan — call the ISP with logs.
When to contact your ISP
Worth escalating if:
- Ethernet speed stays below ~70–80% of your plan;
- you see packet loss or dropouts with working hardware;
- the issue lasts several days at different times;
- replacing router and cable changed nothing.
Bring: service address, account number, dated test screenshots, router model, and whether tests were Wi‑Fi or wired.
Common testing mistakes
- One test instead of a series — a single spike or dip misleads.
- Testing only through VPN without a no-VPN baseline.
- 4K streaming on TV during the test.
- Comparing phone Wi‑Fi results to wired plan speed.
- Confusing Mbps (megabits) with MB/s (megabytes): a 100 MB file at 100 Mbps takes ~8–10 seconds, not one second.
Public Wi‑Fi: a separate case
In cafes and airports, speed tests may look fine while real services lag because the access point is overloaded, filtered, or hostile. Risks and tips: public Wi‑Fi security.
Conclusion
Checking internet speed is not a one-click affair — it means multiple measurements under controlled conditions, looking at download, upload, ping, and packet loss together. Most slowdowns come from Wi‑Fi, background load, or evening congestion, but you can only rule out a faulty line with structured diagnostics.
If VPN is part of your setup, also read ping, latency, and speed with VPN and what your ISP can see — sometimes “slow” is about routing and filtering, not megabits.