Skip to content
Testpartout

Input Device Tests

Input device tests show the events this browser receives from a keyboard, mouse or game controller. Choose the device with the symptom, repeat a deliberate action and compare the observed events before deciding whether a hardware fault is plausible. No installation or account is required.

Choose a test

  • Touch Screen Test

    Map touch coverage, compare simultaneous contacts and watch for unexpected touch events reported by your browser.

  • Keyboard Ghosting & Key Rollover Test

    Hold combinations together and compare browser-observed keys, presets and maximum simultaneous input.

  • Mouse Polling Rate Test

    Estimate browser-delivered mouse event rate over ten seconds with median intervals and sample context.

  • Keyboard Test

    Press keys to confirm every one registers, and find stuck, dead or repeating keys.

  • Mouse Test

    Check buttons, double-clicks, scrolling and pointer movement for a failing or erratic mouse.

  • Gamepad / Controller Test

    Check buttons, triggers and analog sticks, including stick drift and dead-zone behaviour.

Keyboard events: a received key is not a circuit diagnosis

Keyboard Test lists detected keys, held states, modifiers and repeat events after you start listening. Press one key at a time, release it and compare the visible response. A key that registers here confirms a browser event arrived; a missing entry can also result from focus, browser-reserved shortcuts, operating-system handling or a key that does not expose a standard event.

Physical-key codes and produced characters are different. Keyboard layout, Shift, Alt and input methods influence the character while the physical code may remain unchanged. Holding a letter commonly produces repeat events through the system’s repeat settings. That is not the same observation as repeated events from a brief, deliberate tap. Test modifiers individually before combining them.

Mouse buttons, wheel and double-click observations

Mouse Test observes presses and releases, left/right/middle button activity, wheel direction and pointer movement in its test area. Start the test and keep your intended interactions inside that area. Browser menus and navigation may reserve additional buttons. Wheel deltas describe events received by the page, not a calibrated distance travelled by a physical wheel.

For unwanted double-clicks, compare repeated isolated taps with deliberate two-click pairs. The double-click indicator reflects the browser’s dblclick event; it does not independently inspect a mechanical switch. Operating-system timing settings and driver remapping can affect which actions applications interpret as double-clicks. A second event is evidence to investigate, not a guaranteed switch-wear diagnosis.

Controllers: buttons, triggers, sticks and deadzones

Connect a supported controller, then press a button to make it visible to the Gamepad API where the browser requires an initial interaction. Gamepad Test reads browser-reported buttons, trigger values and analog stick axes. Mapping can differ between controllers and browsers; an unfamiliar button label does not by itself mean the physical control is defective.

A stick-drift check looks at resting coordinates after you release the stick. Small offsets need context: device calibration, firmware and software can all affect what the browser reports. A game may apply its own deadzone and ignore movement visible on this page. Repeat after moving and releasing the stick in several directions, then compare the symptom in the application that concerns you.

Separate a connection symptom from an application problem

If a key, click or controller button works here but not in a game, first inspect that application’s bindings and input mode. Focus, overlays, accessibility settings and remapping software can alter behavior before or after the browser sees an event. Avoid changing several settings together: keep a short observation log so you can identify which change mattered.

For USB devices, reseat the connector and try another supported port. A hub, adapter or cable can introduce a different path from a direct connection. Wireless devices also depend on battery charge, pairing and receiver placement. Bluetooth and dedicated wireless receivers are not interchangeable technologies; compare supported connection modes rather than assuming both have the same behavior.

Repeat safely before replacing equipment

Try the same simple action in another browser and, if available, on another computer. Persistent symptoms across independent setups make a device-side issue more plausible, but do not prove a particular internal cause. For debris around keys or buttons, disconnect or power off the device as the manufacturer recommends and follow its cleaning instructions. Do not open or electrically modify equipment based on browser readings.

These tests inspect browser input APIs rather than firmware, switch contacts or controller electronics. They cannot provide manufacturer-grade diagnostics or establish a universal performance benchmark. Keyboard and mouse events, controller coordinates and drift observations stay local; test results are not sent to analytics. Use the guides below for symptom-specific follow-up checks.

Read the methodology for measurement principles and the privacy policy for data handling. Return to all device tests to check another part of your setup.

Guides & troubleshooting