Audio Reaction Time Test
This audio reaction time test — an auditory reaction time test, in the technical term — measures how fast you react to sound: wait for a beep that plays after a random delay, then click the instant you hear it. Your score is the time in milliseconds between the beep and your click. People usually react faster to sound (by roughly 30–50 ms) than to a visual change, because the ear’s path to the brain is shorter.
Click start, then wait — a beep will sound after a random delay of a few seconds. The instant you hear it, click the pad. Clicking before the beep is a false start and doesn’t count.
Sound on · speakers or wired headphones give the truest score (Bluetooth adds delay) · runs entirely in your browser
Wait for the beep…
Attempts
0
Best
—
Average
—
Your attempts will appear here.
How the test works
Click start and the pad arms itself with a hidden countdown — anywhere from about one to five seconds, chosen at random so you cannot guess it. When the countdown ends, the browser plays a short 880 Hz beep and starts a precision clock at the same instant; your click stops it. The score is the gap between the beep and your click, in milliseconds, timed locally with the browser’s high-resolution clock.
The random delay is the whole game. With a fixed wait, your brain learns the rhythm and starts predicting — and a predicted click is not a reaction at all. Click early here and the attempt is thrown away as a false start, exactly like a sprinter leaving the blocks before the gun. Your best score shows your ceiling; your average over five or more attempts is the honest number to compare over time.
One equipment warning: the clock starts when the beep is sent, so anything slow between your computer and your ear inflates the score. Speakers and wired headphones add almost nothing; Bluetooth audio adds roughly 100–250 ms, which is why a “slow” result on wireless earbuds usually says more about the earbuds than about you.
Why sound beats sight
People react to sound measurably faster than to light. The auditory path — cochlea to brainstem to cortex — is short and built for speed, while a visual signal needs retinal processing and a longer route before it registers. Typical averages tell the story: in lab conditions roughly 140–170 ms for sound against 190–220 ms for light — and in a browser, where device and audio delays pile on, large online datasets put the typical auditory score nearer 185–240 ms, still clearly faster than a visual score on the same setup (try the Reaction Time Test on the same equipment and compare). It is the same reason starting guns, referee whistles and game “audio cues” all use sound when the reaction has to be instant.
What moves your score most is not raw talent: it is sleep, warm-up (the first two attempts are almost always your worst), and honest equipment. Compare your audio score with the F1 Reaction Test for a lights-out visual challenge with a twist, or check the Hearing Test to make sure the ears doing the reacting can still reach the high frequencies.
Frequently asked questions
What is a good audio reaction time?
Judge it against browser scores, not lab numbers: once device and audio delays are included, large online datasets put the typical auditory reaction time around 185–240 ms. On speakers or wired headphones, under 180 ms is quick, 180–230 ms is a solid typical range, and under 160 ms is genuinely fast. Scores past 250 ms usually have a mundane explanation — Bluetooth delay, tiredness, or a first attempt before you settle in. Compare your average over five or more attempts, not a single best fluke.
Why is my audio score faster than my visual reaction time?
The ear gets a head start. Sound is converted to a nerve signal in the cochlea and reaches the brain by a short, direct path, while a visual signal needs the retina and a longer processing chain before you are even aware of it. That is why most people beat their visual reaction score by 30–60 ms on this test, and why races are started with a gun or beep rather than a flag.
Do Bluetooth headphones ruin the result?
They inflate it, yes. Bluetooth audio typically adds 100–250 ms of delay between the computer sending the sound and your ear receiving it, and this test can only time from when the beep is sent. For an honest score use speakers or wired headphones; if Bluetooth is all you have, treat the number as your reaction time plus a fixed equipment tax, and compare against your own past scores rather than other people's.
Why do I keep clicking too early?
Because your brain is predicting instead of reacting — it notices it has been a 'while' and gambles. The random delay (anywhere from about one to five seconds) is deliberately wide so prediction fails often enough to stay honest. False starts are not counted as attempts. A useful trick: react to the beep itself, not to the feeling that it is due, and accept the first two attempts as warm-ups.
Can you actually train reaction time?
A little. Practice on tests like this one shaves a few milliseconds as the movement becomes automatic, and sleep, warm-up and simply being alert matter more than any drill — a tired brain can be 30 ms slower. What training cannot do is move you far outside your physiology: raw nerve speed is largely fixed, so the realistic goal is reaching the fast end of your own range consistently, which is exactly what the average score tracks.
Does audio reaction time change with age?
Yes, but slowly. Auditory reaction time is fastest in the late teens and twenties, then drifts upward by roughly half a millisecond a year from about age 20 in long-running studies — a few milliseconds a decade at first, more later in life. In any single browser session, sleep, caffeine, warm-up and your headphones move the number far more than age does.
How this test works: the beep is generated and timed locally in your browser with a high-resolution clock, and scores never leave this page. Audio hardware adds a few milliseconds (Bluetooth adds far more), so treat scores as a fair comparison against yourself — not a laboratory measurement.