A reaction time calculator is two things joined together. The first is a measurement: how long it takes you to notice a signal and produce a physical response. The second is a conversion: at a given speed, that delay corresponds to a distance covered before anything you do has any effect. The second half is why the first half matters outside a psychology lab.
Arb Digital publishes this in a free tools library that covers physics, measurement and everyday conversions. The physics here is trivial — distance equals speed multiplied by time — but the input is not, because most people badly underestimate their own delay and have no reference point for what a quarter of a second costs at road speed.
What This Reaction Time Calculator Does
The test presents a prompt that changes at a random moment between about one and four seconds after you arm it. You press again as soon as you see the change, and the interval is recorded. Five trials are collected and averaged, because a single trial is dominated by noise — anticipation, distraction, and the moment you happened to blink.
Your average is written into the reaction time field, and everything below it recalculates. Enter a speed in miles per hour, kilometres per hour or metres per second, and the tool reports the distance covered during that reaction in both metres and feet. The optional extra-delay field adds any mechanical or system lag that sits between your decision and the effect, which is how the figure is used in practice.
The boundary with the closest tool on this site is clean and worth knowing. The stopping distance calculator takes a reaction time as a typed input and adds braking distance to produce a total stopping distance. This page measures the reaction time itself and converts it into the reaction component alone. They are designed to be used together: measure here, then take the figure across.
How to Use It
- Press the button to arm a trial. The prompt will change after an unpredictable delay of one to four seconds.
- Press again the instant it changes. Pressing before it changes voids that trial, which is deliberate — anticipation is not reaction.
- Complete all five trials. The average is the useful number; individual trials scatter far more than people expect.
- Set the speed. The conversion is linear, so doubling the speed doubles the distance for the same reaction.
- Add any system delay if it applies. Brake system lag, machinery response and relay time all sit after the human part and before the effect.
The Formula and How It Is Calculated
Distance is speed multiplied by time, with the units made consistent first. One mile per hour is 0.44704 metres per second, and one kilometre per hour is 0.27778 metres per second, so the calculator converts the entered speed to metres per second and multiplies by the reaction time in seconds.
Worked example. At 60 miles per hour a vehicle is travelling 60 × 0.44704 = 26.82 metres per second. A reaction time of 250 milliseconds is 0.25 seconds, so the distance covered before anything happens is 26.82 × 0.25 = 6.71 metres, or 22.0 feet. Add 200 milliseconds of brake system lag and the total becomes 0.45 seconds, or 12.07 metres — nearly forty feet, and not a single one of those feet involves the brakes doing anything.
The linearity is the important property. There is no threshold, no curve and no diminishing effect: at 30 mph the same quarter second costs 3.35 metres, and at 70 mph it costs 7.83 metres. Reaction distance scales exactly with speed, while braking distance scales with the square of speed, which is why the two components behave so differently and why the stopping distance calculator keeps them separate.
What the Research Says a Normal Reaction Time Is
Simple visual reaction time — the exact task this test performs, where one signal calls for one known response — has been measured extensively. A large study published in Frontiers in Human Neuroscience on the factors influencing the latency of simple reaction time, covering 1,469 participants aged 18 to 65, reported a mean of 231 milliseconds, or 213 milliseconds once the delays introduced by the measuring hardware were corrected for. A replication with 189 participants aged 18 to 82 produced about 238 milliseconds.
That hardware correction is the reason for the caution note above this article. The same study found that a large part of the variation between published figures came from measurement equipment rather than from people, and a web browser is a considerably less controlled environment than the calibrated apparatus used in that work. Your figure here will run somewhat high for that reason alone.
Age matters, and less than folklore suggests. The same research found reaction time increased by about 0.55 milliseconds per year of age, while the perceptual component of the task was unaffected — the slowing is in producing the movement rather than in seeing the signal. A separate analysis of two large cohorts on age-associated variation in visual reaction time performance found a curvilinear relationship, with the rate of slowing increasing in later decades.
Why a Simple Test Understates a Real One
The test on this page is the easiest reaction task that exists. You know what the signal will be, you know where it will appear, you know what response is required, and you are actively waiting for it. Every one of those conditions is absent in the situations where reaction time actually matters.
A choice reaction task — where the correct response depends on which of several signals appears — is consistently slower, because a decision has been inserted between perception and movement. A task where the signal is unexpected and the response is unpractised is slower again. This is why traffic engineering uses figures far larger than any laboratory measurement: highway design conventionally allows around 2.5 seconds of perception and reaction for an unexpected event, which is roughly ten times what this test will report, and it is chosen deliberately to cover the great majority of drivers rather than a typical one.
The gap between those numbers is not a contradiction. They measure different things: this page measures the floor of human response under ideal conditions, and design standards use a figure covering the realistic worst case. Neither is the "true" reaction time, and using the wrong one for the wrong purpose is the mistake.
What the Browser Is Actually Timing
Between the moment a display changes and the moment your click is recorded, several delays accumulate that have nothing to do with you. The screen has a refresh interval — 16.7 milliseconds at 60 Hz — and the change becomes visible only at the next refresh. The panel has its own response time. The mouse or touchscreen samples at a fixed rate. The browser dispatches the event on its own schedule.
Together these typically add somewhere in the region of 30 to 80 milliseconds, and they are consistent for a given setup. That consistency is what makes the test useful in spite of the offset: comparing your own attempts on the same machine is meaningful, comparing your figure with someone else's on different hardware is not, and comparing either with a published laboratory figure is not either.
If you want to see the offset for yourself, run the test on a phone and on a desktop with a high refresh rate monitor. The difference between the two is mostly equipment, not you. The same principle applies to any browser-based measurement, including the typing speed test, where the input path adds its own consistent overhead.
Using the Figure for Machinery and Sport
Vehicles are the obvious application but not the only one. Any situation where a human response is followed by a mechanical one has the same two-part structure, and the extra-delay field exists for exactly that. A machine guard that stops in 300 milliseconds, a relay with a 50 millisecond pick-up time, or a hydraulic system with a lag all add to the human component, and the total is what determines the distance or the exposure.
In sport the same arithmetic sets the limits of what is possible. A ball travelling at 40 metres per second covers 10 metres during a 250 millisecond reaction, which is why players at that level are responding to the delivery action rather than to the ball itself — there is not enough time for the simple reaction the test on this page measures. For converting between the speed units involved, the speed converter handles the arithmetic, and the meters to feet converter handles the distances.
Arb Digital's free tools library covers speed, distance, unit conversion and timing calculations across hundreds of tools, and our team is happy to talk through anything the tools cannot answer.
Browse Free Tools Talk to Arb DigitalCommon Mistakes to Avoid
- Judging yourself on one trial — individual attempts scatter widely, and only an average across several is meaningful.
- Comparing your figure with a laboratory result — browser measurements carry a consistent hardware offset of several tens of milliseconds.
- Using a simple reaction time for an unexpected event — real situations involve a choice and are far slower, which is why design standards use much larger figures.
- Forgetting the mechanical delay — the human part is only the first component, and brake or machine lag adds to it before anything moves.
- Treating reaction distance as stopping distance — reaction distance scales with speed, braking distance scales with speed squared, and the total needs both.
Related Free Tools From Arb Digital
Take your measured figure to the stopping distance calculator to add the braking component, use the speed converter to move between speed units, the meters to feet converter for the distance side, and the typing speed test for a different browser-based measurement of the same input path. Everything else is in the free online tools hub.
Frequently Asked Questions
Published research on this exact task reports a mean of about 231 milliseconds across nearly 1,500 adults, or 213 milliseconds once measurement hardware delays are corrected for. Browser-based tests generally read higher than that.
Because the measurement includes your display refresh interval, panel response, input sampling and event dispatch. Together these commonly add several tens of milliseconds, consistently, on top of your actual response.
Because anticipating the signal is not reacting to it. The delay before the prompt changes is randomised specifically so that guessing cannot produce a fast result.
Distance is speed multiplied by time. At 60 miles per hour a vehicle covers 26.82 metres per second, so a 250 millisecond reaction corresponds to 6.71 metres, or about 22 feet.
Because they cover unexpected events requiring a decision, not a signal you are actively waiting for, and they are set to cover the great majority of drivers rather than a typical one. Around 2.5 seconds is the conventional design allowance.
Research on large cohorts finds it does, at roughly half a millisecond per year, with the rate increasing in later decades. The same work found the perceptual part of the task largely unaffected, with the slowing occurring in producing the movement.
Any lag that sits between your response and its effect — brake system response, machine stopping time, relay pick-up. It is added to the human component because the total is what determines the distance covered.
This tool measures a response in a web browser and performs a distance conversion. It is not a clinical or occupational assessment of any kind, the measurement includes hardware delays outside your control, and it should not be used to judge fitness to drive or to operate anything.
