Frame Rate Test

Keyboard Latency Test

Measure your keyboard input lag and response time right in the browser.

0.00ms
Processing Lag
Awaiting input
click here to start
Click here, then press keysVisual Lag mode

The amber bar lags the green input bar — the gap is an illustration of input lag.

Min / Max
Jitter (ms)
Consistency
Average (ms)
0Samples

Hardware note:browser-based tests cannot read your keyboard's true hardware scan rate or total system latency. These numbers show event-processing delay measured in the browser, and the operating system controls key auto-repeat. Use them to compare relative responsiveness, not as absolute hardware figures.

This free online keyboard latency test measures the input lag between your keyboard and the browser across three modes — Visual Lag, Event Timing, and Key Latency. Track live processing lag, jitter, consistency, sample count, and an effective event rate, then compare your result against competitive-gaming benchmarks.

Latency is one fault — chatter is another. Check your keys for unwanted double presses with the Keyboard Double-Click Test.

Keyboard Latency Test Guide

What Is Keyboard Latency?

Keyboard latency (input lag) is the delay between physically pressing a key and that press being acted on. It is measured in milliseconds (ms) and determines how responsive your keyboard feels. Lower latency means faster response — important for competitive gaming, fast typing, and rhythm games. This browser tool measures the slice of that delay it can see: the time between an input event being stamped by your system and the page processing it.

What Affects Keyboard Latency?

  • Connection: wired USB is generally faster and more consistent than wireless, and a 1000 Hz gaming keyboard reports more often than a standard one.
  • Switch & debounce: the switch type and the keyboard's debounce delay add a few milliseconds before a press is registered.
  • OS processing: background processes, drivers, and power-saving modes all add delay.
  • Browser: different browsers schedule and process input events at different speeds.

Test Modes Explained

  • Visual Lag: a trailing amber bar lags the green “input” bar — the gap is an illustration of input lag, while the readout shows real event-processing delay.
  • Event Timing: graphs the time between key events. Hold a key down for a steady stream; the tool derives an effective event rate from the interval.
  • Key Latency: measures the processing time for each individual press and plots a histogram of the latencies you record.

Latency Benchmarks

LatencyRating
< 2 msProfessional gaming level
2–5 msGreat for competitive play
5–10 msAcceptable for most users
10–20 msNoticeable lag in fast games
> 20 msMay affect timing-sensitive play

How to Reduce Keyboard Latency

  • Use a wired connection or a low-latency 1000 Hz gaming keyboard instead of a slow wireless link.
  • Connect directly to a USB port and avoid hubs, extenders, and front-panel headers.
  • Update keyboard firmware and drivers from the manufacturer, and lower the debounce delay if your keyboard allows it.
  • Close unnecessary background applications and browser tabs that compete for CPU time.
  • Disable power-saving for USB devices so the keyboard is never throttled.

Browser Limitations

Browser-based tests have inherent limitations compared with dedicated hardware measurement tools:

  • • They cannot read your keyboard's true hardware scan rate — the effective rate is estimated from event timestamps.
  • • Held keys report the operating system's auto-repeat rate, which is not the same as the hardware scan rate.
  • • Results vary based on your browser, operating system, and overall system load.

Frequently Asked Questions

A keyboard latency test measures the input lag between pressing a key and the browser processing that event. This tool reports the event-processing delay in milliseconds across three modes — Visual Lag, Event Timing, and Key Latency — along with jitter, consistency, and an effective event rate.
For browser-measured processing delay, under 2 ms is professional-gaming level, 2–5 ms is great for competitive play, and 5–10 ms is fine for most users. 10–20 ms becomes noticeable in fast games, and above 20 ms can affect timing-sensitive play. Remember these are event-processing figures, not total system latency.
Not directly. Browsers do not expose a keyboard's true hardware scan rate, and a normal key press only fires one event. The Event Timing mode shows the interval between key events — when you hold a key, that reflects the operating system's auto-repeat rate (typically 20–30 Hz), not the hardware scan rate. Treat the effective rate as a relative, browser-level figure rather than a hardware spec.
System load, browser activity, and background processes all affect latency. Each frame the browser has to schedule your key input alongside everything else it is doing, so readings jump around. Close unnecessary programs and tabs and test again for the most stable numbers.
Visual Lag illustrates the gap between a key press and a perceived response while reporting the real processing delay. Event Timing graphs the time between key events and derives an effective event rate — hold a key down for a steady stream. Key Latency plots a histogram of the processing delay measured on each individual press.
It measures browser-level event processing, not total system latency. The figure relies on event timestamps and is affected by your browser, operating system, and system load. For precise end-to-end measurements — from switch actuation to photons on screen — dedicated hardware tools are required.