WebToolArcKey Repeat Rate Test
Hold a key to estimate the initial repeat delay, average repeat interval, and repeat events per second.
Results reflect browser KeyboardEvent auto-repeat timing. Operating-system repeat settings and browser scheduling affect the values.
Steady-repeat stability review
Use the original hold-key test above, then inspect the same captured repeat intervals for sample progress, spread, percentile and jitter evidence.
Hold one ordinary key until the sample goal is reached for a more stable comparison.
Practical guide and verification
Use the tool first, then use these checks to interpret, verify and hand off the result without displacing the primary workflow.
Collect enough steady intervals before comparing rates
The first auto-repeat event includes the operating-system delay and should not be mixed with the steady repeat interval. Hold the same key until the sample goal is reached, then compare median or mean interval across runs. A tiny sample can make one scheduling pause dominate the apparent repeat rate.
Use stability evidence alongside events per second
Two runs can report similar average repeat rates while one has much more interval variation. Review the minimum, maximum, percentile spread, and jitter estimate before calling two settings equivalent. Repeat the test with the same browser, background load, and power mode for a fair comparison.
Keep browser repeat separate from hardware polling
KeyboardEvent repeat timing reflects the operating system and browser auto-repeat pipeline after a key is held. It does not measure switch debounce, scan matrix frequency, USB polling rate, or end-to-end game latency. Use the result to compare repeat settings rather than to certify hardware specifications.
Lock the comparison procedure
Use the same key, focus area, sample goal, and session conditions for before/after tests. Modifier keys and application shortcuts can behave differently from ordinary printable keys. If one result looks anomalous, run several trials and compare the captured history instead of drawing a conclusion from a single hold.