Audio Latency Testbrowser sound delay lab
English
WIRELESS SOUND LAG

Bluetooth Latency Test

Use this Bluetooth latency test to estimate wireless audio lag, compare low-latency modes, and find an A/V sync offset that makes video, games, and calls feel aligned.

browser test bench

Run the bluetooth latency test

Use this Bluetooth latency test to estimate wireless audio lag, compare low-latency modes, and find an A/V sync offset that makes video, games, and calls feel aligned. The tool above is usable on this page, so you can test first and read the guidance below after you have a result.

Current result -- ms Pending
Tap when you hear the beat Use Space or click the pad after each sound.
Example result

A 35 ms average is usually comfortable for video calls and casual gaming. A 140 ms Bluetooth delay is easy to notice when watching lips, rhythm games, or live instrument monitoring. Repeat this bluetooth latency test after changing one device setting so the average and jitter show whether the change helped.

when to use it

What the bluetooth latency test measures

The bluetooth latency test focuses on real playback delay rather than a theoretical device specification. Browser timing, operating-system buffering, USB or Bluetooth transport, driver settings, and your output device all shape the result. The page gives you a repeatable workflow for comparing one setup against another.

Tap mode is best when the sound is isolated in headphones or earbuds. Mic Round-Trip mode is best when a microphone can physically hear a speaker. A/V Sync mode is best when your problem is not a single number, but a correction value that makes picture and sound feel aligned.

Compare setups

Run the same test on wired, wireless, laptop, and speaker outputs.

Watch consistency

A low jitter result is more trustworthy than one lucky tap.

how to interpret

How to read your bluetooth latency test result

Treat the average as the main estimate and jitter as the confidence signal. A low average with high jitter means the setup may be unstable or the tapping rhythm was inconsistent. A high average with low jitter means the delay is real enough to correct or compare.

For headphones and Bluetooth earbuds, repeat the test after changing low-latency mode, game mode, codec settings, sample rate, browser, or output device. For microphone and speaker tests, repeat after moving the microphone, reducing room noise, or disabling aggressive echo cancellation.

Under 40 ms

Usually comfortable for calls and casual listening.

Over 100 ms

Often noticeable in games, videos, and live monitoring.

edge cases

Why browser latency tests vary

The browser can schedule a sound accurately enough for comparison, but it cannot always know the exact moment the sound leaves the driver, codec, speaker, or earbud. Bluetooth devices add buffering, TVs may add video processing, and operating systems can change audio paths when devices reconnect.

That is why this page is designed for repeated measurements and practical decisions. If the result changes slightly, compare averages across several runs. If one device is consistently much higher than another, the difference is usually more meaningful than the exact single number.

No upload needed

The test logic runs in your browser.

Use professional tools for certification

DAW loopback and hardware rigs are better for final studio calibration.

wireless checklist

How to improve a Bluetooth latency test result

A Bluetooth latency test is most useful when you compare states. Run the test once with normal Bluetooth settings, once with game mode or low-latency mode enabled, and once with another device if you have one available. Keep the phone, laptop, or tablet close to the earbuds so radio quality does not become a hidden variable. If the Bluetooth latency test average changes by more than a few dozen milliseconds, the setting or codec probably matters.

Bluetooth audio delay often comes from buffering and codec behavior rather than the web page itself. Some earbuds prioritize stable playback and battery life, while others offer a low-latency gaming profile that may trade sound quality or range for faster response. A Bluetooth latency test cannot name the active codec in every browser, but it can show whether the current connection feels fast enough for your use case.

Use A/V Sync mode when your problem is video lips, a TV, a streaming box, or a rhythm game. Increase or decrease the offset until the flash and beep feel aligned, then try the same correction in your video player, console, TV, or editing app. The Bluetooth latency test result becomes more practical when it points to a correction you can actually apply.

A final Bluetooth latency test pass should be done after the earbuds reconnect, because some devices switch profiles when the microphone is active or when a game launches. Test media playback, call mode, and game mode separately if your device exposes those choices. The most useful Bluetooth latency test result is the one that matches the way you actually watch, play, or speak.

Test game mode

Many earbuds reduce delay only after a low-latency or gaming toggle is enabled.

Compare wired audio

A wired baseline shows how much lag Bluetooth adds to the same device.

quick answers

Bluetooth Latency Test FAQ

How accurate is this bluetooth latency test?

It is a practical browser estimate. Repeated runs and device comparisons are more reliable than one isolated number.

Should I use Tap Test or Mic Round-Trip?

Use Tap Test for headphones and earbuds. Use Mic Round-Trip only when your microphone can hear the speaker output.

Why is Bluetooth usually slower than wired audio?

Bluetooth devices often buffer and encode audio before playback. That buffering can add noticeable lag, especially without a low-latency mode.

Can I fix audio delay after measuring it?

Often yes. Try wired audio, game mode, low-latency Bluetooth settings, a different browser, or an A/V offset in your player or TV.

Does the test upload recordings?

No. The browser analyzes timing locally. Mic mode uses permission only while the test is running.

How do I compare two results from this bluetooth latency test?

Run the same bluetooth latency test mode twice with only one setting changed. Compare the average first, then use jitter to decide which result is more stable.