A GPS speed app trails your real speed by a second or two when you accelerate or brake hard, and that’s mostly by design. The phone delivers about one new fix per second, and apps average several fixes so the number doesn’t twitch. At a steady speed the lag disappears; under hard acceleration the display catches up a couple of seconds after you settle. A reading that freezes for longer than that is a lost signal, not lag. In a well-built app, lag doesn’t cost you any trip distance either, because distance is measured from positions, not from the smoothed speed.
This article is about how quickly the number follows a change in speed. If your reading is steady but you doubt it at highway speed, see is GPS speed accurate at high speed? instead.
Where does GPS speed lag come from? #
- The update rate. Most phones hand apps about one GPS fix per second. Nothing can change faster than that on screen.
- Smoothing. Raw one-second speeds jitter, so apps average them. Speedometer GPS shows the average of the last five one-second readings. During steady acceleration, a five-reading average sits roughly two seconds behind the present.
- The receiver’s own filtering. GPS chips run their own filters before an app ever sees the data, and how much they smooth varies from phone to phone.
- A weak fix. With few satellites or reflected signals, the receiver may hold back or predict, and speed trails or jumps.
- Speed worked out from positions. Most phones report a Doppler-based speed that’s quick and steady. When a phone doesn’t, an app has to derive speed from the distance between fixes, which is laggier and noisier. A good app uses the phone’s own speed whenever it’s available and only falls back to positions when it isn’t.
How big is the lag in real numbers? #
At a steady cruise, zero: the average of five identical speeds is the same speed. It only shows while your speed is changing. If you accelerate briskly from 0 to 100 km/h in 10 seconds, gaining 10 km/h every second, a five-second average reads about 20 km/h below your true speed partway through, then catches up within about two seconds of reaching a steady speed. Braking works the same way in reverse, so the display keeps showing some speed for a moment after you stop.
Is it lag or something else? #
| What you see | Most likely cause |
|---|---|
| The number trails while you speed up, then matches at a steady speed | Normal smoothing |
| The number freezes on one value for several seconds | Lost signal; a well-behaved app drops to 0 and shows it’s searching instead of freezing |
| Random jumps and spikes | Weak fix or reflected signals |
| Speed still showing for a second or two after you stop | The tail of the smoothing |
| Steadily lower than the dashboard at a constant speed | Not lag: car speedometers are built to read high |
That last one confuses a lot of drivers. If GPS reads 67 mph while the dash says 70 on a steady highway, the phone isn’t slow; the speedometer is reading high, as most do. Our explainer on why a car speedometer reads higher than GPS covers the rules behind that.
Does GPS speed lag affect trip distance? #
Not in an app that measures distance properly. Speedometer GPS adds up the straight-line distance between each pair of position fixes, so the smoothing on the speed readout never touches the distance total.
Even an app that worked distance out from its smoothed speed would lose very little. A moving average delays the speed without changing its total over time, so apart from the last couple of seconds of a trip, the distance comes out the same. When GPS trip distance is off, the usual reasons are corners cut between fixes, tunnels and signal filtering, which our article on GPS distance vs your odometer covers.
Smoothing does affect top speed. An app that records the maximum from the smoothed value, as Speedometer GPS does, can’t be fooled by one glitchy reading into a fake top speed, but a very short peak, like a two-second sprint or a quick overtake, comes out a little lower than it really was.
How to reduce lag and jitter #
- Give the phone a clear view of the sky. A dashboard or handlebar mount beats a pocket, a cup holder or a spot under a metal roof.
- Let the fix settle. Wait until the accuracy indicator shows a strong fix, ideally within 5 to 10 metres, before you rely on the number.
- Keep the speed app in the foreground. Apps that don’t track in the background, Speedometer GPS included, stop getting fixes when you switch away or the screen locks.
- Turn on precise location. On iPhone, apps with approximate location only get a rough area. On Android, the Location Accuracy setting helps the first fix.
- Restart location or the phone if readings seem stuck, and keep the operating system updated.
- Accept the trade-off. Less smoothing means a faster but twitchier number. Where an app offers a smoothing setting you can choose; where it uses a fixed average, the lag is part of the design.
If you need precise acceleration times, such as 0-60 runs, a phone at one fix per second is the wrong tool. Dedicated GNSS performance meters that update ten or more times a second exist for that.
Why lag matters more on a bike or a run #
On a bike, a sprint lasts a few seconds, so smoothing takes a real bite out of the peak. A wheel sensor responds within one turn of the wheel, as our bike speed sensor vs GPS comparison explains. Running is slower still, and live pace takes several seconds to settle when you start an interval, which is why running pace is best judged over a whole split.
In a car, the dashboard speedometer responds instantly, so treat GPS as the check on it, not the thing you watch. If you want a warning at a set speed, set the alarm before you leave and let it buzz, so there’s no reason to look at the phone while you drive.
Frequently asked questions #
Why is my GPS speed delayed? #
Phones deliver about one GPS fix per second, and speed apps average several fixes to keep the number steady. Together that puts the display a second or two behind while your speed is changing. At a steady speed there’s no meaningful delay.
Is GPS speed accurate if it lags? #
Yes, once your speed is steady. The lag only affects how quickly the number follows a change. With a good fix, a steady GPS speed is typically within a couple of km/h of your true ground speed.
Can I make my phone’s GPS update faster? #
Not much. Phones generally give apps about one fix per second. You can make the reading steadier and quicker to settle by keeping the phone where it sees the sky and waiting for a good fix. Dedicated GNSS meters with 10 Hz or faster updates exist for timing acceleration.
Why does GPS show speed when I’ve stopped? #
For a second or two after you stop, the smoothing is still averaging readings from when you were moving. If it keeps showing a small speed while you’re parked, the fix is weak and the position is drifting; good apps filter that out of the distance.