What Is an Acceptable Jitter Level in a Speed Test?

What Jitter Means in a Speed Test

Jitter is the variation between successive packet delivery times. A stable connection delivers packets at nearly regular intervals, while a connection with high jitter delivers them unevenly. Speed tests may report jitter in milliseconds, often alongside latency, download speed, upload speed, and packet loss.

As a general guide, jitter below 5 ms is excellent for real-time traffic, 5 to 20 ms is usually acceptable, and values above 20 to 30 ms may cause noticeable problems in calls or online games. These ranges are practical guidelines rather than universal limits. The impact depends on the application, server distance, latency, and packet loss.

How High Jitter Appears to Users

High jitter can make a voice or video call sound choppy, create interruptions, or cause the picture to freeze briefly. In online games, it may appear as inconsistent movement, delayed actions, or sudden position changes. Streaming services can often hide moderate jitter by buffering, so a high jitter result may exist even when a video plays normally.

A normal download result does not rule out jitter. Download speed measures capacity, while jitter measures timing consistency. A connection can have high capacity but unstable packet delivery during busy periods.

Common Causes of High Jitter

Wi-Fi interference and weak signal

Wi-Fi interference from nearby routers, Bluetooth devices, appliances, thick walls, or overlapping channels can force packets to wait or be retransmitted. A weak signal can create similar timing variation, especially when the device is far from the router. Testing over Ethernet helps determine whether Wi-Fi is the main cause.

Network congestion

Congestion occurs when the available connection or a shared network segment is handling more traffic than it can process smoothly. Multiple downloads, cloud backups, video streams, and uploads can fill queues in the router or broadband network. Jitter often becomes worse during evening peak hours or whenever the connection is heavily used.

Background uploads and downloads

Automatic updates, file synchronization, security scans, cameras, and other connected devices can consume bandwidth without obvious activity on the test device. Upload saturation is particularly important because a full upload queue can delay acknowledgements and interactive traffic, increasing latency and jitter.

Router or modem limitations

An outdated router, overloaded modem, or device with weak traffic management may introduce queueing delays. Problems are more likely when several devices use high-bandwidth services at the same time. Firmware issues, overheating, or an unsuitable router configuration can also make packet timing less consistent.

Unstable cable, fiber, or wireless broadband service

Signal faults, damaged wiring, loose connectors, optical issues, or radio interference on a fixed wireless service can cause retransmissions and variable delivery times. If jitter remains high on a wired connection with local traffic stopped, the issue may be beyond the home network and should be discussed with the ISP.

Test server distance and routing

A speed test server in another city or region may use a longer and more complex route. Different routes can produce different latency and jitter results, so one test is not enough to diagnose a line. A distant server does not always indicate a fault with your broadband service.

How to Judge an Acceptable Jitter Result

Interpret jitter together with latency, packet loss, and the type of service you use. A practical reference is:

• Below 5 ms: excellent consistency for calls, gaming, and other real-time traffic.
• 5 to 20 ms: generally acceptable for most broadband users.
• 20 to 30 ms: potentially noticeable in sensitive applications.
• Above 30 ms: more likely to cause interruptions, especially when combined with high latency or packet loss.

These figures are not a service guarantee. Consistency matters more than a single low reading, and application tolerance varies. A stable 15 ms result may feel better than a result that changes repeatedly between 2 ms and 50 ms.

How to Test Jitter Accurately

1. Connect the test device to the router with an Ethernet cable if possible.
2. Pause downloads, uploads, cloud synchronization, streaming, and VPN connections.
3. Run several tests at different times, including a quiet period and a busy period.
4. Use a nearby test server first, then compare results with another reputable server.
5. Record jitter, latency, packet loss, download speed, upload speed, and the connection type.

You can use a broadband test such as Speedtest.im to compare results over time. If jitter is high only on Wi-Fi, test from different rooms and bands. If it is high on Ethernet as well, continue with router and ISP checks.

Ways to Reduce Jitter

• Move closer to the router or use a wired Ethernet connection for calls and gaming.
• Place the router in an open, central location and select a less congested Wi-Fi channel.
• Use the 5 GHz or 6 GHz Wi-Fi band when the device is nearby and supported.
• Pause large uploads, backups, and downloads during real-time activities.
• Enable smart queue management or quality of service if the router supports a reliable configuration.
• Restart and update the router and modem, and check for overheating or damaged cables.
• Compare jitter at different times to identify peak-hour congestion.
• Contact the ISP if high jitter continues on Ethernet with no local traffic, especially when packet loss or service drops are also present.

When High Jitter Requires ISP Support

Contact the ISP when repeated wired tests show high jitter, packet loss, or large changes in latency across multiple nearby servers. Provide test times, connection type, router status, and whether the issue affects all devices. This information helps distinguish a home Wi-Fi problem from a fault involving the modem, access network, routing, or broader service congestion.