Connect one output path
Select the headphones, speakers, USB interface, monitor, or Bluetooth device you want to check. If you switch hardware, wait for the operating system to finish connecting before starting another run.
BROWSER AUDIO DIAGNOSTICS
Audio Latency Test
Estimate how much delay you feel between a browser click and your tap. This audio latency test works with speakers, headphones, Bluetooth headsets, and wired interfaces without a download or account.
- Runs in your browser
- Shows milliseconds
- Works without uploads
- Repeatable local trials
01
START WITH A TIMING CHECK
Measure your sound delay
Tap with the beatReady
Timing note: A browser can estimate event timing, but it cannot replace a calibrated round-trip measurement with known hardware.
A FIVE-TRIAL AUDIO LATENCY TEST
How to use this audio latency test
The useful question is usually comparative: does Bluetooth feel slower than wired audio, or did a browser and operating-system setting add delay? Run the same short sequence for each setup and keep the conditions consistent.
Listen for the click
Press Start Latency Test. A quiet click repeats at a comfortable pace. Keep your hand near Tap now and listen for the next beat instead of watching the button.
Tap five times
Tap when you hear each click. The page stores the absolute distance between the scheduled beat and your tap, then uses the median to reduce the effect of one early or late response.
Compare like with like
Run a second set with the same browser tab, volume, sample rate, and nearby applications. Change only one output path so the difference has a useful meaning.
READ THE RESULT CAREFULLY
What an audio latency result means
Milliseconds are useful for comparing a setup, but a browser result is not a laboratory certificate. It combines browser scheduling, audio buffering, your device path, and the reaction time of the person tapping.
Median is the center
The median is the middle value after the five trials are sorted. It is less sensitive than an average to one accidental double tap or a moment when you looked away.
Range shows stability
A narrow range means your taps and the browser schedule were fairly consistent. A wide range suggests that you should repeat the run before blaming the headphones or speakers.
Lower is not always better
Low delay is helpful for rhythm games, monitoring, and live instruments, but a comfortable and stable output can matter more than a single small number.
USE CASES
When to run an audio latency test
A short comparison is most helpful when the symptom is noticeable but the cause is unclear. Save the result with the device name and the browser so you can reproduce the same check later.
A
Bluetooth headphones
Wireless codecs, radio conditions, buffering, and battery-saving modes can add delay. Compare Bluetooth with a wired pair at the same volume and browser tab.
B
Music or video sync
If speech or a drum hit feels late, test before changing every system setting. A repeatable result tells you whether the issue follows one output path.
C
Rhythm games and instruments
Game audio and live monitoring often reveal small offsets. Use this page as a quick comparison, then use the game's own calibration or the interface manufacturer's measurements for final setup.
D
New browser or device
A browser update, USB hub, monitor, or virtual audio cable can change buffering. Run a baseline with the setup that previously felt normal before troubleshooting.
FIX AN UNEXPECTED DELAY
What to check when the number looks high
The page cannot repair a device, but it can help you narrow the comparison. Change one variable at a time and reset the result whenever you change the output path.
01
Repeat the five trials
Tap timing is a human input. Sit comfortably, listen to the click, and repeat the run. If the range is wide, the session is not stable enough to compare.
02
Check wireless and power modes
Bluetooth codec selection, low-power modes, and a weak connection can increase buffering. Test close to the computer with other wireless audio paused.
03
Close competing audio tools
Virtual mixers, screen recorders, meetings, games, and many browser tabs may request their own audio contexts. Close them, reload this page, and run a clean baseline.
04
Confirm the actual output
Operating-system routing can send the browser to a monitor or a different headset than the one you are wearing. Verify the selected output before interpreting the result.
ACCURACY AND PRIVACY
Browser limitations to keep in mind
This tool is intentionally transparent about what it can and cannot observe. No recording or upload is needed for the timing estimate, and the page does not claim a calibrated hardware measurement.
Not a round-trip meter
The test measures the gap between a scheduled browser beat and your tap. It does not send a known signal through a microphone and back, so it cannot calculate a true input-plus-output round trip.
No permanent device score
Results can change with the browser, operating system, CPU load, sample rate, Bluetooth codec, power mode, and your reaction. Treat the number as a session comparison.
Local by design
The page uses local JavaScript, the Web Audio API when available, and performance timing. It does not request microphone permission, upload audio, save recordings, or require an account.
Use safe listening levels
Keep volume low before starting and increase it only enough to hear the click. A browser cannot know the sound pressure at your ears or protect against an unsafe listening level.
COMMON QUESTIONS
Audio latency test FAQ
These answers explain how to use the browser test without turning an estimate into a hardware guarantee.
What is a normal audio latency result?
There is no single normal value for every browser and device. Wired paths often feel more immediate, while Bluetooth, virtual mixers, and power-saving modes can add delay. Use the same page and conditions to compare two setups.
Can I test Bluetooth headphone latency online?
Yes. Choose Bluetooth headphones or speaker in the output path label, run five trials, and compare the median with a wired device. The selector is a note for your comparison; the browser cannot force a hardware route.
Does this measure true round-trip audio latency?
No. It estimates browser output timing against your tap. A calibrated round-trip test needs known input and output hardware, a microphone path, and controlled measurement software.
Why do my trials vary so much?
Variation can come from reaction time, missed beats, background CPU work, wireless buffering, or a browser tab that is not active. Repeat the test with one tab, stable volume, and fewer competing applications.
Can I use this for a rhythm game or live instrument?
Use it as a quick comparison, not as the final calibration. Rhythm games and audio interfaces usually provide their own offset controls or technical measurements that match the actual application path.
Does the audio latency test save my taps?
No. Trial values live in the page while it is open. They are not uploaded or stored as an account record, and resetting the tool clears the live list.
Why does a browser result differ from another website?
Different tools schedule clicks, use different input methods, and report different parts of the audio path. Compare trends inside one tool before comparing absolute numbers across websites.
READY TO COMPARE
Measure the delay you can actually feel
Start with a quiet click, complete five steady taps, and keep the result tied to the device and browser that produced it. That simple record is more useful than an unexplained promise of perfect audio timing.