Keyboard Latency Test
Check how long your browser waits between handling a key press and its next animation frame. This is a browser timing check, not a hardware latency measurement.
Your timing session
Start the test, then press individual keys.
Tab or Esc to leave the test
Session summary
Last 100 samplesUp to 24 samples · bars scale to the largest value
Measures the wait from a browser key event to the next animation frame. USB, Bluetooth and display latency are outside this measurement.
What this test measures
The timer starts inside the browser’s keydown handler and ends in a requestAnimationFrame callback. The callback runs before a repaint. The number is therefore a measure of browser scheduling delay, not the time from switch actuation to a visible pixel on your display.
USB polling, Bluetooth transmission, switch debounce and operating-system delivery happen before this timer starts. Display processing and pixel response happen after it ends. A website cannot use this method to measure either part. See the requestAnimationFrame documentation.
How to run the test
- Keep the tab visible and click the test area.
- Press individual keys at a normal pace. Avoid holding a key down, because key repeat is a separate behavior.
- Take several samples and compare the average with the best and worst values.
- Close busy tabs or background apps, then repeat under the same conditions.
The statistics use the most recent 100 samples. Keep the computer, browser, display refresh rate and power settings the same when comparing sessions. Changing keyboards alone does not make this a reliable hardware comparison.
How to interpret the numbers
A 60 Hz display has a frame interval of roughly 16.7 ms; at 120 Hz, it is roughly 8.3 ms. Your result depends on when a key arrives within that cycle and whether the browser is busy. A small result can simply mean the event arrived just before the callback.
Occasional larger samples may indicate browser or system load. There is no universal pass/fail threshold here, and a low number does not prove that a keyboard has low hardware latency.
If typing feels delayed
First check whether the delay occurs in another app. Reconnect the keyboard, charge wireless devices and try a direct USB port. Close demanding applications and check whether the system is in a power-saving mode.
Bluetooth interference can affect input delivery, but this test starts after the browser receives that input. Network delay matters for remote desktops and online services; your router does not directly set the response time of a local USB keyboard. Keyboard repeat delay controls held-key repetition rather than the initial press.
If a key is missing entirely, use the keyboard tester. If keys disappear only when held together, use the rollover test. For persistent problems, follow the keyboard troubleshooting guide.
Measuring hardware latency
A hardware measurement needs a known actuation time and a way to observe the keyboard’s output or the display response. Dedicated electrical or optical test setups can do this; this browser tool does not replace them.
Privacy
The test processes input on this page. It does not send your key presses to our server. Advertising and embedded media are described separately in the privacy policy.