Keyboard Latency Test - Find and Fix Your Keyboard Input Delay

Press any key to see your keyboard's input latency split into delivery lag and processing lag. Lock a custom baseline or compare against wired, wireless, and Bluetooth benchmarks to measure the impact of any change.

Best Used on a Desktop With a Physical Keyboard.
Loading…
1-5ms
Typical Wired Gaming Keyboard
5-15ms
Most Keyboards in Good Range
10-30ms
Typical Bluetooth Addition
100%
Free - No Sign-Up Required
0
Data Sent to Any Server
What It Measures

What This Test Actually Measures (And What It Does Not)

Most keyboard latency tools online are vague about this. Being precise about what browser-based measurement can and cannot capture makes your result far more useful.

What "Latency" Actually Means Here

This tool measures the time between when the operating system timestamps a keydown event and when the browser's JavaScript engine processes it. This is the OS-to-browser processing delay, representing the portion of input lag that reflects your keyboard's polling rate, USB transmission efficiency, OS scheduling overhead, and browser event handling speed combined. It is sometimes called the software latency layer, and it is the component of the full input chain most directly affected by your keyboard hardware choice and system configuration.

What It Cannot Measure

True hardware-level USB polling latency (the delay between switch actuation and USB packet transmission) requires a USB protocol analyzer or oscilloscope. No browser-based tool can directly read this. Similarly, display latency (the time from GPU output to pixel on screen) and game engine tick latency are outside what JavaScript can observe. What this tool gives you is real, useful data about one important layer of the input chain. While it is not a substitute for hardware measurement, it provides a genuinely informative relative benchmark.

Why Jitter Often Matters More Than Average

Two keyboards can have the same average latency of 8ms but feel completely different to use. If one keyboard always delivers events within 6 to 10ms (2ms jitter) while another fluctuates between 3ms and 20ms (17ms jitter), the second one feels unpredictable, especially in fast gaming or high-speed typing where your muscle memory has learned to compensate for a consistent delay but cannot adapt to a variable one. Low jitter is what makes a keyboard feel reliably responsive, not just fast on average.

The Full Input Chain and Where This Fits

Your complete input chain runs from switch actuation to USB polling, OS processing, application tick, GPU render, and monitor display. This test captures the middle segment, which includes USB polling, OS processing, and browser event handling. At 1000 Hz polling rate, the USB segment alone contributes up to 1ms. The OS processing layer typically adds 0.5 to 5ms. Browser overhead adds another 0.5 to 10ms depending on system load. Understanding which layer is contributing the most to your result tells you exactly where an improvement effort will have the most impact.

The Right Way to Use This Test

The most valuable use is relative comparison. Test your keyboard as it currently is, make a change (plug into a different USB port, switch from Bluetooth to 2.4GHz, close background applications, change polling rate), then test again. The difference between the two averages and jitter scores is your objective, quantified measurement of the impact of that change. This kind of before-and-after comparison extracts real information from a browser-based test and sidesteps the limitations of absolute measurement.

When Keyboard Lag Actually Affects You

For most typing and everyday use, latency below 30ms is imperceptible. The situations where it matters are fast-paced games (CS2, Valorant, osu!, rhythm games) where the game engine processes inputs on short tick cycles, and high-speed typing above 80 WPM where the delay between a keypress and the character appearing creates a disconnect that makes self-correction difficult. You can check your raw keystroke rate with our keyboard CPS test. If your keyboard feels sluggish in everyday use, background processes and system load are almost always the cause, rather than the keyboard hardware itself.

Contributing Factors

What Actually Determines Your Keyboard's Input Delay

Latency is never caused by a single component, but is the sum of contributions from several places in the input chain. Here is each one and how much it typically contributes.

Keyboard Polling Rate

Polling rate controls how often your keyboard reports its state to the computer. At 1000 Hz, it reports once per millisecond, meaning the maximum additional delay from polling is 1ms. At 125 Hz, that maximum is 8ms. On average, polling contributes half the interval value, which is 0.5ms at 1000 Hz and 4ms at 125 Hz. This is why upgrading from 125 Hz to 1000 Hz saves roughly 3.5ms on average, which is a real but modest improvement. Verify yours with our keyboard polling rate test.

Connection Type

Wired USB is the baseline, and all other connection types add delay relative to it. A 2.4GHz wireless dongle at 1000 Hz, like those used by Logitech Lightspeed or Razer HyperSpeed keyboards, adds 1 to 3ms over wired. Bluetooth HID adds 10 to 30ms because Bluetooth uses a slotted radio protocol optimized for efficiency rather than speed. For gaming or fast typing, wired or 2.4GHz at 1000 Hz delivers the most consistent results.

OS Scheduling and CPU Load

The operating system processes USB HID reports in interrupt-driven code, but the delivery of those events to applications still runs through the scheduler. When the CPU is heavily loaded, OS scheduling delays add jitter to input event delivery, which you will see as wider variance in your latency readings across a 50-sample session. This is why closing background applications before testing produces meaningfully cleaner results, and why gaming with heavy background processes feels worse than the hardware alone would suggest.

Browser and JavaScript Event Loop

Browsers process input events in their JavaScript event loop, which shares CPU time with rendering, JavaScript execution, and network operations. A loaded browser tab, heavy script execution, or heavy visual animations all introduce event loop delays that show up as increased latency in this test. The cleanest results come from running the test as the only active tab in a browser window with no extensions. Chrome and Edge generally show slightly better event timing than Firefox for this type of measurement.

Keyboard Scan Rate vs Polling Rate

These two terms are related but distinct. The keyboard's scan rate is how fast its internal controller reads the key matrix to detect which keys are pressed, typically 1000 Hz on gaming keyboards and sometimes higher. The polling rate is how often the keyboard then reports to the computer via USB. Both affect latency, so a keyboard with a 1000 Hz scan rate and a 1000 Hz polling rate delivers the fastest possible end-to-end detection. Some keyboards scan faster than they poll, and this extra scan speed helps with accurate detection at high key-press rates but does not reduce reporting latency beyond the polling interval.

Keyboard Firmware Debounce

Every keyboard includes a firmware debounce delay, which is a brief window after a keypress during which additional signals from the same switch are ignored. This prevents contact bounce from registering as double keypresses. Most keyboards default to 4 to 8ms of debounce time. Increasing this to 12ms, a common fix for switch chatter, adds up to 4ms of additional latency. The trade-off between eliminating double inputs and minimising delay is worth understanding if you are tuning a keyboard's firmware. If you are experiencing key chatter, our keyboard double typing test identifies which specific keys are affected.

How to Use It

Getting Results You Can Act On

The test runs the moment you start pressing keys inside the zone. These habits give you data that is reliable enough to make real decisions from.

01

Minimise Background Activity First

Close other browser tabs, pause cloud sync, and stop any downloads or antivirus scans before running the test. System load from background processes adds variability to OS scheduling, which shows up as higher jitter in your results. For a clean baseline that reflects only your keyboard and connection, test with the system as idle as possible.

02

Press Any Key Globally

You do not need to click inside a text box. The tool captures keypresses globally on this page. Simply press any key to immediately register a latency sample. The container highlights in yellow on each keypress to confirm that the input has been processed successfully.

03

Press Keys Continuously at a Natural Pace

You do not need to press a specific key or at a specific speed. Press any key, or multiple keys in sequence, at your natural typing pace. The tool measures each keydown event independently regardless of which key it is. Aim for the 50-sample default before drawing any conclusions about average or jitter, as fewer samples give less reliable statistics.

04

Read Jitter Alongside Average

Your jitter score (shown as standard deviation in ms) is the most useful single number for gaming and competitive typing. Under 3ms is excellent. 3 to 8ms is typical for quality wired keyboards. Above 10ms suggests system load is interfering. The stability score summarises this: 95 and above means your latency is stable and predictable, while below 80 means it varies enough to affect feel during fast input.

05

Run Before and After a Change

The test's highest practical value is comparison. Run a full 50-sample session, note your average and jitter, make one change (USB port, connection type, background load), then run again. The difference in the two averages is an objective measurement of what that change actually did, which is far more reliable than trying to judge by feel alone.

06

Test Different Ports and Connections

Plug your keyboard directly into a rear USB port on your motherboard's back panel rather than a USB hub. Hubs and extension cables add extra routing layers that can increase latency jitter. For wireless keyboards, keep the 2.4GHz receiver close to the keyboard to prevent radio interference from causing lag spikes.

Reduce Input Lag

How to Lower Your Keyboard's Input Delay

Ordered from the most impactful and easiest to the most involved. Start at the top, as most people see the largest gains without touching any hardware.

01

Plug Directly Into a Rear USB Port

USB hubs, especially unpowered or front panel hubs, can cap your keyboard at 125 Hz and introduce additional jitter. Connecting directly to a rear motherboard USB port bypasses this limitation entirely. This is the single most common cause of unexpectedly high latency in this test, and it costs nothing to fix. After making the change, reset the test and run another 50 samples to confirm the improvement.

02

Set Polling Rate to 1000 Hz

Many keyboards ship at 500 Hz by default. Open your keyboard's companion software (Logitech G HUB, Razer Synapse, SteelSeries GG, Corsair iCUE) and confirm the polling rate is set to 1000 Hz. This reduces the polling interval from 2ms to 1ms, saving up to 1ms of reporting delay. Verify the change with our keyboard polling rate test before drawing conclusions from the latency test.

03

Switch From Bluetooth to Wired or 2.4GHz

Bluetooth adds 10 to 30ms of latency compared to wired connections, plus significantly more jitter. If your keyboard supports both Bluetooth and a 2.4GHz dongle, always use the dongle for gaming or fast typing. If you are testing over Bluetooth and seeing 30ms+ results, this is expected because the connection protocol, not the keyboard, is the bottleneck.

04

Enable Windows Game Mode and High-Performance Power Plan

Windows Game Mode allocates more CPU resources to the foreground application and reduces background process scheduling interference. Setting your power plan to High Performance prevents the CPU from clock-speed throttling, which removes a source of variable latency under load. Both settings are in Windows Settings and cost nothing to enable. Together they typically reduce jitter noticeably in browser-based latency tests.

05

Close Background Applications

Antivirus scans, cloud backup, browser sync services, and video conferencing apps idling in the tray all consume CPU scheduler cycles. These appear in latency tests as irregular high latency spikes, which are events that arrive much later than usual because the scheduler was briefly occupied. Closing background applications before testing and gaming reduces jitter without any hardware changes. The consistency score in this test will show you the improvement immediately.

06

Update Keyboard Drivers and Firmware

Outdated keyboard firmware can include suboptimal debounce timing or USB communication code that has since been corrected. Check your keyboard manufacturer's website for firmware updates and run them before testing for a baseline. Similarly, keeping USB host controller drivers current, through Windows Update or your motherboard manufacturer's site, ensures your system is handling HID events with the most efficient code available. If a firmware update changed your debounce settings and you are now experiencing repeated keypresses, our keyboard double typing test can confirm whether chatter is still the cause.

Honest Assessment

What This Test Is Good For and Where Its Limits Are

Knowing what a tool can and cannot measure makes every result more useful, not less.

What This Test Does Well

  • Measures OS-to-browser processing delay accurately and consistently
  • Captures jitter and consistency, which is often more informative than average alone
  • Excellent for before/after comparisons on the same machine
  • Identifies whether background load is causing event delivery delays
  • Works across all keyboard types including wired, wireless, membrane, and mechanical
  • Reveals the practical effect of polling rate changes and USB port differences

What This Test Cannot Do

  • Measure raw USB polling latency because that requires hardware tools
  • Isolate keyboard hardware latency from OS or browser contributions
  • Measure display latency or GPU render pipeline delays
  • Provide results comparable to professional hardware testing labs
  • Detect switch actuation timing or mechanical response speed
Benchmark Guide

What Your Result Means in Practice

These ranges reflect browser-measured OS-to-browser latency on a reasonably clean system, rather than raw USB hardware specs. Use them as relative context, not absolute verdicts.

Average LatencyLevelTypical SourceWho Notices
1-8msExcellentHigh-polling-rate wired keyboard, clean system, low browser loadCompetitive gamers, professional typists, osu! and rhythm game players
8-15msGoodStandard wired keyboard at 1000 Hz, well-maintained systemMost users in this range will not perceive any lag during normal use
15-25msAcceptableKeyboard at 500 Hz, 2.4GHz wireless, moderate background loadNoticeable to experienced gamers in fast-paced FPS games, but imperceptible for typing
25-40msElevatedBluetooth keyboard, heavy system load, 125 Hz polling, USB hubPerceptible to most users during fast gaming, which may affect rhythm at 80+ WPM typing
40ms+InvestigateBluetooth with congestion, extreme system load, old keyboard driversClearly noticeable lag, making it worth diagnosing causes before accepting the result

Important Context

Results above 25ms in this browser test do not necessarily mean your keyboard hardware is slow. System load from other processes, running this test in a background tab, or using a browser with heavy extensions all inflate the measurement. Always test with minimal background activity and a focused browser window before concluding that a hardware change is needed.

FAQ

Frequently Asked Questions

Clear, technically honest answers to what people actually ask about keyboard latency and how to measure it.

The tool captures the timestamp that the browser assigns to each keydown event and compares it to the actual time the JavaScript event handler runs. The difference is the OS-to-browser processing delay, which is the combined result of your keyboard USB polling rate, OS input scheduling, and browser event loop timing. This is not the same as raw USB polling latency, which requires a hardware USB analyzer, but it reflects your practical end-to-end input experience in a browser environment and is directly useful for comparing keyboards or system configurations against each other.
Not necessarily. Browser-measured latency includes system load, background processes, and browser overhead, not just keyboard hardware. Before concluding the keyboard is the bottleneck, run the test with all background applications closed and your power plan set to High Performance. Many users who initially test at 20 to 30ms drop to 8 to 12ms simply by closing a cloud sync application or browser tab that was consuming CPU scheduler time. If latency remains high after minimising system load, the keyboard hardware or connection type is more likely the actual cause.
Theoretically achievable in hardware tests with the right equipment, yes, as some keyboards at 8000 Hz polling rate produce USB report delays under 0.2ms. In browser-based measurement, consistent sub-1ms results are uncommon because the OS and browser overhead alone typically contribute 1 to 5ms. As for whether it matters, the difference between 1ms and 5ms average latency is imperceptible to any human. The competitive advantage of ultra-low latency keyboards is real but modest, and it only becomes relevant once your gaming setup has already been optimised in every other respect. For most people, the difference between a 1000 Hz wired keyboard at 5ms and an 8000 Hz keyboard at 0.5ms is not something that will affect their play.
Bluetooth HID (Human Interface Device) was designed for general-purpose peripherals with an emphasis on low power consumption rather than low latency. It uses a slotted polling protocol where the device and receiver coordinate communication on fixed time slots, and this architecture introduces 10 to 30ms of latency compared to wired connections, plus more jitter due to radio-frequency factors. If your keyboard supports both Bluetooth and a 2.4GHz USB dongle, switching to the dongle will dramatically reduce this latency, as most gaming-grade 2.4GHz implementations stay within 1 to 5ms of wired performance.
The scan rate is how frequently the keyboard controller reads the key matrix to detect which keys are pressed. The polling rate is how often the keyboard then reports its state to the computer via USB. Both are measured in Hz, and both affect latency but in different ways. A 4000 Hz scan rate means the controller checks for new keypresses 4,000 times per second, which reduces the delay in detecting a physical press. A 1000 Hz polling rate means it reports to the computer 1,000 times per second. For practical input lag, the polling rate matters more for how quickly a detected keypress reaches the OS. Most gaming keyboards now match or exceed their polling rates with their scan rates, but budget keyboards sometimes have high scan rates with lower polling rates, such as 1000 Hz scan and 125 Hz polling, which creates a performance bottleneck. You can verify your actual polling rate at any time with our keyboard polling rate test.
The input latency test measures your total response time, which is the combined time from a visual signal appearing on screen to your click or keypress registering. This includes your biological reaction time, which typically accounts for the vast majority of the result, usually between 150 and 300ms. This keyboard latency test focuses specifically on the hardware and system processing side, measuring how quickly the keyboard event travels from physical press to browser registration. The two tests are complementary, with the keyboard latency test telling you about hardware and system performance, while the input latency test tells you about your total response loop including your own reaction speed. To isolate your biological reaction time directly, our reaction time test removes hardware variables from the equation entirely.
For the best performance, plug directly into a rear motherboard USB port. USB hubs, especially unpowered or older ones, can reduce your keyboard effective polling rate to 125 Hz even if the keyboard is capable of 1000 Hz. Front-panel USB ports on desktop cases are connected to the motherboard through an internal header and sometimes introduce additional latency or polling rate caps depending on the motherboard and case design. If you are getting higher latency than expected, try a different port as the first diagnostic step because it is free, immediate, and resolves a surprisingly large number of cases.
At typical latencies below 30ms, the effect on typing accuracy is minimal for most people. The typing cadence of even fast typists at 80 WPM involves keypress intervals of roughly 150ms, which is far longer than the latency difference between a fast and slow keyboard. Where latency becomes relevant for typists is jitter. If the delay between keypresses and characters appearing on screen is inconsistent, your visual feedback loop breaks down at high speeds, making error detection and correction harder. For competitive typing at 100+ WPM, consistent low-jitter response is more important than absolute low latency. If you want to benchmark your actual typing speed once your system latency is optimised, our typing speed test measures your WPM and accuracy under consistent conditions.
Yes, it is fully free with no account, no sign-up, and no daily limit. Everything runs entirely in your browser and no key event data is ever sent to any server.