Reaction Time Test

Understanding the result

What a result means

The result measures time from the page’s visual signal to the received click or tap. Display latency, browser scheduling and the input device are all included, so the number is recreational and not a neurological or medical assessment.

Confirm the pattern by repeating randomized wait before the signal. Results reflect events and values exposed by this browser.

How to use this test

1. Press Start and wait without holding the button.
2. Click or tap only after the panel says GO.
3. Repeat several trials under the same conditions.
4. Compare the average rather than one unusually fast value.

What this test checks

• Randomized wait before the signal
• Latest, best and average response
• False-start detection
• Mouse and touch input

What this test cannot check

Results reflect events and values exposed by this browser.

This test does not certify hardware or replace professional inspection.

Browser scheduling, display latency and input hardware affect the result.

This is recreational and not a medical or neurological assessment.

Common problems and troubleshooting

Discard false starts, use several trials and compare the average under the same display and input conditions. Keep the tab visible and avoid comparing a touch screen with a wired mouse as though only human response changed.

1. Repeat the same observation. Focus the test surface and repeat “Randomized wait before the signal” three times under the same conditions.
2. Change one condition. Compare “Latest, best and average response” after changing only the relevant port, connection, browser setting or application.
3. Rule out focus or interception. Close overlays and reserved shortcuts, keep the page visible and confirm that the live indicator changes during the action.
4. Keep the result within its limit. Results reflect events and values exposed by this browser.

If the same pattern remains across relevant applications and connections, give the manufacturer or a qualified technician the repeatable observations instead of a guessed fault label.

Browser compatibility

High-resolution timers and pointer input are available in current browsers, but background throttling and privacy timer reduction can change precision. The page detects false starts locally and stores no trial history after reload.

“Expected baseline” is an editorial capability expectation, not a completed browser test. The live feature check above is authoritative for this browser and device.

Privacy information

Test values are calculated in this browser. Device Test Bench does not store a test result or create a device fingerprint.

The public analytics allowlist does not accept pressed keys, typed text, pointer coordinates, media labels, device IDs, recordings, video frames or controller input. Test results are not written to LocalStorage.

Primary technical references

These specifications define the browser signals used by this test. They document web-platform behavior; they do not certify a particular device.

• Pointer Events specificationW3C
• HTML animation framesWHATWG

Frequently asked questions