This internet speed guide explains download speed, upload speed, ping and jitter so you can choose the correct next step without confusing Wi‑Fi limits, device caps, router queueing and provider faults.
Internet speed test results
A single Mbps number cannot explain every broadband problem. Use the clean test below, then match the failed metric to Wi‑Fi, device, router-load or provider evidence before changing hardware or packages.
Instant interpretation
Use your latest Mbps result to decide whether the issue is simply lack of capacity or whether the next test should focus on Wi‑Fi, loaded latency or provider routing.
Enter a recent speed-test result, then choose the activity profile that best matches the household. The output tells you whether the raw capacity is comfortable, borderline or unlikely to be the main fault.
It is useful when a speed result looks “fine” on paper but the household still struggles. The calculator separates raw capacity questions from the deeper fault boundary.
Start here
Keep the device, test server and browser conditions consistent. Change one variable at a time so the result proves where the limit sits.
Stop downloads, cloud backup, CCTV uploads, software updates and other speed tests.
Use a modern device and record download, upload, ping and jitter from the same test.
Use a known-good cable where possible. Confirm the wired link is 1 Gbps rather than 100 Mbps.
Repeat on the affected device or in the slow room without changing the server.
Retest while the household is active and note whether ping, jitter or upload changes sharply.
Browser check: if one older device reports unusually low speeds, retry in a private window with extensions disabled or compare another modern device. Browser CPU limits can distort high-speed tests.
Metric meanings
How quickly data reaches your device. It affects streaming quality, large downloads, app updates and how many people can consume content at once.
How quickly your device sends data out. It affects video calls, backups, CCTV, livestreaming and file sharing.
The round-trip delay to a server. Lower is better for gaming, voice calls, remote desktops and other interactive services.
The variation between packet delays. High jitter can create call dropouts, robotic audio, stream stutter and gaming micro-freezes even when average ping looks acceptable.
This diagram shows why one speed result can disagree with another. Traffic does not only travel between your device and the router; it continues through the ISP exchange and on to the edge server or CDN host that actually serves the content or test file.
Weak Wi‑Fi, retransmissions, a 100 Mbps wired link or a busy router can distort the result before the traffic ever leaves the house.
If wired tests fall below the package speed at the same quiet times, look at the router sync, line profile or local exchange congestion.
If a streaming-specific test such as Fast.com is consistently lower than the main LinkSpeed speed test on the same device and time, compare both before blaming local Wi‑Fi. That mismatch can point to peering, CDN selection or app-delivery issues.
Typical UK result ranges
These are practical reference ranges, not contractual guarantees. Your package, server distance and access technology matter more than one universal number.
| Metric | Strong result | Usable result | Investigate when |
|---|---|---|---|
| Download | 200 Mbps or more for busy multi-user homes | 30–200 Mbps for typical streaming and browsing | Repeated wired results are below the expected package range |
| Upload | 20 Mbps or more for frequent calls, backups and sharing | 5–20 Mbps for ordinary calls and light uploads | Calls fail, uploads crawl or loaded latency rises sharply |
| Idle ping | Below 20 ms to a nearby UK server | 20–40 ms can still feel responsive | Wired ping stays high when the connection is quiet |
| Jitter | Below 5 ms | 5–15 ms may be acceptable | Voice, video or games stutter and the figure varies widely |
| Loaded latency | Small increase above idle | Moderate rise under heavy load | Ping jumps by tens or hundreds of milliseconds during transfers |
Result-led diagnosis
The result should decide the next action. Do not treat every poor experience as a download-speed problem.
This points to local Wi‑Fi range, obstruction, mesh placement or band choice rather than the broadband line.
The client may have an older Wi‑Fi standard, a 100 Mbps Ethernet port, weak antennas, outdated drivers or a browser CPU limit.
Check ping, jitter, packet loss and loaded latency. Bulk capacity can be excellent while real-time traffic still waits in queues.
This is a loaded-latency or queue-management problem until testing proves otherwise.
A 100 Mbps Ethernet link, old network card, damaged cable or legacy router port is likely capping the result.
Check the operating-system link speed and replace the cable or port before escalating.
Build a repeated wired log. If the pattern survives with household traffic paused, peak-time provider congestion becomes more likely.
Advanced router audit
Use this only when ordinary Wi‑Fi, device and Ethernet comparisons do not explain why the connection becomes unstable under load.
First identify the real shaped interface. Do not assume that every installation uses pppoe-wan or the same IFB name.
uci show sqm
ip link show
tc qdisc showtc -s -d qdisc show dev pppoe-wan
tc -s -d qdisc show dev ifb4pppoe-wantop
cat /proc/softirqs
cat /proc/interruptsInterpretation: persistent backlog with rising loaded latency can indicate incorrect shaping or another unmanaged queue. Controlled AQM drops or ECN marks are not automatically faults. Low backlog with collapsing throughput points more strongly to CPU, driver or offloading limits.
This page defines the counters and identifies the fault boundary. For upstream saturation and queue-management tuning, continue to the slow upload guide. For CPU, offloading and SQM capacity, use the router SQM and hardware-acceleration guide.
Provider escalation
Use the same modern device, Ethernet cable and test method. Record time, download, upload, ping and jitter across several tests.
Verify the Ethernet link is 1 Gbps or faster. A 100 Mbps negotiation will usually cap real throughput near 90–95 Mbps.
Record the package, expected range, minimum guarantee where applicable and router sync or line rate before contacting support.
Tell the provider whether the issue is low download, low upload, high idle ping, high jitter or peak-time degradation rather than reporting only “slow internet”.
Escalate when: repeated Ethernet results remain below the expected or guaranteed range with background traffic paused, or the same line-level problem appears across multiple devices and times.
Diagnostic tools
Measure download, upload, ping and jitter together.
Run the LinkSpeed speed test →Measure latency to a chosen server and compare consistency.
Run the ping test →See how much latency rises while download and upload are busy.
Run the bufferbloat test →Check whether dropped packets are causing stutter or call problems.
Run the packet-loss test →Convert Mbps into practical download times for large files.
Use the speed calculator →Compare the technologies available at the property before upgrading.
Check broadband availability →FAQs
Download speed measures bulk bandwidth capacity. Gaming and video calls depend more on low idle ping, low jitter and stable loaded latency, so a fast connection can still lag when router queues fill or packets arrive unevenly.
Wi‑Fi is a shared half-duplex radio medium affected by distance, obstructions, interference and retransmissions. Ethernet removes those radio variables, although a 100 Mbps port or damaged cable can still cap a wired result near 90 to 95 Mbps.
Lower and consistent is better. For many UK connections, idle ping below 20 ms and jitter below 5 ms are strong results, but server distance and access technology can make higher figures normal.
Contact the provider when repeated Ethernet tests remain below the expected or guaranteed range with household traffic paused, or when the same line-level problem appears across multiple devices and times.