Precision test · 10 cues · average scored
Audio reaction time test
Respond the instant you hear the cue. Ten randomized sounds, an average score — and honest labeling, because a browser can't see inside your headphones.
Use wired headphones or speakers for the cleanest baseline. Bluetooth can add hidden delay, so wireless results are best treated as same-setup comparisons.
Click, tap, or press space · a click before the cue voids it
Ranking needs all 10 cues clean. Wait for the sound.
Ten randomized cues · cues advance on their own · a pre-cue click voids that cue
Reported delay is not timing precision or physical calibration. Browser/device/privacy settings can affect these estimates; a small or fixed value does not certify accuracy. Compare repeats on the same setup.
History belongs to this browser and website address. Records saved on another domain are not copied here.
Reading local history…
How this audio reaction time test works
The audio test — also called a sound reaction time test or auditory reaction time test — measures your response to 10 randomized sound cues. Respond once when you hear each sound; this is simple sound detection, not a test of recognizing footsteps or making a game decision.
Browser audio can schedule cues precisely, but a web page cannot directly observe the physical delay inside Bluetooth headphones, TV speakers, operating-system mixers, or USB audio devices. See how we measure for the browser timing model and its limits.
Clicking before a cue voids it as a false start, and a ranked run needs all 10 cues clean. Randomized timing alone is not enough to make guessing unprofitable: click continuously and a press eventually lands just after a cue, which is how anticipation produces fake sub-100 ms results. The result screen shows the average reaction time as the main leaderboard score, plus a point total that rewards fast clicks and consistent timing across all 10 triggers.
What your audio reaction time score means
Lower average milliseconds means faster measured responses on this setup. Best is only one click; consistency (SD) describes the spread between responses. Compare both average and SD across complete, clean runs rather than treating your fastest click as your baseline.
Audio points are an app score, not a population percentile; average milliseconds determines leaderboard rank. Audio clock readings and output-delay estimates do not establish a numerical error bound. Coarse or unresolved clocks, estimated onset mapping, and interruptions qualify the result; none of these readings is an acoustic calibration. Compare results within the same browser and setup, not by choosing the browser with the lowest number.
Build a baseline you can compare
- Preview one cue at a comfortable volume, then finish a practice run.
- Keep the same browser, audio output, cue, volume, and response method. Keep the tab visible.
- Record three complete 10-cue runs, with a short break between them. Note any false starts or interruptions.
- Compare all clean-run averages and SDs, not just the best run. Keep Bluetooth and wired results separate.
Three runs is a starting log, not a guarantee of reliability. A change that repeats across sessions is more informative than one lower number. The auditory measurement guide explains what to record and why a headset comparison is not a latency calibration.
Want a short sound-response practice block? Open the audio test again and start when ready. Repeating does not require ranking or donation. This is simple sound detection, not an auditory Arena drill or evidence of better game performance.
Audio reaction time, answered
+Is audio reaction time faster than visual?
There is no guaranteed ordering for your browser scores. Audio output delay and differences between test protocols can change the comparison. Build separate same-setup baselines for sound and screen cues.
+Does Bluetooth ruin my score?
Bluetooth can add hidden output delay, and the amount depends on the device and audio path. Keep wireless results as a separate same-setup baseline. Wired output is preferred for comparisons, but it does not remove every source of delay.
+Why does audio rank by average over 10 cues?
The average includes every valid response instead of selecting your fastest click. Leaderboard rank uses average milliseconds, not audio points. Points combine cue scores, best speed, and regularity; a ranked run needs all 10 cues clean.
+What is a good audio reaction time?
Start with your own repeated, clean runs on the same setup. A lower average means faster measured responses there, but one best click or a score from different headphones is not a fair benchmark. This test does not establish a universal human norm or measure neural speed in isolation.
+What happens if I click before the sound?
That cue is voided as a false start, and the run can no longer be ranked — a ranked audio run needs all 10 cues clean. The test keeps going so you can finish for practice, and you can restart at any point. This is what stops spam-clicking: without it, clicking continuously eventually lands a press just after a cue and pays out a fake sub-100 ms result.