How to Reduce Latency: What Actually Works (and What Doesn't)

Quick answer: most latency you can reduce comes from three places: your own network (use a cable instead of Wi-Fi, stop your line from being saturated, fix router settings), your choice of destination (pick servers and regions closer to you) and unnecessary detours (a VPN or proxy you do not need). The part caused by physical distance cannot be reduced, only avoided by connecting to something nearer. Always measure before and after, so you know which change helped.

What can and cannot be reduced?

Latency is the delay for data to travel across a network, measured in milliseconds (ms); see what is latency. It is the sum of propagation delay (distance), transmission delay, processing delay and queuing delay. Some of these are fixed, some are not.

Component	Can you change it?	How
Propagation (distance)	Not for a given route	Connect to a closer server or region. Light in fibre travels about 200,000 km/s, so roughly 1 ms of RTT per 100 km of path
Queuing (waiting in buffers)	Often, the biggest win at home	Stop saturating the line, enable smart queue management, fix Wi-Fi congestion
Transmission (pushing bits onto a link)	On slow links, yes	Faster link; matters little on modern broadband
Processing (devices and servers)	Partly	Better router, fewer middleboxes, a faster server, caching
Route (extra hops, detours)	Sometimes	Different provider, different server, remove VPN, ask your ISP

Step 0: measure first

Without a baseline you cannot tell whether a change worked. Run several tests at the same time of day to the destinations you care about, and note the average, best and worst. With GlobeLatency you can run a test from your browser to servers around the world and see your average, best and worst pass and how you compare with the world average for each destination. Keep the saved report or note the figures. For ongoing observation while you change settings, use the monitor. Change one thing at a time and retest; otherwise you will not know which change mattered. See running a test for details.

Use a wired connection

Wi-Fi adds delay for several reasons: the radio has to wait for a clear channel, it retransmits frames that were not acknowledged, and signal strength varies with walls and distance. In a good setup Wi-Fi adds a few milliseconds; in a poor one it adds tens of milliseconds and irregular spikes. Ethernet adds well under a millisecond and is steady. If your device has a port, a cable to the router is the single most reliable improvement for gaming, calls and remote work. If a cable is impractical, consider powerline or MoCA adapters, or a wired access point, and compare the results. Details are in Wi-Fi, Ethernet, fibre, mobile and satellite latency.

If you must use Wi-Fi

• Move closer to the router or add a properly placed access point; avoid walls and appliances in between.
• Use the 5 GHz or 6 GHz band for devices near the router; they are usually less crowded than 2.4 GHz, though they reach a shorter distance.
• Choose a less crowded channel if neighbours overlap yours.
• Reduce the number of busy devices on the same network at the same time.
• Keep router firmware and device Wi-Fi drivers up to date.

Stop your own line from being saturated

When your connection is full, packets queue in the router or modem and every other packet waits behind them. Ping to everything can jump from 20 ms to several hundred. This is bufferbloat (see bufferbloat explained), and uploads are often the trigger because upload speeds are low.

Find out if you have it

Watch latency on the monitor while you start a large upload or download on the same connection. If the readings rise sharply while the transfer runs and recover when it ends, the cause is a queue on your line.

Fixes, from easiest to hardest

1. Schedule heavy transfers (cloud backups, game updates, photo syncs) outside the times you need low latency, or limit their speed in the application.
2. Enable smart queue management (SQM, using algorithms such as fq_codel or CAKE) if your router supports it. Many consumer routers offer it as "SQM", "Smart Queue", "QoS" or "adaptive QoS"; support varies by model.
3. Set the limit just below your real speed. Setting the router's download and upload limits to roughly 85 to 95 percent of what the line actually delivers moves the queue to the router, where it is managed. The exact figure needs experimenting.
4. Replace the router with one that supports modern queue management, or use a separate device for it.

Basic traffic-priority rules ("QoS") that only mark device priority, without limiting speed, help less than smart queue management on a saturated link.

Choose closer destinations

For games, video meetings, cloud tools and websites, the quickest way to cut latency is often to connect to a nearer server. Many games let you pick a region or show ping per server. Cloud tools and your own services can be hosted in a region near most users. For a website's visitors, a CDN places copies near them; see latency for websites and APIs. The live map and the global comparison show how far various regions are from you, which helps you pick sensibly. Remember the floor: no server 9,000 km away will answer in 30 ms.

Remove detours: VPNs, proxies and security software

A VPN sends your traffic through the provider's server, so the path is your device to the VPN server to the destination. That usually adds distance, encryption work and an extra hop. Turn it off for gaming or calls unless you need it, or pick a VPN server near you and near the destination. Corporate proxies, security suites that inspect traffic and browser extensions can also add measurable delay; test with them off to see. The rare case where a VPN helps is when your ISP's path to a service is unusually poor and the VPN's is better, which you can only know by testing both ways.

Check your equipment and settings

• Restart the modem and router if latency suddenly worsened; long-running consumer gear can degrade. If a restart fixes it repeatedly, the device may be failing.
• Use good cables. A damaged or very old Ethernet cable can cause errors and retransmissions.
• Reduce load on the device. A computer at 100 percent CPU or with a failing network adapter can add delay that looks like network latency.
• Close background apps that use the network, including cloud sync, streaming on other screens and updates.
• Disable unneeded router features such as heavy deep-packet inspection if you suspect they slow forwarding.
• Check for double NAT (two routers chained). It can add small delay and cause connection problems; see IP addresses, IPv4, IPv6 and NAT.

Does changing DNS reduce latency?

DNS turns names into addresses. A faster or closer resolver reduces the time of the lookup, which affects only the first connection to a name, and results are cached afterwards. It does not change the round-trip time once you are connected. Switching resolver is a small optimisation for page load, not a fix for high ping in a game. In rare cases a resolver can steer you to a CDN server farther away than necessary, so if a particular site is oddly slow, testing with a different resolver is reasonable.

Change the connection type or provider

Access technology sets a floor on your first-hop latency: fibre to the home typically adds a few milliseconds, cable and DSL often 5 to 20 ms, 4G and 5G commonly 20 to 60 ms depending on signal and load, and geostationary satellite roughly 500 ms or more because of the orbit height. Low Earth orbit satellite systems are lower than geostationary but generally higher and more variable than fibre. If you have a choice, fibre or a good cable line gives the best baseline. If your latency is high to many destinations even nearby ones, or spikes at the same time every evening, the cause may be on your provider's side. See talking to your ISP.

Worked examples

Example 1: Wi-Fi to cable

A player measures a 38 ms average to a regional server over Wi-Fi, with a worst pass of 140 ms. After switching to Ethernet, the average is 27 ms and the worst 41 ms. The average dropped 11 ms, but the biggest change is the spikes: the worst pass fell by about 100 ms, which is what removes visible stutter.

Example 2: bufferbloat

Idle ping to a nearby server is 18 ms. While a cloud backup uploads, it rises to 420 ms. After enabling SQM and setting the upload limit to about 90 percent of the line's real upload speed, ping during the upload is 35 ms. Idle latency did not change; the loaded latency improved by about 385 ms. The upload takes slightly longer, which is the trade.

Example 3: the fix that can't work

A user in Europe measures 190 ms to a server in Australia and wants 50 ms. Great-circle distance is roughly 15,000 km and real fibre paths are longer, so the physical floor is about 150 ms before any equipment delay. Nothing at home can reach 50 ms; the only option is a server in a nearer region. See undersea cables and the speed of light.

Common mistakes and myths

• "A faster plan will lower my ping." Only if your line is saturated; see latency vs bandwidth vs throughput.
• "Gaming routers and boosters guarantee lower ping." They can help with queuing on your own line. They cannot shorten the route beyond your router.
• "Changing DNS fixes lag." It affects name lookups, not round-trip time.
• Changing many things at once. You will not know what worked.
• Testing once. Latency fluctuates; compare several runs, and look at the worst pass as well as the average.
• Testing only while the line is idle. Problems like bufferbloat only show under load.
• Chasing an impossible number. Compare with what the distance allows; see what is a good latency.

What to do next

If you are not sure where the problem is, follow the step-by-step flow in troubleshoot high latency. If the evidence points at your provider, read talking to your ISP before you call. Use the free latency test before and after each change, and save the report link to compare. For use-case targets, see latency for gaming.