Choose sensitivity
Start with the default 40 ms threshold. Use 20 ms for lower sensitivity or 80 ms to flag more short release-to-press intervals.
Check suspicious repeated inputs with adjustable sensitivity. Events stay local.
Possible Chatter / Suspicious Repeated Input observed. Repeat the test at a steady pace and on another device; this does not prove a hardware defect.
Click Start Test, then tap your physical keys.
Newest first · Last 100 events · Interval means same-key release → next press.
| Key / Code | Event Type | Interval | Timestamp | Status |
|---|---|---|---|---|
| No events yet. Start a test to see received inputs. | ||||
Test only with a physical keyboard. Do not type passwords or sensitive information. Events stay in page memory. Fn, media keys, and OS-reserved shortcuts may not reach your browser.
Start with the default 40 ms threshold. Use 20 ms for lower sensitivity or 80 ms to flag more short release-to-press intervals.
Click Start Test, then tap each physical key at a steady pace. Normal operating-system auto-repeat is ignored.
Stop the test and review the recent event log. Repeat the same key on another device before interpreting a suspicious result.
Possible Chatter means a key was released and pressed again within your selected threshold. Suspicious Repeated Input means a non-repeat keydown arrived without an observed keyup.
These labels describe browser events, not a hardware diagnosis. Fast manual taps, timing precision, software, and missed release events can affect the result. The threshold is analysis sensitivity, not a certification standard.
Long holds flagged by the browser as auto-repeat do not add valid presses or suspicious events. Results summarize the whole session; only the most recent 100 events are retained. Changing sensitivity updates the analysis without restarting.
No. It is a reason to investigate and repeat the test. A website only sees events delivered by the browser, and rapid manual tapping or software behavior can look similar to chatter.
Normal keydown events with repeat=true are ignored for valid presses and suspicious counts. A non-repeat down without a release is marked as uncertain repeated input, not a confirmed defect.
It measures the time from the last observed keyup to the next keydown of that same physical key. A dash means there was no comparable observed release, including duplicate downs without a release.
Download Report creates a CSV locally with sensitivity, session totals and the most recent 100 physical-code events. Your keystrokes are not uploaded or stored between visits.