Output
Event-to-animation callback time, milliseconds
UserBenchmark / All Tools / Keyboard Event Latency Test
Keyboard
Keyboard Event Latency Test
Measure keyboard event-to-next-frame delay inside the browser.
Free to useNo downloadNo sign-up
Keyboard Event Latency Test · At a glance
Quick answer: Measure keyboard event-to-next-frame delay inside the browser. The interval ends at the next animation callback after event handling.
Keyboard Event Latency Test
The test loads when you open it. Device access is requested only after you choose to start.
Detailed guide
How to use this tool
- Focus the surface, press an ordinary key and repeat several samples.
- Keep the same display mode for comparison.
Input
Clicks or focused key presses
Browser requirement
requestAnimationFrame; performance timestamps
Processing
Runs on your device; no tool-result upload
How it works and what the result means
The number measures time from handling the browser input event to the next animation frame callback. It does not measure USB hardware latency, switch actuation or actual photon response.
Reading the result
The interval ends at the next animation callback after event handling. It does not include actuation travel, USB polling or physical display response.
What to check next
Avoid shortcuts that change focus. Power saving and a busy main thread can increase the observed scheduling delay.
Frame scheduling, tab visibility and system load affect the result. Compare the median under the same conditions and avoid treating this number as end-to-end input lag.
Frequently asked questions
Can I compare keyboard switch latency with this number?
This browser interval cannot isolate switch hardware. A controlled external measurement is needed to compare physical actuation-to-output latency.
How do I start the Keyboard Event Latency Test?
Click the test surface or press a key, depending on the selected test. Repeat for several samples.
Does this tool require a download or an account?
No. Open the interactive tool above in a modern browser. The instructions and explanations are available even with JavaScript disabled; running a test needs JavaScript.
Why can two attempts give different results?
Power settings, background tasks, browser scheduling, operating-system input processing and device settings affect measurements. Compare repeated attempts with identical settings rather than the single highest score.