Representative interval
The 10th percentile of valid short intervals. It represents the faster portion of the run without letting one unusually short event control the result.
Factory acceptance bench / Keyboard input
Keyboard Polling Rate Test
Observation window10.000 sLocal browser processing
Check fast keyboard event timing and consistency in ten seconds—without installing software or pretending a browser can see raw USB reports.
Test process / 10 seconds
- 01Connect the keyboard directly and close heavy background apps.
- 02Start, keep this area focused, then alternate A and S quickly.
- 03Read the estimate and consistency before comparing settings.
Browser estimate limitation
This measures browser-visible keyboard event timing. It cannot read or certify the raw USB/HID polling rate.
EVENT TRACE / KEY STATE CHANGES10.0 s window
Samples0valid intervals
Time10.0seconds
During the test, alternate the A and S keys. The page only observes timestamps for these keys while this area has focus.
Exactly what this test can—and cannot—measure
The browser exposes key event timestamps, not USB packets or the keyboard matrix scan. We use the 10th percentile of valid short intervals as a representative fast spacing, then convert it with 1000 ÷ interval. Use repeated runs to compare settings on the same computer, browser and port.
01 / Method
How the estimate is calculated
A fast-event estimate with the limitation built in
During a run, the focused test area records timestamps for non-repeating A and S keydown and keyup events. It does not keep the key sequence, and events outside the fixture are ignored.
Invalid timestamps, intervals under 0.125ms and pauses over 250ms are removed. The representative spacing is the 10th percentile of the valid intervals; the displayed Hz estimate is 1000 divided by that spacing.
Focused A/S eventsClean short intervals10th percentileBrowser-observed Hz
02 / Provenance
Methodology record
A named maintainer and a bounded validation scope
This record states who maintains the test, what was checked for this release, and where the keyboard-event data goes. It does not claim laboratory validation or coverage we have not performed.
- Maintained by
- HardwareTest.org Editorial Team
- Last methodology update
- Verified release environment
- Chromium-based browser on Windows; responsive presentation checked at 1440 × 900 and 390 × 844. Firefox, Safari, macOS and Linux are not claimed as verified for this release.
- Data boundary
- Intervals are calculated locally in your browser. The tool does not save or transmit the A/S key sequence; analytics receive aggregate test metadata only.
03 / Readout
Result interpretation
Read the intervals before the headline number
The result sheet describes browser-visible key-event timing. Its value is in repeatable comparisons on the same setup—not in certifying the keyboard’s advertised USB polling mode.
Fastest interval
The single shortest valid interval. It is diagnostic only because one browser scheduling burst or timestamp anomaly can make it look better than the rest of the run.
Timing variation
The standard deviation divided by the mean interval, shown as a percentage. Lower values mean the observed intervals were more tightly grouped, but key technique and system load also affect it.
Confidence thresholdsApplied after at least 20 valid intervals
High
80+ valid intervals and timing variation ≤ 45%
Medium
40+ valid intervals when the high-confidence conditions are not both met
Low
20–39 valid intervals
No result
Fewer than 20 valid intervals
What the result can support
- Comparing repeated runs on the same browser, computer and USB path
- Seeing whether browser-visible timing or consistency changes after one controlled adjustment
What it cannot support
- Certifying a raw 125, 500, 1000, 4000 or 8000Hz USB report rate
- Proving a hardware defect, total input latency or switch response time
04 / Reference
Rated polling intervals
What 125–8000Hz means in theory
Polling rate is reports per second. The inverse gives the theoretical time between USB reports—but that interval is not the same thing as a browser keyboard event interval.
125 Hz8.00 ms
500 Hz2.00 ms
1000 Hz1.00 ms
4000 Hz0.25 ms
8000 Hz0.125 ms
Scan rate is different. A keyboard can scan its switch matrix at one rate and report to the host at another. Debounce, firmware and the operating system sit between those stages and the event your browser sees.
Keyboard Polling Rate Explained05 / Conditions
Better test conditions
Make each comparison repeatable
Use the same direct USB port
Avoid changing hubs, wireless modes or ports between runs.
Alternate A and S continuously
Use a light, repeatable rhythm through the whole ten-second window.
Reduce scheduling noise
Close heavy tabs and apps, keep the page visible and repeat at least three times.
06 / Diagnose
Troubleshooting
If the estimate looks lower than expected
01
Repeat under low load
Browser scheduling spikes can hide short intervals. Close active workloads and compare the median story across several runs.
02
Verify the configured profile
Check the keyboard’s firmware or companion software, then confirm that the intended onboard profile is active.
03
Change one variable
Compare direct USB versus hub, wired versus wireless, or one browser versus another—one change per set of runs.
04
Use the right instrument
If you need the actual USB report cadence, use a USB analyzer or a trusted low-level diagnostic. This browser result is not proof of a defect.
07 / FAQ
Common questions
Keyboard polling test FAQ
01Can a browser measure my keyboard’s true USB polling rate?+
No. A webpage receives keyboard events after the keyboard, USB stack, operating system and browser have already handled them. This tool estimates fast browser-visible event spacing; a USB protocol analyzer or suitable manufacturer utility is needed to inspect raw reports.
02Why does the result change between runs?+
Typing rhythm, browser scheduling, background load, power management and the keyboard’s scan behavior all add variation. Compare several runs under the same conditions and treat the result as a relative check, not a certification.
03Does an 8000Hz keyboard always show 8000Hz here?+
No. A claimed 8000Hz USB report setting corresponds to a theoretical 0.125ms report interval, but browsers can coalesce, delay or expose fewer keyboard events. A lower browser estimate does not by itself prove that the keyboard is misconfigured.
04What sample is used for the estimate?+
The tool removes invalid timestamps, intervals shorter than 0.125ms and pauses longer than 250ms. It then uses the 10th percentile of the remaining short intervals rather than the single fastest event, which is too sensitive to anomalies.