Mouse & Keyboard Tester

Why test your keyboard and mouse in the browser?

When a key stops responding or a mouse button behaves erratically, the first instinct is often to blame the software — the game, the text editor, the operating system. But before spending time reinstalling drivers, updating firmware, or adjusting settings, it is worth establishing whether the problem is actually in the hardware. A browser-based tester operates at a different layer than most applications: it listens directly to the browser's keyboard and pointer event APIs, which in turn sit very close to the OS input stack. If a key fails to register in the browser tester, it is almost certainly a hardware issue. If it registers fine here but misbehaves in a specific application, the problem is likely software-side.

Another practical use case is testing a new device before the return window closes. Buying a keyboard or mouse online and unboxing it carries real risk: dead keys, inconsistent switches, and side buttons that do not register properly are all legitimate defects that sometimes slip through quality control. Running this tester within the first few days of receiving a new peripheral gives you a complete picture of its condition before you have any difficulty returning or exchanging it. It takes about two minutes to press every key, click every mouse button, and scroll the wheel — a worthwhile investment given the alternative of discovering a dead key six months later.

The tester also works well in shared environments — office computers, school labs, libraries — where you may not have permission to install diagnostic software. Because it runs entirely in the browser with no installation required, it is available anywhere you have a browser and can access the site.

Keyboard tester

The keyboard tester renders a full keyboard layout in the browser and listens for keydown and keyup events. Every key press lights up the corresponding key on the virtual keyboard — including Fn keys, media keys, and modifier combinations.

The visual approach matters because it makes anomalies immediately obvious. If you press every key from A to Z in order and one does not light up, you have confirmed a dead key with no ambiguity. If a key lights up but does not clear when you release it — staying highlighted indefinitely — you have a stuck or shorted switch. If a key lights up twice in rapid succession from a single press, the switch is chattering (also called bouncing), which is a form of mechanical wear in physical switches.

Key rollover, n-key rollover, and ghosting

Most people are unaware that the number of keys a keyboard can correctly register simultaneously is not unlimited. Standard USB keyboards using the HID (Human Interface Device) protocol are typically limited to six simultaneous non-modifier key presses — a limit called 6-key rollover (6KRO). Modifier keys (Shift, Ctrl, Alt, Meta) are handled on a separate channel and do not count toward this limit, which is why typing with Shift held is not affected.

When more keys are pressed than the keyboard supports simultaneously, one of two problems can occur. The first is that excess keypresses are silently dropped — you press six keys and add a seventh, and the seventh simply does not register. The second, more troubling problem is ghosting: a phantom keypress is registered for a key that was never physically pressed. Ghosting is a consequence of how the keyboard's internal matrix scanning circuit works. In a matrix layout, each key is at the intersection of a row and a column wire. Pressing multiple keys in the same row/column region can create an ambiguous electrical signal, and the keyboard firmware may misidentify which key was pressed.

N-key rollover (NKRO) means the keyboard can correctly register every key pressed simultaneously, with no upper limit on the count. Gaming keyboards frequently advertise NKRO as a feature because it matters for games that require holding many keys at once — sprinting, crouching, reloading, and looking left in an FPS game might require four or five keys simultaneously. The browser tester lets you verify rollover behavior by pressing multiple keys at once and checking whether all of them appear in the highlighted key map. If some disappear or a key you did not press appears, your keyboard is experiencing ghosting at that combination.

Note that NKRO often requires USB HID mode rather than Boot mode. Some keyboards switch between these modes, and Boot mode imposes a 6KRO limit regardless of the hardware's capability. If you are testing a gaming keyboard and seeing dropped keys at more than six simultaneous presses, check whether the keyboard has a setting to enable NKRO mode.

Mouse tester

The mouse tester shows a diagram of a generic mouse with buttons that highlight on press. It catches left, middle, right, and side buttons (buttons 4 and 5, commonly Back/Forward), plus scroll wheel direction.

The left and right buttons are the most commonly used and also the most commonly worn. Most consumer mice use Omron D2FC switches for the primary buttons, which are rated for a certain number of actuation cycles — often 20 million for standard models and higher for gaming-grade variants. As a switch approaches the end of its rated life, it begins to exhibit erratic behavior: double-clicking when you click once, failing to register a click, or registering a click when you release the button rather than when you press it (called a "pre-travel" or "post-travel" fault depending on the direction). The tester will surface all of these behaviors if you watch the event log carefully.

The middle button (scroll wheel click) and side buttons (commonly mapped to browser Back and Forward) fail far more often than most people realize, simply because they receive less engineering attention despite being used frequently. Side button contacts are particularly prone to oxidation over time, which causes intermittent registration failures. Testing all buttons systematically — not just the two you use most — gives you a complete picture of the device's condition.

Scroll wheel testing and what skipping means

The scroll wheel on a mouse uses a rotary encoder — a small component with a series of notches that produce electrical pulses as the wheel turns. Each notch corresponds to one scroll step, which the operating system translates into a scroll event. Over time, the contacts inside the encoder can oxidize or wear down, causing the encoder to occasionally skip steps (a notch produces no pulse) or to produce spurious pulses in the wrong direction (scroll up produces a brief downward scroll before reversing, or vice versa).

The scroll test counts each individual scroll event and displays its direction. If you scroll slowly upward and see a "down" event appear in the log, your encoder is producing spurious reverse pulses — a common symptom of encoder wear. If the count seems lower than the number of physical notch clicks you made, the encoder is skipping steps. Both problems typically worsen over time and are a sign that the scroll wheel encoder needs to be replaced or the mouse needs to be serviced or retired.

Scroll wheel issues are often mistaken for software problems — users frequently try adjusting the scroll sensitivity in system settings before discovering the root cause is hardware. The tester removes this ambiguity: if the raw event stream shows spurious reverse events, no amount of software adjustment will fix it.

Double-click speed detection

A double-click is two clicks within a time window (typically 500ms on Windows). Some mice develop a hardware fault where a single click registers as a double-click — a common problem with Omron switches after heavy use. The tester shows the time interval between consecutive clicks so you can spot if your mouse is firing multiple events.

The underlying cause is a phenomenon called contact bounce or switch chatter. When a mechanical switch closes, the contacts do not make clean contact in a single motion. Instead, they make and break contact several times in rapid succession over a span of a few milliseconds before settling into a stable closed state. Switch manufacturers build debounce circuitry or firmware logic into keyboards and mice to ignore these brief bounces and register only a single clean press. As a switch ages, however, the bounce duration can increase to the point where the debounce logic no longer filters it out, causing the firmware to register the bounce as a second legitimate press — and the operating system receives two click events from what was physically one click.

The practical impact of a double-clicking mouse is significant and often frustrating before the user identifies the cause. Files get opened instead of selected, drag-and-drop operations fail immediately after starting, UI elements trigger twice, and text editing becomes erratic as double-click selections fire unexpectedly. Many users spend significant time adjusting OS sensitivity settings or blaming their applications before discovering the hardware root cause.

Once you have confirmed double-click chatter through the tester, the options are: replace the switch (feasible if you are comfortable with soldering), replace the mouse, or as a temporary workaround, reduce the operating system's double-click speed threshold so the OS does not interpret the chattering as a double-click. The last option is a workaround, not a fix — the underlying switch will continue to deteriorate.

Click speed (CPS) and input responsiveness

Clicks per second (CPS) is a straightforward measurement: how many distinct click events the browser registers from your mouse within a given time window. The test runs for five seconds and displays both your average CPS and your peak rate. The primary use cases are gaming (where high CPS matters in games like Minecraft PvP), competitive clicking challenges, and — more practically — verifying that your mouse's polling rate and debounce settings are allowing rapid clicks to be registered correctly.

Polling rate is related but distinct from CPS. A mouse with a 125Hz polling rate reports its state to the OS eight times per second. A 1000Hz mouse reports 1000 times per second. Higher polling rates reduce the maximum latency between a physical click and the OS receiving it, which matters for competitive gaming. For most productivity use, 125Hz is imperceptible. The CPS test can indirectly expose polling rate limitations: if you click faster than the polling interval allows, clicks will be merged or dropped in the OS event stream before they ever reach the browser.

Input responsiveness also encompasses the question of whether modifier key combinations register cleanly. Holding Ctrl or Shift while clicking should produce clean modified events. Some wireless keyboards and mice with poor firmware exhibit a delay between when you press a modifier key and when it is reflected in subsequent events, which can cause keyboard shortcuts to fire without the modifier. The tester's event log will show you the exact sequence of events received, making this category of problem easy to identify.

Diagnosing a faulty or worn keyboard

Keyboard faults fall into several categories, each with distinct symptoms and causes. Understanding which category you are dealing with helps you decide whether to repair, replace, or live with the issue.

Dead keys do not register any event at all — no keydown, no keyup, nothing. On mechanical keyboards, this usually means the switch is physically broken (a broken spring or burnt-out contact), or the solder joint connecting the switch to the PCB has failed. On membrane keyboards, it often indicates a damaged membrane layer. In both cases, the tester confirms the issue definitively: press the key, no highlight appears.

Intermittent keys register sometimes but not consistently. This is often caused by oxidation on switch contacts, debris under a keycap (particularly on laptop keyboards), or a loose solder joint that makes contact only under certain conditions. Testing an intermittent key by pressing it fifty to one hundred times in succession often reveals the failure rate — pressing it ten times might produce ten successful registrations, but pressing it a hundred times may reveal that it drops five to ten percent of events.

Stuck modifier keys are among the most disorienting keyboard faults. If the Shift key is physically stuck (the keycap is binding, or the stabilizer mechanism is caught), or if the switch is shorted closed, the OS will behave as if Shift is constantly held: all letters type in uppercase, numbers type symbols, and keyboard shortcuts behave unexpectedly. The tester's key display will show Shift highlighted with no ability to clear it, confirming the hardware cause.

Liquid damage typically causes multiple adjacent keys to stop working or to behave erratically, since liquids spread across the membrane or PCB rather than affecting a single point. If you spilled something on a keyboard and now see a cluster of non-functional keys in the tester, the cause is almost certainly liquid residue shorting contacts. Cleaning with isopropyl alcohol and allowing thorough drying sometimes recovers the keyboard; in severe cases the damage is permanent.

Wireless dropout shows as keys that register fine when the receiver is close but miss events when the keyboard is further away, has a low battery, or is in an environment with RF interference. Testing a wireless keyboard by pressing each key slowly at different distances from the receiver — and then rapidly while close — can expose both range limitations and battery-related performance degradation.

Testing a new device before the return window closes

Quality control for consumer peripherals is imperfect, and manufacturing defects that were missed at the factory appear with low but non-zero frequency. The most economically sensible time to discover a defect is within the retailer's return or exchange window — typically 14 to 30 days. After that, you may be dependent on manufacturer warranty processes, which can be slow and require shipping the device.

For a keyboard, a thorough new-device test should cover every single key — including the numpad, all function keys, media keys, and any macro or special keys specific to your model. Press each key at least twice, once lightly and once with a firm press, since some switch defects only manifest at certain actuation depths. Test modifier keys (both Shift keys, both Ctrl keys, both Alt keys) individually. Hold down five or six keys simultaneously across different regions of the keyboard to check for ghosting or rollover limitations.

For a mouse, click each button at least twenty times in the click log while watching for double-click events. Test the scroll wheel by slowly scrolling in each direction and watching for reverse events or missed steps. Verify that side buttons register cleanly. Run the CPS test to confirm the mouse's polling and debounce behavior are consistent. The entire process takes under five minutes and can save you significant frustration later.

Interpreting results

The keyboard map is the primary output for key testing. A key that never lights up despite being pressed is dead. A key that lights up but stays lit after release is stuck or shorted. A key that occasionally fails to light up is intermittent. A key that lights up twice from a single press is chattering. Normal keys light up promptly on press and clear immediately on release, with no ambiguity.

For the mouse, the click log is where you will find the most diagnostic information. A healthy click produces exactly one mousedown and one mouseup event per physical press. A chattering switch produces two or more events with an interval of under 80ms between them. The scroll event log should show a clean alternation of "up" or "down" events corresponding to your physical wheel rotation; any "up" event appearing while you scroll down (or vice versa) indicates a faulty encoder.

A CPS result that is significantly lower than expected for the speed at which you are clicking can indicate that the mouse firmware is applying aggressive debouncing (which prevents rapid clicks from registering as a feature to counteract chatter, but can also suppress legitimate fast clicks), or that the polling rate is too low to capture all events. If a gaming mouse that previously allowed high CPS rates now seems capped, try updating the firmware, checking the polling rate settings in the manufacturer's software, and running the tester again to verify.

Frequently Asked Questions