Two connections can both test at 200 Mbps, yet one feels instant and the other oddly sluggish. The difference is latency — the time a tiny request takes to travel to a server and back. It governs how quickly pages start loading, calls respond and games react, and most people have never seen their number. This guide explains latency in plain English and shows how to improve yours.
Below you will find the checks in the order an experienced network engineer would do them, starting with the free and simple ones. Work through them in sequence rather than jumping to the last step, because each result tells you whether the next step is even necessary for your situation.
Understanding the Problem First
Most people jump straight to fixes, but a minute spent understanding the moving parts saves a lot of wasted effort later. Your connection is a chain — the line or signal reaching your home, the router or modem, the wiring or Wi-Fi inside, and finally the device you are using. A weakness anywhere in that chain produces the same vague symptom, which is why guessing rarely works and simple tests do.
- Latency is measured in milliseconds (ms) as ping. Under 20ms feels instant, 20–50ms is normal for home broadband, and above 100ms browsing and calls feel noticeably delayed.
- Every web page needs multiple round trips — DNS lookups, connection setup, then content — so high latency taxes pages far more than single big downloads.
- Distance sets a floor: light in fibre covers roughly 200 km per millisecond of round trip, so a server on another continent cannot answer in under about 60–80ms.
- Latency spikes under load (bufferbloat) matter more than the idle average; a connection idle at 12ms but spiking to 400ms when busy will feel broken.
What You Need Before You Start
Before you start, gather the basics and make the job easier. Log in details for your router are usually printed on its label, and your account details are in your provider’s app or your welcome email. Work when you can afford twenty minutes of interruption, and tell the household what you are doing so nobody ‘fixes’ things halfway through.
- Your router admin password and provider account login
- A phone or laptop for testing, plus an Ethernet cable if you have one
- A notebook or notes app to record results and times
- About twenty minutes when the household can tolerate a restart
Step-by-Step: How to Work Through It
Follow these steps in order. Each one either solves the problem outright or narrows it down, so do not skip ahead — the early steps are deliberately the cheapest and most common fixes.
Step 1: Measure your latency properly
Run a speed test and note the ping figure, then test again while a large download runs on another device. Record both idle and loaded latency — the gap between them reveals more about your browsing experience than any headline speed. Do not rush this stage to reach the ‘real’ fix. In practice, careful checks like this one are the real fix — they separate a five-minute adjustment from an unnecessary purchase.
Step 2: Understand where your latency comes from
Add up the contributors: your Wi-Fi hop (2–10ms), your access technology (fibre 5–15ms, DSL 20–40ms, satellite far higher), the route across the internet, and queuing in your router when it is busy. Each is fixable or choosable to a degree. Once done, leave the setup alone for a while and use it normally. Many network problems are intermittent, and an hour of ordinary use is a better test than thirty seconds of optimism.
Step 3: Cut the in-home contribution first
Wire key devices or sit within strong Wi-Fi range, because a struggling wireless link retransmits constantly and inflates delay. Replace an ancient router; its processor and queue management are part of your latency whether you see them or not. Write down the result before moving on, even if it looks unremarkable. Small notes taken now become the pattern that identifies the cause later, and they are exactly what support teams ask for.
Step 4: Fix latency under load with SQM or QoS
Enable Smart Queue Management or QoS on the router and, if asked, set your line’s real speeds slightly below maximum (about 95%). This one setting is the recognised cure for bufferbloat and transforms how responsive browsing feels on a busy connection. Give the change a few minutes to settle and then retest the same thing you tested before it. Comparing like with like is how you know whether this step helped or simply changed the scenery.
Step 5: Choose nearer services where you can
Use DNS resolvers with nearby servers such as 1.1.1.1 or 8.8.8.8, pick regional game and cloud servers closest to you, and prefer CDNs’ local endpoints. You cannot move a server, but you can often choose a closer one. If this step reveals something unexpected, do not panic or stack more changes on top. Note it, finish the remaining checks, and judge everything together at the end with a full picture.
Step 6: Judge improvements by feel plus numbers
After each change, retest idle and loaded ping and simply browse your usual sites. Consistent loaded latency under about 50ms is the point where most people stop noticing delay altogether. Take a photo of any settings page before you alter it. That simple habit means every change in this guide is reversible in a minute if it does not suit your setup.
Expert Tips to Get the Best Result
Once the basics are handled, small refinements make the difference between ‘working’ and ‘working well’. Keep your router’s firmware updated, because manufacturers quietly fix stability and security issues in releases most people never install. Revisit your setup after any big change — a new TV, a house extension, a change of provider — because a configuration that suited last year may not suit the home you have now. Finally, keep your notes: a dated record of speeds, settings and faults turns every future problem into a shorter one.
For wider background reading, the Wikipedia explanation of latency in systems is a solid starting point, and the Cloudflare guide to internet latency and its causes covers the official detail. You will also find our guides to understanding broadband performance, with related walkthroughs for the rest of your home network.
Common Mistakes and How to Avoid Them
A final tip that applies to almost every mistake above: change one thing, test it properly, and only then decide. Households get into trouble not because individual fixes are wrong, but because three fixes applied at once leave nobody knowing which one worked — or which one made things worse.
- Chasing a faster Mbps plan to fix what is actually a latency problem — capacity and delay are different things.
- Testing ping only when the network is idle and declaring everything fine.
- Ignoring Wi-Fi’s contribution and blaming the ISP for retransmissions happening two metres from the router.
- Comparing your ping to a server on another continent against a friend’s ping to a local one.
Conclusion
You now have a complete, ordered way to tackle this problem: understand the chain, work the steps in sequence, and judge by measured results rather than impressions. In most homes the answer turns out to be something small — a cable, a setting, a position, a schedule — rather than an expensive upgrade. If your checks instead prove the fault lies beyond your walls, you have the log and the language to make your provider deal with it. Either way, your connection ends up faster, steadier and properly understood.
Frequently Asked Questions
What is a good latency for everyday browsing?
Idle ping under 30ms with loaded latency staying under roughly 60ms feels snappy for browsing, calls and casual gaming. Consistency matters as much as the average — wild swings feel worse than a steady 50ms.
Why do pages load slowly when my latency is fine at idle?
Because pages load while other traffic is moving, and loaded latency is what they experience. Test ping during a download; if it balloons, bufferbloat — fixable with SQM/QoS — is your culprit.
Does fibre broadband have lower latency than DSL?
Yes, typically. Full fibre commonly shows 5–15ms to nearby servers, while DSL’s error correction and copper path often land at 20–40ms. Satellite is the outlier, with far higher delay.
Can I get latency to zero?
No — physics forbids it. Signals take time to travel and be processed; the goal is keeping total delay low and stable, not eliminating it. Anyone promising zero latency is selling something.
What is jitter and why does it matter?
Jitter is the variation between successive ping times. High jitter makes calls sound robotic and games stutter even at a decent average ping, because data arrives unevenly instead of in a steady stream.
Leave a Reply