Reaction Time Test

Reaction time is the interval between a signal appearing and a response being registered. In this test, the signal is the green stage and the response is one click, tap, or accepted key press.

The displayed number is an end-to-end browser measurement. It combines your visual detection and movement with the time used by the screen, browser, operating system, and input hardware.

This is a simple reaction-time task: one known visual signal calls for one known response. A choice reaction-time task asks the participant to select among different responses depending on the signal.

Choice tasks add decision complexity. Research on Hick's law examines how response time relates to the number of stimulus-response alternatives, while also noting effects from compatibility, practice, and task design.

The tool chooses a cryptographically generated random wait from 1.5 to 5 seconds so the green signal is harder to anticipate.

The ready timestamp is set on the browser's next animation frame, immediately before the green state is presented. The response timestamp uses performance.now(), a monotonic high-resolution browser clock, and the difference is rounded to a whole millisecond for display.

The clock can be precise while the complete measurement still includes presentation and input delays. Precision of the timer is not the same as laboratory accuracy of the full system.

One attempt is only one observation. Attention, anticipation, fatigue, practice, posture, background activity, and ordinary trial-to-trial variation can change the next result.

Compare a small set of attempts made under similar conditions instead of treating one unusually fast or slow value as a stable personal score.

A display updates in frames, so the visual change may appear after the code requests it. Browser scheduling and other work on the device can add variation before presentation or response handling.

Input hardware and its driver also take time to report a mouse button, touch contact, or key press. Controlled research calibrates these paths with external equipment; this everyday browser test cannot measure or remove each device-specific delay.

Mouse, touch, and keyboard inputs travel through different hardware and software paths. They also require different physical movements, so switching methods can change the measured value.

For a useful session comparison, keep the same device, browser, hand, posture, and input method. Treat a change of setup as a new comparison rather than continuing the old one.

After two valid attempts, the stage shows your best result, rounded average, and valid-attempt count for the current page session.

False starts never enter those statistics. Refreshing or closing the page clears the session, so old results do not silently affect a later visit.

Laboratory systems can calibrate stimulus onset and response registration with known displays, dedicated response devices, and external timing equipment. A public browser tool runs across many uncalibrated screens, operating systems, browsers, and input devices.

Use this tool for casual practice and consistent same-device comparisons. Do not interpret it as a clinical assessment, a diagnosis, or a device-independent measure of neurological performance.

Attempts and summary statistics are calculated in the browser and held only in the current page memory. No account is required, and refreshing the page resets the session.

Do not use an informal reaction-time result to make medical, employment, driving-safety, legal, or other high-stakes decisions. Seek an appropriately qualified professional and calibrated assessment when accuracy has real consequences.