Your Bluetooth Headphones Are ~300 ms Late. Measure It in One Browser Tab

This is a condensed cross-post of the original KeyboardTester.click guide: Bluetooth Audio Delay: Measure the Lag, Then Fix It.

Bluetooth audio is always late. The only questions are how late, and whether you can do anything about it.

Every Bluetooth chain does four jobs before you hear a sound: the source encodes it with a codec, the radio ships it in packets, the receiver buffers enough data to survive retransmissions, and the headphone chip decodes it. Each stage costs milliseconds. Video players hide the total by quietly delaying the picture; games can't wait for your earbuds, which is why the same pair feels fine on YouTube and broken in a shooter.

The honest numbers

Connection	Measured / specified delay	Basis
Wired	Effectively immediate (use as baseline)	Practical guidance
Everyday Bluetooth (SBC / aptX / LDAC / AAC)	308 / 316 / 324 / 369 ms averages across four Android flagships	SoundGuys lab tests
aptX Low Latency (both ends)	~40 ms by specification	Qualcomm aptX
Bluetooth LE Audio (LC3)	Designed for reduced latency vs Classic; no single public ms figure	Microsoft LE Audio docs

Human tolerance is narrow: broadcast research behind Rec. ITU-R BT.1359-1 found viewers start detecting lip-sync error when audio lags the picture by roughly 125 ms (or leads by only ~45 ms). Ordinary Bluetooth links blow past that routinely.

Measure before you touch a single setting

You can put a number on your own delay with nothing but a speaker and a microphone — the same acoustic principle Apple uses when an iPhone calibrates Wireless Audio Sync on Apple TV 4K.

The browser audio latency test plays correlated chirps, listens for their return, and reports the median round-trip delay with confidence filtering and jitter.

The workflow is a subtraction, because a round-trip includes fixed costs (OS mixer, mic path, air travel) that have nothing to do with Bluetooth:

1. Baseline first. Run the check on wired or built-in speakers. Quiet room, volume 30-50%, mic 20-50 cm from the speaker. Note the median.
2. Switch only the output. Connect the Bluetooth headphones, keep everything else identical, run it again.
3. Subtract. Bluetooth minus wired = your Bluetooth link share.
4. Trust only clean runs. High jitter or rejected chirps mean rerun, not squint.
5. Re-measure after every fix so you know which change earned the milliseconds.

The fix ladder (cheapest step first)

1. Re-pair from scratch — forget the device, restart both, pair again. Forces fresh codec negotiation; links silently fall back to baseline SBC and nothing warns you.
2. Pick the best mutual codec. Android: Developer options → Bluetooth Audio Codec. Windows 11: check the LE Audio toggle. macOS/iOS negotiate automatically.
3. Enable game / low-latency mode in the earbud companion app — it trades range or quality for a smaller buffer.
4. Clear the airwaves. Line of sight, distance from the router and USB 3.0 ports, disable multipoint while gaming.
5. Disable audio enhancements. EQs and spatializers add their own buffers.
6. Update firmware and drivers on both ends.
7. Re-measure and decide. Still far above the ~40 ms class? Settings won't close the gap — hardware will: an aptX-LL/adaptive transmitter + matching headset, LE Audio on both ends, a 2.4 GHz gaming dongle, or a wire.

One more culprit hides outside the audio path: a wireless controller adds its own input delay on top. Measure it separately with a gamepad response check so input lag never gets blamed on your headphones.

---

Full guide (platform-by-platform levers, the TV lip-sync special case, an upgrade decision matrix, and FAQ): Bluetooth Audio Delay: Measure the Lag, Then Fix It