Understanding Network Latency: What Affects Your Connection Speed

By PingTester · August 10, 2026 · 7 min read

When a video call freezes, an online match stutters, or a remote desktop session feels sluggish, the culprit is almost always the same: network latency. Latency is the time it takes for a packet of data to travel from your device to a destination and back. We measure it in milliseconds, but the consequences ripple across everything you do online.

This article breaks down what latency actually is, the four components that make it up, and the practical levers you can pull to reduce it.

What Is Network Latency?

Network latency is the round-trip time (RTT) for a data packet to travel from a source to a destination and for an acknowledgement to come back. It is commonly reported by the ping utility as the time= field, expressed in milliseconds. Latency is distinct from bandwidth — bandwidth is how much data you can push through the pipe per second; latency is how long each chunk takes to arrive.

A connection with high bandwidth but high latency will still feel slow for interactive use: file downloads finish quickly, but every click, keystroke, and packet exchange incurs a perceptible delay. For real-time applications — voice, gaming, remote shells — latency matters more than raw throughput.

The 4 Components of Latency

Total latency is the sum of four distinct delays, each occurring at a different point in the packet's journey:

Propagation Delay

Propagation delay is the time it takes for a signal to physically travel through the medium (fiber, copper, air) between two points. It is bounded by the speed of light in that medium and the distance the signal must cover. This is the irreducible floor of latency — no routing optimization can beat physics.

Transmission Delay

Transmission delay is the time needed to push all of a packet's bits onto the link. It equals the packet size divided by the link bandwidth. A 1500-byte packet on a 1 Gbps link transmits in roughly 12 microseconds; the same packet on a 1 Mbps link takes about 12 milliseconds. On modern broadband, transmission delay is usually negligible compared to other components.

Processing Delay

Processing delay is the time each router or switch takes to read the packet header, run checksums, consult its forwarding table, and decide where to send the packet next. Modern hardware does this in microseconds, but it accumulates across every hop in the path.

Queuing Delay

Queuing delay is the time a packet spends waiting in a buffer because the outgoing link is busy. This is the most variable component of latency and the one most affected by network congestion. Under light load, queuing delay is near zero; under heavy load, it can spike to hundreds of milliseconds and is a leading cause of jitter.

How Geographic Distance Affects Ping

Distance is the single most predictable contributor to latency because propagation delay is fixed by the speed of light in the transmission medium. Light travels through vacuum at about 300,000 km/s, but through fiber optic cable it moves at roughly two-thirds of that speed. According to research compiled by grahammiranda.com, fiber optic signals travel at roughly two-thirds the speed of light, adding approximately 1ms of latency per 200km.

This is why a user in New York pinging a server in Tokyo will see a baseline latency of around 70-80ms before any routing overhead — they are limited by the physical distance and the speed of light in the undersea cables connecting the two continents. You cannot optimize away the speed of light; the only mitigation is to move the server closer to the user, which is the foundation of content delivery networks (CDNs) and edge computing.

Practical rule of thumb: every 100km of fiber between you and your destination adds about 0.5ms one-way, or 1ms round-trip. Cross-continental paths routinely add 40-60ms of unavoidable propagation delay, and intercontinental paths add 100ms or more.

Network Hops and Routing

Every router a packet passes through is a "hop." Each hop adds processing delay and may add queuing delay if the router is busy. The more hops between you and your destination, the more latency accumulates — and the more opportunities there are for congestion or path suboptimality to inflate the round-trip time.

Routing is rarely a straight line. Packets follow the paths that border gateway protocol (BGP) and interior routing protocols determine, which are optimized for cost, policy, and stability — not necessarily for lowest latency. A packet from Los Angeles to San Francisco might detour through Seattle if a peer's routing table prefers that path. Tools like traceroute and mtr expose the actual hop-by-hop path so you can see where latency enters your connection. For a deeper dive, see our guide on diagnosing packet loss, which uses these tools to locate where delay and loss occur.

Bandwidth vs Latency: The Common Misconception

People often assume a "faster" internet connection means lower latency. It usually does not. Bandwidth upgrades — going from 100 Mbps to 1 Gbps, for example — improve throughput, the volume of data you can transfer per second. They do almost nothing for latency, because propagation delay and hop count are unaffected by how wide the pipe is.

This is why a household on a 1 Gbps fiber plan can still experience lag in online games while another on a 50 Mbps plan with a shorter, less-congested path plays smoothly. If your use case is interactive — gaming, voice, remote desktop, SSH — chase latency first. If your use case is bulk transfer — downloading large files, backups, video streaming of buffered content — chase bandwidth first.

Hardware Factors: Routers, Cables, WiFi vs Ethernet

Hardware choices at home introduce their own latency, sometimes dramatically.

• Router quality. Cheap consumer routers often have underpowered CPUs that add measurable processing delay, especially when many devices are active. A router that overheats or runs old firmware can also introduce packet jitter.
• Cable type. Cat5e, Cat6, and fiber all support low-latency transmission. Damaged or low-quality cables can cause retransmissions that compound latency. For short runs inside a home, the cable type rarely dominates latency.
• WiFi vs Ethernet. Ethernet adds 1-3ms of consistent latency. WiFi typically adds 5-20ms, and that latency varies packet-to-packet because the wireless medium is shared and contention-based. WiFi also retransmits packets that fail due to interference, multiplying latency during congestion. For latency-sensitive work, a wired Ethernet connection is the single most effective hardware change you can make.

Practical Ways to Reduce Latency

Once you understand the components, the levers for reducing latency become obvious:

1. Use a wired connection. Switching from WiFi to Ethernet removes wireless contention and retransmission latency. This is the highest-impact change for most home users.
2. Choose closer servers. In multiplayer games, voice apps, and cloud services, pick the region geographically nearest to you. Halving the distance halves the propagation delay.
3. Enable QoS on your router. Quality of Service settings prioritize latency-sensitive traffic (gaming, voice) over bulk traffic (downloads, backups) so a large file transfer does not inflate your ping.
4. Upgrade aging routers. A modern router with a faster CPU and up-to-date firmware can shave milliseconds off processing and queuing delay under load.
5. Reduce hop count when possible. If you operate your own infrastructure, peering directly with networks you exchange traffic with removes intermediate hops and lowers RTT.
6. Use a CDN or edge platform. For delivering content to users, serving from edge nodes close to them eliminates the bulk of distance-induced latency.

For step-by-step instructions on running a ping test to measure these improvements, see our beginner's guide to running a ping test. To compare how transport protocol choice affects the latency you measure, our TCP vs UDP latency comparison covers the protocol-level differences.

Summary

Network latency is the round-trip time for a data packet, and it is the sum of four components: propagation, transmission, processing, and queuing delay. Distance sets the floor through propagation delay; hops and routing add processing and queuing delay on top; and your local hardware — especially WiFi versus Ethernet — can add significant variable latency. Bandwidth upgrades rarely help interactive performance; reducing physical distance, hop count, and local contention does. Measure first with ping and traceroute, then attack the component that dominates your numbers.