Calibration first
The test stays locked until you play the 1 kHz beep and confirm you heard it. A silent round looks exactly like a slow one, so we verify the sound path before any timing happens.
Measure how fast you respond to sound instead of light. Calibrate your audio first, then react to a 1,000 Hz beep across five rounds — median score, false-start rejection, and an honest account of the audio latency your device adds.
This test only works if the beep actually reaches your ears. Play the test tone — a 1,000 Hz sine wave, about 150 ms long — and confirm you heard it clearly before any timing starts. Use speakers or wired headphones: Bluetooth audio adds enough delay to inflate every round. On an iPhone, check that the mute (silent) switch is off.
The test panel below stays locked until you confirm the beep.
After calibration, activate this button to start a round. Wait for the beep, then activate it again — or press the spacebar — as quickly as possible. This test requires audible sound output.
Five-round score card
Your score includes this device’s audio output latency on top of your response. On Bluetooth audio that added delay can exceed 100 ms — compare only sessions taken on the same audio setup.
Completed sessions are saved automatically on this device.
This is a five-round simple auditory reaction time test: instead of waiting for a panel to change color, you wait for a 1,000 Hz beep. Before timing starts you play a test tone and confirm you heard it, so a muted speaker or a silent iPhone switch can’t quietly corrupt your score. Each round waits a random 1.5–4.5 seconds, plays the beep, and times your click, tap, or spacebar press. Pressing early — or within 100 ms of the beep — is rejected as anticipation and retried; no response within 1,000 ms is treated as a missed tone. The headline result is the median of five valid rounds. Everything runs locally in your browser, and your score includes your audio device’s output latency on top of your biological response.
Auditory reaction time has two very different reference points, and mixing them up is the most common way people misread their score.
| Benchmark | Figure | What it includes |
|---|---|---|
| Laboratory (calibrated) | Simple auditory reaction around 140–160 ms (Jain et al., 2015) | Dedicated hardware with measured, subtracted device delay — close to pure physiology. |
| Browser (online sample) | 241 ms mean across a large web-based sample (Madison et al., 2016) | Response plus the participants’ own hardware, operating system, and browser delay. |
Your score here belongs to the second row. It is the sum of your nervous system’s response and your audio output path, input device, OS, and browser — and no web test can separate those parts from the outside. So don’t compare your number with the 140–160 ms lab figure and conclude you are slow; compare it with other sessions on the same setup, where a shifting median actually means something.
Auditory reactions are consistently faster than visual ones, and the reason is anatomical. Sound reaches the auditory cortex in roughly 8–10 ms, while a visual signal needs about 20–40 ms to reach the visual cortex — and the auditory pathway passes through fewer synaptic relay stages on the way. Across simple reaction tasks, studies typically find sound responses about 20–40 ms faster than sight (Hülsdünker et al., 2021).
That advantage is why sprinters react to a gun rather than a light, and why athletics treats a start under 100 ms after the gun as anticipation — see our world record fact-check for the full story. In a browser test, though, the physiological edge competes with your hardware: Bluetooth audio can add an estimated 150–250 ms of output latency, which is more than enough to erase it. Run the visual test on the homepage and this page on the same device to see your own gap in the comparison box below.
The clock starts when the browser schedules the beep, but your reaction can only begin when the sound reaches your ear. Everything in between is output latency added to your score. The figures below are order-of-magnitude estimates from typical hardware behavior — not guarantees, and individual devices vary.
| Audio path | Estimated added latency | Notes |
|---|---|---|
| Built-in speakers / wired headphones | ~ under 10 ms | The reference setup. Use this for scores you want to compare over time. |
| USB audio interface / external DAC | ~ 10–30 ms | Driver buffering adds a small, fairly stable delay. |
| Bluetooth with aptX Low Latency | ~ 40–80 ms | Requires support on both the transmitter and the headphones. |
| Bluetooth with the standard SBC codec | ~ 150–250 ms | The default on most wireless audio — enough to dominate the measurement. |
The practical rule is simple: test on speakers or wired headphones. A Bluetooth score is still valid as a measurement of that whole setup — just don’t compare it with a wired session or with anyone else’s hardware.
The test stays locked until you play the 1 kHz beep and confirm you heard it. A silent round looks exactly like a slow one, so we verify the sound path before any timing happens.
Each round waits a random 1.5–4.5 seconds so you cannot time the beep. A press during the wait — or within 100 ms of the sound — is rejected as anticipation and the round is retried.
Five valid rounds are sorted and the middle value is reported. One lucky or distracted round cannot dominate the headline score; average, best, and spread stay visible beside it.
If 1,000 ms pass with no response, the round is voided with a prompt to check your volume. A round you never heard never becomes a fake 1,200 ms “reaction.”
The clock starts at the moment the browser schedules the beep and stops on your earliest input event — click, tap, or spacebar keydown. Audio output latency between scheduling and your ear is included in the score, and we say so rather than pretending to subtract it.
Results are stored only in this browser’s local storage, where you can review or clear them. Nothing about this test is uploaded.
The full protocol, calculations, and limitations are documented on the methodology page.
Take the visual reaction time test on the homepage first, then finish a session here. This box will compare your visual median with your auditory median — laboratory studies typically find sound reactions about 20–40 ms faster than sight.
Yes, on average. Auditory signals reach the cortex in roughly 8–10 ms while visual signals take about 20–40 ms, and studies comparing simple reaction tasks typically find sound reactions about 20–40 ms faster than sight (Hülsdünker et al., 2021). In a browser test the gap can shrink or even reverse, because audio output latency — especially Bluetooth — is added to your sound score while display latency is added to your visual score.
For an online browser test like this one, taken on speakers or wired headphones, a five-round median under about 220 ms is on the faster side and 220–300 ms is typical — orientation, not a ranking. Two anchors frame the range: a calibrated laboratory study put simple auditory reaction around 140–160 ms (Jain et al., 2015), while a large online sample measured a 241 ms mean once device latency was included (Madison et al., 2016). Your browser score lives in the second world.
Yes, heavily. Bluetooth audio adds output latency between the moment the browser schedules the beep and the moment it reaches your ear — an estimated 150–250 ms with the common SBC codec and roughly 40–80 ms with low-latency codecs like aptX LL (these are order-of-magnitude estimates, not guarantees). That delay is added directly to every round. For a meaningful score, test on speakers or wired headphones.
No. This page measures how quickly you respond to a 1,000 Hz tone that you have already confirmed you can hear — it says nothing about your hearing thresholds, and it cannot screen for hearing loss. The 1 kHz stimulus sits inside the speech range, so mild high-frequency hearing loss usually has little effect on the result, but individual differences exist. For any concern about your hearing, see an audiologist.
First you calibrate: play the test beep and confirm you heard it clearly, which unlocks the test. Each round then waits a random 1.5–4.5 seconds and plays a 1,000 Hz tone; respond by clicking, tapping, or pressing the spacebar as fast as you can. Pressing before the beep, or within 100 ms of it, is rejected as anticipation and the round is retried; no response within 1,000 ms is treated as a missed tone. After five valid rounds your headline score is the median.
Because a silent round is indistinguishable from a slow one. An iPhone mute switch, a muted tab, or audio routed to a disconnected Bluetooth device would otherwise produce missed rounds and inflated scores without you knowing why. The one-beep calibration confirms your sound path works before any timing happens — no competitor we reviewed does this, and it removes the most common source of bad auditory data.
The median is the middle value of your five valid rounds, so one lucky fast round or one distracted slow round cannot drag the headline score the way it drags an average. The score card still shows your average, best, and spread alongside the median, so nothing is hidden.
A press before the beep plays is a false start, and any response under 100 ms after the beep is also rejected — that is faster than a genuine auditory reaction, so it is anticipation, not response. Both cases retry the round instead of recording a number. At the other end, if 1,000 ms pass with no response, the round is treated as a missed tone: you are asked to check your volume and the round is retried.
Two reasons. Physiology: sound reaches the cortex faster and through fewer relay stages than sight, so laboratory studies find auditory reactions roughly 20–40 ms quicker. Equipment: your audio output and your display add different latencies to the two scores, and Bluetooth audio can add enough delay to erase the natural advantage entirely. The comparison box above the FAQ shows your own visual-versus-auditory gap once you have taken both tests on this device.
Yes — tap the panel instead of clicking. Two phone-specific cautions: on an iPhone the mute (silent) switch silences the beep for many browsers, so flip it off if the calibration beep is silent; and wireless earbuds add the same Bluetooth latency described above, so test on the speaker or wired earphones for a score you can compare over time.
Run the five-round visual reaction time test to compare modalities on the same device, try the spacebar version to isolate input-device latency, check your result against average reaction time references, read the world record fact-check, practice with the 7-day training plan, or read the methodology behind every number on this site.
This tool is not a medical device and not a hearing assessment. It measures browser time between a scheduled beep and your input, which includes audio output latency on top of your response. Latency figures in the table above are order-of-magnitude estimates, not measured guarantees.