Keyboard & Mouse Tools

Keyboard Latency Test

Run a keyboard latency test and compare repeated event-to-render timing samples in the same setup. This is not an end-to-end hardware latency measurement.

Keyboard timing Animation frame Median and p95
Local by default
Your test data is processed locally in your browser and is not uploaded.
Ready to test

Browser input-to-display timing estimate

Press keys in the active zone. Each sample ends at the next animation frame callback.

Median estimate—
P95—
Range—
0 valid samples

What this page helps you test

This keyboard latency tester estimates the interval from a browser key event to its next visual update. Compare repeated sessions under the same display and load; it does not rank keyboards by hardware latency.

Troubleshooting

If the result is not what you expected

1

Keep focus in the test

Input tests capture events only inside the clearly marked active area.

2

Try a direct port

Reconnect wired devices without a hub and retest the same control.

3

Compare another app

OS shortcuts and browser event filtering can hide otherwise working controls.

Method

How it works

  1. Activate the test and press different keys at a comfortable pace.
  2. Each keydown is paired with the next animation-frame callback.
  3. Review the browser input-to-display timing estimate and sample distribution.
Browser limitations

What this result cannot prove

  • This is not end-to-end keyboard hardware latency.
  • Refresh rate, scheduling, background load, and the operating system affect every sample.
Check browser support
Keep checking

Related tools

Questions

Frequently asked questions

Can this keyboard latency test rank gaming keyboards?

Not reliably. The estimate includes browser scheduling and rendering and misses the time before the browser event. Keep device, display and background load fixed; use it for repeatable observations rather than manufacturer comparisons.

Is the Keyboard Latency Test private?

Yes. Test input is processed in this tab and is not uploaded by this tool.

Why can browser results differ from another app?

Browsers, operating systems, permissions, device routing, and background load can all change what is exposed and measured.