Audio latency test
Tap when the panel flashes, then tap when you hear each beep. The difference estimates your audio delay in milliseconds.
Audio latency test workspace
How to use
4 short steps.
Press the panel to start
Five visual trials come first. Tap as soon as the panel turns green.
Tap when you hear each beep
Five audio trials follow. The panel does not change, so keep your eyes off it and listen.
Read the estimate
The estimate is the audio median minus the visual median. A wide spread means the trials varied; run again.
Compare connections
Run once wired and once on Bluetooth. The difference between the two is the Bluetooth delay.
What the result means
Match what you see to one of these.
Under 40 ms
If the estimate is under 40 ms, the delay is typical for wired output or a low-latency gaming mode, and you will not notice it in games or video.
40 to 150 ms
If the estimate falls between 40 and 150 ms, it is typical for Bluetooth. Video players correct for it, but rhythm games and instruments feel late.
Over 150 ms
If the estimate is over 150 ms, lips and sound will be visibly out of step. Look for a low-latency or gaming mode on the headset, or use a wired connection.
The spread is over 100 ms
If the spread is wide, your taps varied more than the delay you are measuring. Repeat with fewer distractions and take the lower of the two runs.
Troubleshooting
If the test fails, try these in order.
Turn on low-latency or gaming mode
Many Bluetooth headsets have a game mode in their app or by holding a button. Turn it on and run the test again.
Change the codec
In the phone or computer's Bluetooth settings, prefer aptX, aptX Adaptive or LE Audio over SBC where offered. Run again.
Close heavy apps and repeat
Background CPU load delays the beep. Close other tabs and apps, then run the full test again.
Compare wired
Plug in wired headphones and run again. If the wired result is also high, the delay is in the computer, not the headset.
What this test can't tell you
Where a browser check stops.
- The estimate includes your reaction, the display, browser scheduling, the operating system and the output hardware; it cannot isolate a Bluetooth codec.
- Reactions to sound are usually 20 to 50 ms faster than to light, so this method under-reads by a few tens of milliseconds. Compare two connections rather than trusting one number.
- The browser output latency card comes from the AudioContext outputLatency value, which Safari does not report and which excludes Bluetooth.
FAQ
Common questions about this test.
What is a good audio latency?
Wired output is typically 5 to 20 ms. Low-latency Bluetooth codecs such as aptX Adaptive and LE Audio run 40 to 80 ms, aptX 60 to 120, AAC 100 to 200 and SBC 150 to 300. These are typical ranges, not pass marks.
Is 75 ms audio delay noticeable?
Not for music listening, and video players hide it by delaying the picture. Most people notice lip-sync errors from about 80 to 100 ms, and rhythm games and live instruments feel late well below that.
Is 20 ms audio latency good?
Yes. 20 ms is at the low end of what wired headphones and speakers achieve and is not noticeable in games, calls or music.
How do I test Bluetooth audio latency?
Run this test once with wired headphones and once with the Bluetooth headset, keeping the same device and browser. The difference between the two estimates is the Bluetooth delay.
Why is my Bluetooth audio delayed?
Bluetooth compresses audio with a codec and buffers it to avoid dropouts, which adds 100 to 300 ms with SBC or AAC. Low-latency modes and codecs such as aptX Adaptive cut that to under 80 ms.