Run five guided tone trials and use the median response to compare wired, Bluetooth, speaker, or audio-interface setups.
Browser utility
Use headphones, speakers, or the device you want to test.
The page will play a short tone at low volume.
Click the moment you hear each tone.
Compare a steadier five-trial result and browser timing details.
Step 1: make sure your headphones or speakers are ready, then continue.
Start the guided test to record five trials and calculate a median response delay.
Guide
Run five browser audio latency trials, compare the median across Bluetooth, wired, speaker, or audio-interface setups, and review Web Audio timing details.
Browser audio latency matters for music tools, games, recording interfaces, metronomes, web synthesizers, and interactive media. When sound arrives late, clicks and visuals feel disconnected. This page uses a guided test so the user knows exactly when audio will play and when to respond.
The test plays five short tones through the Web Audio API and asks you to click as soon as you hear each one. The median reduces the influence of one unusually early or late click. The result still includes human reaction time, so it is a practical comparison rather than a laboratory-grade hardware measurement.
The page also reports browser-exposed timing values such as base latency, output latency when available, and sample rate. Those values help explain whether the browser and device path look unusually slow before you run a more formal loopback test.
Use this page as a quick diagnostic when comparing browsers, headphones, Bluetooth devices, speakers, or external audio interfaces. Keep volume comfortable because the test plays a short tone.
Quick reference
Choose one output setup, then record five click-after-tone trials.
Median click response: 214 ms / Five trials: 198, 208, 214, 227, 241 ms / Sample rate: 48000 Hz
The click response includes your reaction time, so use repeated trials and compare relative results rather than treating one value as hardware latency.
Bluetooth, browser choice, operating system routing, and external audio interfaces can all change the result.
For physical round-trip latency, use a microphone or loopback setup. This browser test is a quick comparison tool.
In-depth guide
A browser click test is most useful as a repeatable comparison. Keep the setup stable, collect multiple trials, and compare the median instead of treating one click as a hardware measurement.
Keep the browser, volume, output device, and physical position unchanged for all five trials. This reduces avoidable variation between clicks.
Record one five-trial median for each setup. Bluetooth usually adds buffering, while wired headphones or an audio interface can provide a shorter path.
The measured click delay includes hearing, attention, and mouse or trackpad response. Use the result to compare setups, not to claim exact round-trip latency.
DAW monitoring, live performance, and driver tuning require a microphone or physical loopback measurement. Browser timing values alone do not cover the complete analog path.
Common mistakes
No. A click-based browser test includes human reaction time. Physical round-trip latency needs microphone or loopback measurement.
A guided flow reduces confusion because the page can warn you before sound plays and ask for the click at the right moment.
Not every browser exposes outputLatency. The tool shows Not reported when that value is unavailable.
Yes. The test plays a very short tone at low volume.
Run at least five trials with the same setup and use the median. More trials can help when your click times vary widely.
Yes. Run a complete five-trial set for each device under the same browser and volume conditions, then compare the medians.
Yes. The click response includes your reaction time plus browser and device delays, so it is a relative comparison rather than a lab measurement.