Audio Latency Test – Measure Speaker-to-Mic & Bluetooth Delay
Round trip & tapReady
- Wired: 5–30 ms
- Bluetooth: 100–300 ms
- Gaming target: under 50 ms
- Allow the mic in the address bar
- Choose the right input device
- Audio never leaves the tab
- Runs inside your browser
- No upload, no account
- Nothing saved after you close
Audio and Bluetooth latency test
Audio latency is the delay between a sound being sent and heard, and it matters for gaming, music and lip-sync. This test estimates it by tapping along to a beat or by playing a click from the speaker into the microphone.
Round-trip latency
The loopback test plays a click and times when the mic hears it.
Bluetooth latency
Bluetooth codecs buffer audio; SBC and AAC often add 150–250 ms, aptX Low Latency and LE Audio less.
Wired vs wireless
Wired headphones add almost no delay; wireless trades convenience for latency and compression.
How to Use the
Audio Latency Test
- 01
Loopback
put the mic near the speaker and press Measure.
- 02
Repeat
take five readings and use the average.
- 03
Tap test
start the beat and tap along on headphones.
- 04
Compare
repeat wired and wireless to see the difference.
Round-trip latency
The loopback test plays a click and times when the mic hears it. Result = output delay + input delay + air travel (about 3 ms per metre).
Bluetooth latency
Bluetooth codecs buffer audio; SBC and AAC often add 150–250 ms, aptX Low Latency and LE Audio less. Video apps compensate, games and music apps often cannot.
Wired vs wireless
Wired headphones add almost no delay; wireless trades convenience for latency and compression.
Reducing latency
- Use wired or low-latency codecs
- Use ASIO/CoreAudio with small buffers in music apps
- Disable audio enhancements
Latency details
How the test works
A click is played and the microphone listens for it; the time difference is round-trip latency.
Calibrate reaction time
In tap mode, first tap along with wired headphones to learn your personal offset.
What the numbers mean
Under 20 ms feels instant, 20–50 ms is fine for most uses, above 100 ms is noticeable in games and music.
Who this helps
Gamers, musicians, streamers and anyone with lip-sync problems.
Compare one change at a time
Change only the headphones or only the codec between runs.
Accuracy
How accurate is the test?
Within about ±5–10 ms after averaging.
How to read your audio delay result
| Result | What it means |
|---|---|
| Under 20 ms | Excellent; fine for playing instruments |
| 20–50 ms | Good for games and calls |
| 50–150 ms | Noticeable for rhythm games and music |
| Over 150 ms | Typical Bluetooth; lip-sync may suffer |
Related guides and fixes
Learn more in these guides: Bluetooth audio delay, Microphone not working, Microphone settings, Discord mic fixes, Decibel levels chart, What is LUFS.
Frequently Asked Questions
Q.Why do results vary?
Buffer timing differs per run; average several.
Q.Tap test accuracy?
Includes your reaction; compare relative values.
Q.Is the click loud?
Short; keep volume moderate.
Q.Why does latency matter for gaming?
Delay between an action and its sound makes timing harder and positional cues arrive late. Wired headphones or a low-latency mode help most.