Why Does My Keyboard Feel Slow or Laggy?

Before changing any settings, describe what is actually happening as narrowly as you can. A keyboard where every key is uniformly delayed has a different problem from one where a single key needs a hard press, and both differ from one that types double letters. Fixes for one do nothing for the others. Find your symptom below, then read that section.

First: confirm the keyboard is even involved

Three swaps eliminate most wrong guesses, and they take about five minutes. Do them before you buy anything or reinstall anything.

1. Same keyboard, different computer. If the problem travels with the keyboard, the keyboard, its cable or its receiver is the suspect.
2. Different keyboard, same computer. If the problem stays behind, it is the computer: its software, its input path or its display.
3. Same computer, different application. If only one application is affected, the keyboard is fine.

You can put a number on the second swap: run the browser keyboard latency test with each keyboard on the same machine, at least 30 valid samples each, then load both into session comparison. Remember what that measures — the browser-observed input pipeline, not keyboard hardware. It is a good relative comparison between two setups on one machine, and a poor absolute statement about either keyboard.

Everything is delayed, uniformly — "why is my keyboard delayed?"

If every key is late by roughly the same amount and it never lets up, the cause touches every keystroke equally. In rough order of likelihood:

• The display and frame pipeline. A 60 Hz screen produces a frame every 16.7 ms, and a keystroke waits about half of that on average before the frame that could show it even begins. Games that queue frames ahead add several more frame intervals. This is commonly the largest single contributor, and it is not a keyboard problem at all.
• Sustained CPU load. A saturated machine delays the delivery and handling of every input event. Check the task manager for something running flat out.
• Software in the input path. Remappers, macro tools, vendor suites and overlays sit between the operating system and the application. On Windows, low-level keyboard hooks are handled synchronously, so a hook that is slow to return holds up the keystroke for everything downstream.
• Accessibility filters. Windows Filter Keys and macOS Slow Keys deliberately require a key to be held before it registers, and both are easy to switch on by accident.
• Connection and hubs. A Bluetooth keyboard, or one behind a KVM switch or dock that re-packages its reports, can add a consistent delay.

Next action: take a baseline on the latency test, then work down how to reduce keyboard input lag, which is ordered by expected impact.

It lags in bursts — "why does my keyboard lag sometimes?"

Intermittent lag points at something that comes and goes, not something broken. The pattern of when it happens is your best evidence.

Next action: run the latency test once while the problem is happening and once while it is not. Compare the 95th percentile and the jitter figure rather than the median — intermittent problems live in the tail and can leave the median almost untouched.

Only one key is slow, or needs a firm press

If exactly one key misbehaves and every other key is normal, no system-wide setting explains it — a setting would affect all of them. That narrows the search to the key itself: debris under the keycap, a worn or contaminated switch, or a poor contact in that position.

Next action: open the keyboard key test, press the suspect key normally about twenty times, then do the same with a neighbouring key you trust. You are looking for presses that produce no event at all, or that only register when you press harder. The full keyboard tester sweeps every key at once if you would rather check the whole board.

If presses are being missed, try the physical remedies in order: remove the keycap and clear debris, use compressed air, and on a hot-swappable board move the switch to a position you rarely use. If the fault follows the switch, the switch is the problem; if it stays with the position, the board is.

Keys repeat or double from a single press

Typing "hhello" when you pressed each key once is a distinct fault, and it is not latency. It is one physical press producing more than one event, normally called chatter. It happens when contact bounce outlasts the firmware's debounce window, and it tends to get worse as a switch ages or picks up contamination.

Next action: run the keyboard chatter test and type normally for a minute or two. It flags duplicate events that arrive suspiciously soon after the original — a pattern, not a verdict. If it repeatedly flags one key while the others stay clean, that key is worth attention. What keyboard chatter is covers the mechanism and the usual remedies.

Rule out two things first. If you recently lowered a debounce setting in firmware, put it back up — that trade-off is exactly what you have just bought. And if the "doubling" is really a key repeating while held, that is your operating system's auto-repeat, which the repeat rate test will show you.

Keys go missing when typing fast or gaming

If characters vanish during quick typing, or a movement key stops working while you hold two others in a game, you are running into how many simultaneous keys the keyboard can report — not a speed problem. Cheaper matrices can only distinguish a limited number of combinations, and some specific combinations block each other outright.

• Losing specific combinations, reproducibly, points at ghosting or a matrix limit: test it with the ghosting test.
• To find how many keys register together at all, use the n-key rollover test.
• If characters drop during ordinary fast typing with no chords involved, suspect the application instead — see one application.

Both tests report what your browser registered, which is the right level for "the game is not seeing my key", but a browser cannot confirm a keyboard's hardware rollover specification. Ghosting vs key rollover explains why the two get confused.

A key sticks, or stays held after you let go

A stuck key shows up as a character repeating endlessly, a modifier that seems permanently held, or a game character that will not stop walking. A physical stick is the keycap or stem binding, and you can usually feel it. A logical stick is the key-up event never arriving, so the computer still believes the key is held.

Next action: the stuck key test shows which keys the browser currently believes are held. If a key stays listed after you release it, that is a logical stick; tapping it again often clears it. If it recurs, see how to test for and fix a stuck key.

It only happens in one application

If a single program feels slow and everything else on the same machine is crisp, the keyboard is not the problem. This is the easiest branch to resolve and the easiest to waste money on if you skip it.

Common culprits: autocomplete or linting that runs on every keystroke in code editors, very large documents, spreadsheets recalculating on each entry, and chat or game clients doing background work. In games, check the frame rate and any VSync or frame-queueing setting before blaming input.

Next action: type in a plain text editor. If that is fine, take the problem to the slow application's settings — turn off live spell-check, live preview or autocomplete and re-test.

Only after waking from sleep, or only on battery

Power management is the explanation when the symptom is tied to a power state rather than to what you are doing.

• Only the first press after an idle period is slow. The USB port or the wireless device has been allowed to sleep and has to wake. On Windows, USB selective suspend is the setting to look at.
• Everything is slower on battery than on mains. The power profile is lowering clock speeds and allowing deeper idle states, which raises scheduling latency. Switch to a balanced or high-performance profile and re-test.
• Only after resuming from sleep, until you reboot. Usually a driver or an input-path utility that did not resume cleanly; unplugging and replugging the keyboard or its receiver is a quick confirmation.

Next action: run the latency test on battery and again on mains without changing anything else. If the medians differ noticeably, you have your answer.

Typing in a web page feels laggy, but nowhere else

Something in the browser is doing work on every keystroke, and there are three candidates. Extensions — grammar checkers, password managers, clippers, translators and heavily configured content blockers — attach handlers that run as you type. The page's own JavaScript, such as a rich text editor that re-renders on each character, can add tens of milliseconds by itself; if the lag is confined to one site, that is your answer. And a background tab with a runaway script can slow typing across the whole browser.

Next action: the latency test reports the gap between the browser creating a keyboard event and JavaScript handling it, which is precisely the gap that main-thread work stretches. Take one run with extensions on and one with them off, then compare in session comparison. Browser keyboard event timing explains what happens in that window.

If none of these match

Run the keyboard performance test, which sweeps latency, consistency, key detection, chatter and rollover in one pass. If that report is clean and the keyboard still feels wrong, the problem is most likely downstream of the keyboard — display refresh, frame queueing, or an application — and how to reduce keyboard input lag covers those in order of impact.