How to Reduce Jitter on WiFi and Internet

By Paul Snyman · Published August 28, 2026 · 9 min read

Jitter is the reason a call breaks up on a connection that passes a speed test. Your download number is fine, your ping looks fine, and yet voices stutter and the game rubber-bands. Speed is not the problem. Consistency is.

This is a practical guide: how to measure jitter on a phone, which fixes actually work, and how to tell whether a change helped rather than guessing.

What jitter is, briefly

Latency is how long one packet takes to make the round trip. Jitter is how much that time varies from packet to packet.

A connection averaging 30 ms where every packet lands between 28 and 32 ms feels excellent. A connection averaging the same 30 ms where packets land anywhere between 5 and 200 ms feels broken, because anything real-time has to buffer for the worst case or drop what arrives late. Same average, completely different experience.

That is why a speed test can look healthy while calls fall apart. A speed test measures how much data you can move. It says almost nothing about arrival consistency.

How to measure jitter on an iPhone

Being precise about this, because most tools do not report jitter and the ones that do are not always clear about what they measured.

In PingKit, jitter comes from Connection Monitor. It pings once a second and reports the average difference between each result and the one before it, alongside latency, packet loss and a stability score. That consecutive-difference figure is the number to watch.

Two limits worth knowing up front, because they change how you use it:

• It runs while the screen is on and the app is open. iOS does not let a network tool keep pinging in the background, so this is a live test you watch, not a recorder you leave running overnight.
• It keeps a rolling window of the last 60 seconds. Each new second pushes the oldest one out, and starting a fresh session clears the history. It shows you the connection's behaviour right now.

If you want a rough read without watching a live monitor, a Ping Test gives you minimum, average and maximum. The gap between minimum and maximum is a serviceable proxy: a 12 ms minimum against a 240 ms maximum is a jitter problem even without a jitter figure attached.

One thing not to rely on: PingKit's Speed Test does not report jitter. Use Connection Monitor for that.

Find out where the jitter starts

This step saves the most time, and most guides skip it. Jitter on your own WiFi and jitter out on the internet have completely different fixes, and it takes about two minutes to tell them apart.

1. Ping your router. Run a Ping Test against your gateway address. This traffic never leaves your home. If it is already erratic, the problem is local: WiFi, the router, or something on your network.
2. Ping something on the internet. Try 1.1.1.1 or 8.8.8.8. If your router was steady but this is not, the problem is upstream, at your ISP or beyond.
3. Test on cellular. Turn WiFi off and repeat. If jitter disappears, it is your WiFi or router. If it persists, it is not your home network at all.

If it points upstream, Traceroute shows the path your traffic takes and the latency at each hop, which tells you how far the problem is from your house.

Fixes for local jitter

Ordered by how often they work, in my experience.

1. Move closer, or remove what is in the way

Weak WiFi causes retransmissions, and retransmissions are jitter. Concrete walls, foil-backed insulation, metal appliances and floors between you and the router all cost signal. Test from a room where things work, then from the problem room. If the difference is dramatic, coverage is your problem and no router setting will fix it. A mesh node or a relocated router will.

2. Get off the crowded band

2.4 GHz reaches further but is shared with microwaves, cordless phones, baby monitors, Bluetooth and every neighbour. 5 GHz carries less far and is usually far quieter. If your router publishes both under one name, try splitting them and joining the 5 GHz network directly from the problem room.

Worth knowing: no iPhone app can tell you which band or channel you are on. iOS does not expose it. Check the router's admin page or the manufacturer's app. I wrote up what iOS does and does not allow here.

3. Find out what else is on your network

One device saturating the connection makes everything else jittery. A console downloading an update, a cloud backup mid-sync, or a camera uploading continuously will do it. Run a LAN Scanner to see what is actually connected. People routinely find more devices than they expected.

4. Turn on QoS or Smart Queue Management

This is the fix most people have never tried and it is often the biggest single win. Bufferbloat is what happens when your router queues packets during heavy traffic instead of dropping them, and latency balloons under load. Look for Smart Queue Management, SQM, or QoS in your router settings. On routers that support it properly, this can take jitter under load from 200 ms to under 20 ms.

5. Use a cable where it matters

Unglamorous, and it works. A desktop, console or streaming box on Ethernet takes itself off the WiFi entirely, which helps that device and frees the air for everything else.

6. Restart the router, properly

Last because it is the first thing everyone tries. Power off for a full 30 seconds, not a quick cycle. If this fixes it and the problem returns within days, the router is struggling and the real fix is replacement.

Fixes when the jitter is upstream

Less within your control, but not nothing.

• Check whether it is time-of-day. Congestion on a shared line has a schedule, usually evenings. Test at 3pm and again at 9pm.
• Test the modem directly. If your modem and router are separate, connecting a computer straight to the modem removes your router from the picture entirely.
• Collect evidence before calling. "The internet is bad" gets nowhere. A record of jitter and packet loss figures, at specific times, repeated over several days, is much harder to dismiss. PingKit keeps unlimited history and exports to CSV, JSON or PDF for free.
• Ask about the line, not the speed. On cable, high jitter with packet loss often means a signal-level problem on the line. Ask them to check upstream power and signal-to-noise rather than accepting a speed test as proof everything is fine.

Confirm the fix actually worked

Every change above is worth measuring rather than assuming, because several of them feel like they helped when they did nothing.

1. Before you change anything, open Connection Monitor in the problem spot and let it run a minute. Note the jitter and packet loss.
2. Make exactly one change.
3. Run it again from the same spot, at roughly the same time of day, for the same length of time.
4. Compare. If jitter did not move, undo the change and try the next one.

One change at a time is the whole discipline. Change three things at once and you will never know which mattered, and you will keep the two that did nothing.

Frequently asked questions

What is a good jitter number?

Under 5 ms is excellent, under 20 ms is fine for almost everything, and over 50 ms causes audible problems on calls. What matters more than the absolute figure is the spread: a steady 40 ms connection beats one swinging between 5 and 200 ms.

Why is my jitter high but my speed test fine?

They measure different things. Speed is how much data you can move. Jitter is how consistently it arrives. A connection can move plenty of data while delivering it in erratic bursts, which is exactly what breaks calls and games.

Does a VPN reduce jitter?

Usually not, and often the opposite. A VPN adds a hop and additional processing. The exception is when your ISP is actively throttling or misrouting a specific service, where a different path can help. Measure before and after rather than assuming.

Can I monitor jitter in the background on iPhone?

No. iOS does not permit a network tool to keep testing while the app is closed or the screen is off. Connection Monitor is a live test you watch, with a rolling 60-second window. For continuous unattended monitoring you need a machine that stays awake, which is what PingKit's Mac Agent is for.

Is jitter the same as ping?

No. Ping is how long a round trip takes. Jitter is how much that time varies between consecutive packets. You can have a low ping with terrible jitter, and that combination is what usually causes stuttering calls.