Audio Latency Testbrowser sound delay lab
English
HEADPHONE DELAY CHECK

Headphone Latency Test

Use this headphone latency test to estimate how late sound reaches your ears through wired headphones, earbuds, gaming headsets, laptop speakers, or USB audio devices.

browser test bench

Run the headphone latency test

Use this headphone latency test to estimate how late sound reaches your ears through wired headphones, earbuds, gaming headsets, laptop speakers, or USB audio devices. 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 headphone latency test after changing one device setting so the average and jitter show whether the change helped.

when to use it

What the headphone latency test measures

The headphone 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 headphone 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.

testing checklist

How to get a cleaner headphone latency test score

A reliable headphone latency test starts with a quiet room, a comfortable volume, and one output device selected in the operating system. Close other apps that may steal audio focus, turn off spatial effects for the first run, and keep the browser tab active until the samples finish. Then repeat the same headphone latency test after changing only one setting, such as USB output, a game headset mode, sample rate, or audio enhancement. One controlled change at a time makes the difference easier to trust.

For wired headphones, the result should usually be lower and more stable than wireless earbuds. If wired headphones still show a high headphone latency test average, check the browser output device, system audio enhancements, USB hub, virtual surround driver, or recording software running in the background. If the average is low but jitter is high, your clicks may be inconsistent or the system may be scheduling audio unevenly.

For gaming headsets and earbuds, compare Tap Test with A/V Sync mode. Tap Test gives a human response estimate, while A/V Sync helps you decide whether a video, game, capture card, or streaming app needs an offset. When both modes point to the same delay range, the headphone latency test result is more useful than one isolated number.

A final headphone latency test pass is useful after the device has been connected for a few minutes. Some USB headsets and laptop outputs change behavior after sleep, reconnection, driver switching, or a conferencing app taking control of the audio path. Save the average, minimum, maximum, and jitter from each headphone latency test run, then compare the stable setup rather than the first cold-start sample.

Use one device path

Do not switch between speakers, HDMI, and headset output during the same run.

Repeat after changes

Run the same headphone latency test again after enabling or disabling enhancements.

quick answers

Headphone Latency Test FAQ

How accurate is this headphone 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 headphone latency test?

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