Bandwidth vs. Latency vs. Jitter, Explained

A broadband speed test may report hundreds of megabits per second, yet video calls still freeze, online games feel delayed and remote desktops respond sluggishly.

The connection may have plenty of bandwidth but poor latency, unstable jitter or packet loss.

These measurements describe different parts of network performance:

• Bandwidth is how much data the connection can carry.
• Latency is how long data takes to travel.
• Jitter is how much that travel time varies.
• Packet loss is data that never reaches its destination.

Understanding the difference helps you identify whether a problem needs faster broadband, better Wi-Fi, traffic management or a more reliable route to the service.

Bandwidth: How Much Data Can Be Carried

Bandwidth describes the capacity of a network connection. It is normally measured in:

• Megabits per second, or Mbps
• Gigabits per second, or Gbps

A 500 Mbps broadband service can theoretically carry more data each second than a 100 Mbps service.

Think of bandwidth as the number of lanes on a road. More lanes allow more vehicles to travel at the same time, but they do not guarantee that an individual vehicle reaches its destination quickly.

Bandwidth affects activities such as:

• Downloading large files
• Uploading cloud backups
• Streaming several videos simultaneously
• Transferring data to a server
• Supporting many active users
• Moving large files across a local network

The IETF distinguishes network capacity from the throughput an application actually achieves. Maximum capacity measurements and real-world throughput are related but not identical because performance is affected by congestion control, loss, delay and protocol overhead. 

Bandwidth Is Not the Same as Throughput

Bandwidth is the connection’s potential capacity. Throughput is the amount of useful data transferred successfully during a test or activity.

A Gigabit Ethernet connection has a nominal capacity of 1 Gbps, but a file transfer will normally report less because some capacity is consumed by:

• Ethernet and internet protocol headers
• Acknowledgements
• Error correction
• Encryption
• Retransmissions
• Application overhead
• Storage performance
• Congestion

Similarly, buying 1 Gbps broadband does not guarantee that every website will download at 1 Gbps. The remote server, internet route, Wi-Fi connection and receiving device must all support that rate.

Download and Upload Bandwidth Are Separate

Most consumer broadband packages provide different download and upload capacities.

Download bandwidth is used when receiving:

• Web pages
• Software
• Streaming video
• Cloud files
• Game downloads

Upload bandwidth is used when sending:

• Video-call footage
• Cloud backups
• Email attachments
• CCTV recordings
• Livestreams
• Files to business systems

A service described as 500 Mbps broadband might provide 500 Mbps download but a much smaller upload speed.

That can be enough for ordinary browsing but may become a problem when several people are on video calls while another device backs up photographs or security-camera footage.

How Much Bandwidth Do You Need?

The answer depends more on simultaneous activity than on the number of devices registered to the router.

Twenty idle smart-home devices may use very little capacity. Four people simultaneously streaming, gaming, downloading and joining video meetings may use considerably more.

Bandwidth demand can come from:

• Multiple 4K streams
• Large game downloads
• Cloud synchronisation
• Off-site backups
• High-resolution CCTV
• Remote working
• Software updates
• Large business file transfers

When the connection reaches capacity, packets begin to queue. That queuing can increase latency and jitter, making interactive services feel poor even before the download speed appears completely exhausted.

Latency: How Long Data Takes to Travel

Latency is the delay between data being sent and reaching its destination.

It is normally measured in milliseconds, abbreviated as ms.

Network latency may be measured as:

• One-way delay: the time from sender to receiver
• Round-trip time: the time for data to travel to the destination and for a response to return

Consumer speed tests usually report round-trip latency. The FCC similarly defines round-trip latency as the time required for a packet to travel from one point to another and back. 

Lower latency means a more responsive connection.

What Latency Feels Like

High latency can cause:

• A delay before websites begin loading
• Noticeable lag in online games
• People speaking over each other on calls
• Slow remote-desktop responses
• Delayed cloud applications
• Hesitation in voice assistants
• Slow terminal or server sessions
• Longer pauses during authentication

Latency is particularly important when an activity involves frequent exchanges of small messages.

A video stream can buffer several seconds of content in advance. A game cannot buffer your future actions, and a conversation becomes awkward when every response is delayed.

A High-Bandwidth Connection Can Still Have High Latency

Imagine two internet connections:

• Connection A: 1 Gbps with 80 ms latency
• Connection B: 100 Mbps with 10 ms latency

Connection A can transfer large files faster. Connection B may feel more responsive for gaming, browsing, voice calls and remote work.

Adding bandwidth does not make radio waves or fibre signals travel instantly. It also does not automatically shorten inefficient internet routes or eliminate queues in overloaded equipment.

Cisco defines low latency as a system or network responding with minimal delay, while noting that acceptable measurements depend on the application. 

What Causes Latency?

Every part of the route adds some delay.

Physical distance

Data travelling to a server in another continent takes longer than data travelling to a nearby server.

Even fibre cannot transmit information instantly. Long routes and undersea cables add unavoidable propagation delay.

Routing

The internet does not always use the geographically shortest path.

Traffic may travel through:

• Your internet provider
• Transit networks
• Peering exchanges
• Content-delivery networks
• Corporate security systems
• VPN gateways
• Cloud regions

Poor routing can add unnecessary distance and processing.

Queuing

When a router or connection is busy, packets wait in a queue before being transmitted.

This is one of the most common causes of latency increasing during heavy downloads or uploads.

Wi-Fi retransmissions

A weak or interfered-with Wi-Fi connection may repeatedly retransmit damaged or missed packets.

The connection can show reasonable signal bars while adding delay through retries.

Network equipment

Routers, firewalls, VPN appliances and security filters all process traffic. Underpowered or overloaded hardware may add substantial delay.

Mobile and satellite networks

Radio scheduling, signal conditions and network architecture can add latency.

Traditional geostationary satellite systems also involve extremely long physical paths. Low-Earth-orbit satellite systems reduce that distance but still have changing routes and wireless variability.

Idle Latency and Loaded Latency

A speed test may show excellent latency while the network is quiet but poor latency during a download.

These are different measurements.

Idle latency

The delay when little or no other traffic is using the connection.

Loaded latency

The delay while the connection is carrying substantial traffic.

A connection with 12 ms idle latency but 250 ms loaded latency can feel fine until somebody starts a large upload or download.

The increase is often caused by excessive queuing, commonly associated with bufferbloat.

What Is Bufferbloat?

Routers and network equipment use buffers to hold packets temporarily during congestion.

Some buffering is necessary. Excessive buffering allows long queues to form instead of dropping or managing traffic quickly.

The result can be:

• Fast downloads
• High speed-test figures
• Very slow gaming responses during downloads
• Poor calls while cloud backups run
• Delayed web browsing under load

Bufferbloat is a good example of why bandwidth alone does not describe connection quality.

Modern queue-management systems can keep queues shorter and share capacity more fairly between large downloads and interactive traffic.

Jitter: When Latency Keeps Changing

Jitter is the variation in packet delay over time.

Suppose voice packets experience these delays:

• Packet 1: 20 ms
• Packet 2: 22 ms
• Packet 3: 19 ms
• Packet 4: 85 ms
• Packet 5: 24 ms

The average latency may not look disastrous, but the sudden 85 ms delay disrupts the steady arrival pattern.

The IETF formally describes this as packet-delay variation and notes that the word “jitter” is commonly used for variations in network delay. 

Cisco similarly defines jitter as variation in packet latency and explains that excessive variation can degrade voice quality. 

What Jitter Feels Like

High jitter can cause:

• Robotic or distorted speech
• Brief gaps in audio
• Words arriving out of order
• Video-call freezes
• Erratic gaming movement
• Remote-desktop stuttering
• Livestream interruptions
• Unstable audio synchronisation

A steady 40 ms delay may be manageable. A delay constantly shifting between 10 ms and 150 ms is harder for real-time applications to handle.

Jitter Buffers Help, but Add Delay

Voice and video applications often use a jitter buffer.

The buffer waits briefly for packets and then plays them at a steadier rate. This can smooth out minor variations.

However, the buffer creates a trade-off:

• A larger buffer handles greater variation.
• A larger buffer also adds more latency.

When jitter becomes too severe, the application may not be able to wait long enough without making the conversation uncomfortably delayed.

Packets arriving too late may simply be discarded.

What Causes Jitter?

Jitter can result from:

• Changing network congestion
• Wi-Fi interference
• Weak wireless signals
• Variable mobile coverage
• Router queues
• Competing uploads
• Overloaded VPN servers
• Traffic taking different routes
• Faulty equipment
• Wireless mesh backhaul
• Inconsistent powerline networking

A connection can have a good average ping while still delivering poor calls because individual packet delays vary widely.

Packet Loss: The Fourth Measurement

Packet loss occurs when packets do not reach their destination.

Packets may be dropped because of:

• Congestion
• Weak Wi-Fi
• Radio interference
• Faulty cables
• Damaged network hardware
• Provider faults
• Overloaded routers
• Routing problems
• Security filtering
• Buffer overflows

Real-time applications are particularly sensitive to loss because there may not be enough time to retransmit missing information.

The IETF identifies loss, latency, jitter and bandwidth as separate measurements used to assess network performance. 

What Packet Loss Feels Like

Packet loss can cause:

• Missing words on calls
• Blocky video
• Freezing
• Online-game teleporting
• Failed downloads
• Slow file transfers
• Repeated page loading
• VPN disconnections
• Remote-desktop pauses

Reliable protocols such as TCP retransmit missing packets, preventing silent data corruption but reducing throughput and adding delay.

Real-time voice and video often prioritise timeliness. A missing voice packet may be concealed or skipped rather than resent after it is useful.

A Road Analogy

The three main measurements can be visualised as a road system.

Bandwidth: number of lanes

More lanes allow more vehicles to travel simultaneously.

Latency: journey time

The time one vehicle needs to reach the destination.

Jitter: inconsistent journey time

One vehicle arrives in ten minutes, the next in twelve and another in thirty.

Packet loss: vehicles that never arrive

Some vehicles are lost before reaching the destination.

Widening the road helps when too many vehicles are competing for space. It does not necessarily shorten the route, stabilise traffic flow or recover vehicles that disappear.

Which Measurement Matters Most?

The answer depends on the activity.

Large file downloads

Most affected by:

1. Available bandwidth
2. Packet loss
3. Latency

High latency can reduce the efficiency of some transfers, particularly over long-distance connections, but capacity is normally the most visible factor.

Web browsing

Most affected by:

1. Latency
2. Packet loss
3. Bandwidth

Many web pages require numerous small requests. A modest but low-latency connection can feel faster than a high-capacity connection with large delays.

Video streaming

Most affected by:

1. Sufficient bandwidth
2. Packet loss
3. Connection stability
4. Jitter and latency

Streaming applications use buffering, so they can tolerate more latency than live calls.

Video conferencing

Most affected by:

1. Latency
2. Jitter
3. Packet loss
4. Sufficient upload and download bandwidth

Video calls do not normally require enormous capacity, but they require packets to arrive reliably and at the right time.

Online gaming

Most affected by:

1. Latency
2. Jitter
3. Packet loss
4. Bandwidth

Most games use relatively little bandwidth during play. Downloading the game may require hundreds of gigabytes, but playing it usually depends more heavily on responsiveness and consistency.

Cloud gaming

Most affected by all four:

• Consistent bandwidth for the video stream
• Low latency for controller input
• Low jitter
• Very low packet loss

Voice calls

Most affected by:

1. Jitter
2. Packet loss
3. Latency
4. Modest bandwidth

Voice calls consume relatively little capacity but are extremely sensitive to unstable delivery.

Remote desktop

Most affected by:

1. Latency
2. Jitter
3. Packet loss
4. Enough bandwidth for the screen content

High latency makes every click and keystroke feel delayed.

Why Gaming Does Not Need Gigabit Bandwidth

Online games exchange relatively small updates about:

• Player position
• Inputs
• Events
• Game state
• Voice chat

The large bandwidth demand usually comes from downloading or updating the game, not the live match.

A stable 50 Mbps connection with low latency can provide better gameplay than a congested Gigabit connection with erratic delays.

This is why upgrading from 500 Mbps to 1 Gbps may cut a download time but make no noticeable difference to ping.

Why Video Calls Fail During Uploads

Many broadband services have much less upload capacity than download capacity.

A cloud backup, CCTV system or file upload may saturate the upstream connection. Other packets—including voice and video-call traffic—then wait behind the upload.

Symptoms include:

• Others cannot hear you properly.
• Your video becomes blocky.
• Call latency rises.
• Download tests still look acceptable.
• Problems disappear when the upload stops.

Traffic management, upload limits or a service with greater upstream bandwidth may solve the problem.

Why Wi-Fi Can Have Good Bandwidth but Poor Jitter

A Wi-Fi speed test may show hundreds of megabits per second, but interference can still cause individual packets to be retransmitted unpredictably.

Potential causes include:

• Neighbouring Wi-Fi
• Thick walls
• Mesh nodes using weak wireless backhaul
• Microwave interference
• Bluetooth congestion
• Devices moving between access points
• Poor router placement
• Hidden-node problems
• Busy channels

Ethernet generally provides more consistent delay because it avoids shared radio airtime and most household interference.

Bandwidth on Your Local Network

Your internet package is only one possible bottleneck.

The path may include:

• Broadband line
• Provider router
• Ethernet switch
• Wi-Fi access point
• Client device
• Remote server

A 1 Gbps internet service cannot deliver its full speed through:

• A 100 Mbps Ethernet port
• A slow powerline adapter
• A congested Wi-Fi extender
• An old laptop radio
• A weak mesh backhaul

Similarly, a local NAS transfer can be fast even when the internet is down because it stays inside your home or business network.

How to Measure Bandwidth

Use a speed test under controlled conditions.

For the most useful baseline:

1. Connect a capable computer directly to the router by Ethernet.
2. Stop large downloads and backups.
3. Disable the VPN temporarily where permitted.
4. Use a reputable test service.
5. Test several times.
6. Compare download and upload results.
7. Repeat at different times of day.

Then run the same test over Wi-Fi.

When Ethernet is fast but Wi-Fi is slow, investigate the local wireless network. When both are slow, investigate the broadband service or router.

How to Measure Latency

The ping tool sends a request and measures the round-trip response time.

Example on Windows:

ping 1.1.1.1

Example on macOS or Linux:

ping -c 20 1.1.1.1

Look at:

• Minimum time
• Average time
• Maximum time
• Packet loss

Test more than one destination. A high delay to one server may reflect that route or server rather than the entire connection.

A ping to the router checks the local network. A ping to an internet destination includes the provider and wider route.

How to Measure Jitter

Many speed-test and video-call diagnostic tools report jitter directly.

You can also look at the variation between repeated ping results.

For example:

11 ms

12 ms

10 ms

13 ms

95 ms

12 ms

The average may still appear reasonable, but the 95 ms spike suggests unstable delay.

Basic ping variation is not identical to every formal jitter measurement, but it is useful for practical troubleshooting.

Test Under Load

A network can appear perfect while idle.

Run a continuous ping while starting a large download or upload.

On Windows:

ping -t 1.1.1.1

On macOS or Linux:

ping 1.1.1.1

Observe whether latency rises dramatically.

When idle results are 15 ms but loaded results climb into hundreds of milliseconds, congestion or excessive queuing is likely.

Stop the test with Ctrl+C.

Ping the Router First

Testing the router helps separate local problems from internet problems.

The router’s address is commonly something such as:

192.168.1.1

or:

192.168.0.1

When pinging the router over Ethernet produces stable sub-millisecond or low-millisecond responses but internet latency is high, the problem is probably outside the local wired network.

When Wi-Fi pings to the router fluctuate or lose packets, investigate:

• Signal strength
• Interference
• Access-point placement
• Wireless drivers
• Mesh backhaul
• Client hardware

Why a Nearby Speed-Test Server Can Be Misleading

Speed tests often select a nearby server to measure the best performance available through your provider.

That is useful for checking the broadband line, but it does not reproduce the route to:

• A distant game server
• A company VPN
• An overseas cloud platform
• A particular video service
• A remote data centre

Test the actual service where possible.

A low speed-test ping does not guarantee low latency to every destination.

What Is a Good Result?

There is no universal threshold because applications have different tolerances.

As a broad practical guide:

Latency

• Under 20 ms: excellent for many interactive uses
• 20–50 ms: generally good
• 50–100 ms: noticeable in sensitive applications
• Above 100 ms: increasingly disruptive for gaming and conversation
• Above 200 ms: clearly delayed

Jitter

• Under 10 ms: generally stable
• 10–30 ms: may be acceptable depending on the application
• Above 30 ms: real-time quality may begin to suffer
• Large recurring spikes: likely to cause disruption

Packet loss

• 0%: ideal
• Occasional isolated loss: may go unnoticed
• Around 1% or persistent loss: potentially disruptive
• Several percent: serious for calls, gaming and reliable transfers

These are practical guidelines rather than universal service guarantees. Measurement method, duration and application behaviour all matter.

How to Improve Bandwidth

When the connection genuinely lacks capacity:

• Upgrade the broadband package.
• Choose a service with better upload speed.
• Replace 100 Mbps network hardware.
• Use modern Ethernet switches.
• Improve Wi-Fi coverage.
• Use faster client devices.
• Connect fixed equipment by Ethernet.
• Schedule large backups outside working hours.
• Limit unnecessary cloud synchronisation.
• Check that the remote service is not the bottleneck.

Do not upgrade bandwidth before confirming that the current connection is actually being saturated.

How to Reduce Latency

To improve latency:

• Use Ethernet for gaming and workstations.
• Move closer to the access point.
• Improve router or access-point placement.
• Avoid weak mesh backhaul.
• Choose a nearby game or cloud region.
• Disable unnecessary VPN routing.
• Replace overloaded network hardware.
• Use effective queue management.
• Stop saturating the upload connection.
• Investigate poor provider routing.
• Avoid multiple wireless repeater hops.

Physical distance cannot be eliminated, but unnecessary local delays often can.

How to Reduce Jitter

To stabilise packet timing:

• Use Ethernet.
• Improve Wi-Fi signal strength.
• Change congested Wi-Fi channels.
• Add wired access points.
• Move mesh nodes closer together.
• Remove faulty powerline links.
• Stop large competing uploads.
• Apply traffic prioritisation.
• Replace unstable routers or switches.
• Test without a VPN.
• Investigate mobile-signal quality.
• Check cables and connectors.

The objective is consistency, not merely a lower average measurement.

How to Reduce Packet Loss

Start by finding where the loss occurs.

• Test the router over Ethernet.
• Test the router over Wi-Fi.
• Test an internet destination.
• Replace suspect Ethernet cables.
• Reposition wireless equipment.
• Update network drivers.
• Restart or replace unstable hardware.
• Check router logs.
• Contact the internet provider when loss begins beyond your network.

Do not accept persistent packet loss as a normal feature of fast broadband.

Can Quality of Service Help?

Quality of Service, or QoS, allows network equipment to prioritise certain traffic.

It can help protect:

• Voice calls
• Video meetings
• Gaming
• Remote desktop
• Business applications

from large downloads and backups.

QoS does not create additional bandwidth. It decides which traffic receives priority when capacity is limited.

Poorly configured QoS can reduce performance, so avoid entering arbitrary speed figures or prioritising every device as “highest.”

Modern queue-management systems often provide a better default approach than manually creating dozens of application rules.

When More Bandwidth Will Help

A faster package is likely to help when:

• The connection remains close to full utilisation.
• Several users stream or download simultaneously.
• Upload bandwidth is regularly exhausted.
• Large transfers take too long.
• The router and devices can handle the higher speed.
• Latency rises because the line is constantly saturated.
• Business activity has outgrown the current service.

When More Bandwidth Will Not Help

An upgrade may make little difference when:

• Gaming ping is high because the server is distant.
• Wi-Fi is weak in one room.
• Jitter comes from interference.
• Packet loss comes from a damaged cable.
• A VPN takes an inefficient route.
• The router is overloaded.
• A mesh node has poor backhaul.
• The remote service is slow.
• The current connection is rarely near capacity.

Fix the real bottleneck rather than purchasing a larger number.

A Practical Troubleshooting Order

When the internet feels slow or unstable:

1. Connect a computer to the router using Ethernet.
2. Test download and upload bandwidth.
3. Measure idle latency.
4. Run a latency test during a download and upload.
5. Check jitter and packet loss.
6. Ping the router over Ethernet.
7. Repeat the router test over Wi-Fi.
8. Test the actual affected service.
9. Stop backups, VPNs and large transfers temporarily.
10. Check router placement and wireless coverage.
11. Inspect cables and network equipment.
12. Contact the provider with recorded results.

This approach identifies whether the problem is capacity, responsiveness, consistency or reliability.

The Measurements Work Together

Bandwidth, latency and jitter are not competing ways of measuring the same thing.

A good connection needs an appropriate balance:

• Enough bandwidth for the workload
• Low enough latency for responsive applications
• Stable enough delay to prevent jitter
• Minimal packet loss

A connection can be excellent in one area and poor in another.

The best broadband package is not always the one with the highest headline speed. For gaming, voice, remote working and cloud applications, stable delivery can matter more than maximum throughput.

Hamilton Group can diagnose broadband, Wi-Fi, latency, jitter and packet-loss problems and design reliable networks for homes and businesses.

Call 0330 043 0069 or visit hgmssp.com to speak with one of our experts.