Latency is the delay between sending data and receiving it, and even a small pause can make a network feel sluggish. Learn how propagation, transmission, processing, and queuing contribute to latency—and how it differs from throughput, bandwidth, and jitter in gaming, VoIP, and real-time systems.

Multiple Choice

_____ refers to the time lapse between data being sent and received, and it can have a significant impact on performance.

Latency is the time delay between when data is sent and when it is received, incorporating propagation, transmission, processing, and queuing delays. This delay directly affects how quickly a system can respond, which is why it has a big impact on performance—especially for interactive applications like gaming, VoIP, or real-time control, where even small delays can feel sluggish. Latency is different from throughput, which measures how much data can be transferred per unit time, and from bandwidth, which is the maximum data rate of the channel. Jitter, meanwhile, refers to the variation in latency over time, which can cause inconsistent performance.

What Is Network Latency, and Why Does It Matter?

When you tap a video call button, open a web page, or move a character in an online game, you expect a quick response. The time between sending a request and receiving a reply is called latency. It may last only a fraction of a second, but that small delay can shape how fast and smooth a computer system feels.

Latency matters anywhere data travels between devices. That includes a home Wi-Fi network, a company server, a cloud service, or a connection between two computers in the same room. Understanding it helps explain why a connection can feel slow even when it seems to have plenty of capacity.

Latency is about waiting

A simple way to think about latency is the time it takes for a message to make a round trip. Your device sends a request; another device receives and processes it; then a reply comes back. The delay across that journey is often measured in milliseconds, or thousandths of a second.

Say you click a link. Your computer asks a web server for a page, and the server sends the requested data back. If the round-trip latency is low, the page can begin responding quickly. If latency is high, there may be a noticeable pause before anything happens.

Network engineers often use ping to measure round-trip time. The ping tool sends a small packet to another device and records how long the reply takes. It’s a useful first check, though it doesn’t tell the whole story: a quick ping won’t guarantee that every app or download will feel fast.

Four delays can add up

Latency isn’t caused by just one thing. Several kinds of delay can build on one another as data moves through a network.

  • Propagation delay is the time a signal takes to travel through a medium, such as a fiber-optic cable or radio link. Distance matters here. A server across the country will usually take longer to reach than a nearby one.

  • Transmission delay is the time needed to put data onto the connection. A large packet takes longer to send than a small one, particularly on a link with a lower data rate.

  • Processing delay is the time a router, switch, server, or computer needs to inspect and handle the data.

  • Queuing delay occurs when packets have to wait their turn. If a router is busy or a connection is crowded, that wait can grow.

Imagine driving across town. The distance is like propagation delay; loading the car is a bit like transmission; checking directions resembles processing; and sitting at a busy intersection feels like queuing. Even if each delay seems small, the combined trip can take longer than expected.

Latency, bandwidth, and throughput aren’t the same

These terms often appear together, but they describe different parts of network performance.

Bandwidth is the maximum amount of data a connection can carry in a given period. Picture a road: more lanes allow more cars to pass at once. A high-bandwidth connection can carry a large volume of data, but that doesn’t mean each request will receive a reply right away.

Throughput is the amount of data actually transferred over time. It can be lower than the connection’s stated bandwidth because of congestion, interference, equipment limits, or other conditions.

Latency, by contrast, is about delay. A connection can have high bandwidth and still feel sluggish if each request takes a long time to reach its destination and return. Think of a wide highway with a distant destination: lots of traffic can move along the road, yet the first car still has a journey ahead of it.

This is why a large file download and a video call can behave differently on the same network. A download can often keep going as packets arrive, while a call depends on quick, steady delivery.

Why interactive apps notice every pause

Some activities can tolerate a delay. If a document takes an extra moment to download, it may be mildly annoying, but it usually remains usable. Other tasks depend on immediate responses.

In an online game, a player’s movement must travel to a server and back. With high latency, an action may appear late on screen. The character might keep moving after the player has released a control, or another player may seem to jump from one spot to another.

Voice and video calls are sensitive, too. When latency is high, people may talk over each other because each person hears the other’s words late. A brief delay can feel awkward; a longer one makes conversation harder to follow. Remote equipment control can have even greater demands, since a delayed response may affect how safely someone can guide a machine.

The exact impact depends on the task. A few extra milliseconds may go unnoticed when browsing a news site, yet feel significant during fast gameplay or a live conversation. Context matters.

Jitter: when delay keeps changing

A steady delay is not always ideal, but changing delay can be just as disruptive. Jitter is the variation in latency over time.

Suppose voice packets usually arrive after 40 milliseconds, but some arrive in 40 milliseconds and others in 180. The average might not look terrible, yet the uneven timing can make speech sound choppy. Apps often use a buffer to smooth out these differences. That can improve playback, but it may add some delay of its own.

So latency and jitter are related, but they aren’t interchangeable. Latency describes how long data takes to travel. Jitter describes how much that travel time varies. A road trip with a predictable 30-minute drive is different from one that takes anywhere from 20 to 60 minutes, even if the average is similar.

What can raise latency?

A faraway server is one common cause. Data must travel through physical links, and even signals moving close to the speed of light need time to cover long distances. Network routes can also take indirect paths, depending on how providers connect their systems.

Congestion is another factor. When many devices send data through the same link, packets may have to wait in queues. This can happen on a busy office network, in a crowded public Wi-Fi area, or on a home connection when several people stream, download, and play games at once.

Wireless conditions matter as well. Walls, interference from nearby networks, and distance from a Wi-Fi router can all affect how reliably data moves. Older or overloaded equipment may add processing delays, too. And sometimes the delay sits beyond the local network—in the internet service provider’s network or at the server itself.

How to check and reduce it

A basic way to inspect latency is to run a ping test to a known destination. Compare several results, not just one. If the numbers jump around, jitter or congestion may be involved. A traceroute tool can show the path packets take and where delays may begin, though each network device may respond differently, so one slow-looking point doesn’t always prove that it is the cause.

For a home network, a few simple steps can help:

  • Move closer to the Wi-Fi router, or connect with an Ethernet cable when a stable link matters.

  • Pause large uploads or downloads during a video call or online game.

  • Restart older network equipment if it has been running for a long time.

  • Choose a nearby service region when an app or game allows it.

  • Check whether the delay appears on one device, one app, or the whole network.

These steps won’t fix every source of latency. If the delay remains high across different devices and services, the issue may lie with the internet connection or the route to a remote server. A service provider can help investigate that part.

Fast connections need more than speed

A reliable network isn’t defined by one number. Bandwidth tells you how much data a link can carry; throughput shows how much it is carrying in real conditions; latency tells you how long a response takes; and jitter shows whether that delay stays consistent.

Together, these measures paint a clearer picture. For everyday browsing, small changes in latency may barely register. For gaming, calls, and real-time control, a short wait can change the whole experience. Once you know what latency is—and how it differs from its close companions—network performance becomes easier to understand, troubleshoot, and explain.