What the browser can measure
BenchRush measures the last part of a much larger hardware-to-browser pipeline. This page shows exactly where each number begins, where it ends and how to reproduce it.
The browser sees events, not your entire device.
A keyboard switch closes, firmware creates a report, the operating system processes it, the browser receives an event and JavaScript finally sees that event. BenchRush starts at that last browser-visible layer. That makes the tools useful for reproducing symptoms and personal baselines — but not equivalent to USB analyzers, oscilloscopes or manufacturer diagnostics.
From action to result
Press a key, move a pointer, click a target or wait for a visual cue.
KeyboardEvent, PointerEvent, wheel or animation callbacks reach the page.
JavaScript records distinct events, intervals, hits or misses with a defined test window.
The result is shown with its browser-level limitation and a related guide or test.
Measurement matrix
This is the shortest way to see what each tool means. “Not measured” is deliberate: a useful methodology says where the number stops.
| Tool | Browser signal | Reported result | Not measured directly |
|---|---|---|---|
| Keyboard test | keydown | Distinct received keys / quick-check completion | Switch contacts, scan matrix, cable electronics |
| Rollover | simultaneous keydown/keyup | Held keys + maximum simultaneous count | Every possible matrix combination or NKRO certification |
| Mouse test | pointer/button/wheel events | Which core inputs reach the page | Sensor quality, switch bounce electronics, raw USB packets |
| Double-click check | click timing | Very-rapid repeats under the test threshold | Electrical debounce waveform or switch condition |
| Polling estimate | pointermove timestamps | Approx. browser pointer-event Hz | Configured raw USB polling rate |
| Scroll test | wheel events | event rate + direction changes | Physical wheel rotation distance |
| Gamepad test | Gamepad API button/axis state | browser-visible buttons, axes and connection state | raw HID/USB packets, firmware calibration or physical mechanism |
| Screen visual test | manual solid-color inspection | no automatic score; visual comparison only | physical pixel state from JavaScript |
| Refresh estimate | requestAnimationFrame | median frame cadence + timing spread | Panel electronics or guaranteed monitor mode |
| Reaction test | performance.now() around visual cue/click | 5-round average in ms | Human reaction isolated from display/input latency |
| CPS | click events | clicks ÷ 10 seconds | Switch actuation force or hardware debounce settings |
| Spacebar sprint | non-repeat keydown | distinct presses / 10 seconds | Physical travel or switch force |
| Mouse accuracy | target pointer events + timing | hit accuracy + average acquisition time | Sensor lab precision, human ability independent of setup |
Timing rules that matter
performance.now()Reaction and target-acquisition timing use the browser’s monotonic high-resolution clock rather than wall-clock time.
requestAnimationFrame()The refresh test samples callbacks scheduled before repaints. Hidden/background tabs can be throttled, so the test asks you to keep the tab visible.
Pointer events can be coalesced or scheduled by the browser. That is why polling is labeled a browser event-rate estimate, not raw USB telemetry.
Short browser measurements are noisy. Same-device, same-browser repeated runs are more useful than comparing isolated numbers across different setups.
How result labels work
A raw number is not very useful without context, so BenchRush adds a short interpretation directly to completed numeric tests. The label depends on the kind of measurement:
Uses a public browser-test reference. Human Benchmark currently reports a 273 ms median across more than 81 million recorded reaction clicks. BenchRush uses that as broad context, not as a medical norm or a guaranteed percentile.
Use broad BenchRush guide ranges designed to make repeated same-device runs easier to understand. They are explicitly not population percentiles.
Use the nearest familiar Hz class to describe browser-visible cadence. “Near 1000 Hz” or “Near 144 Hz” is setup context, not certification of USB or panel hardware.
For any timing or speed result, your own repeated runs on the same device and browser are usually more meaningful than a cross-device comparison. Reaction reference checked 2026-10-05: Human Benchmark reaction-time statistics.
PlayerScore v1 — exact rules
PlayerScore is intentionally simple and transparent. It unlocks after at least three supported benchmark components exist. Each available component is normalized to 0–100, the available components are averaged, then the average is multiplied by 10 and rounded to produce a 0–1000 local score.
clamp((450 − ms) ÷ 3, 0, 100)clamp((CPS − 2) × 10, 0, 100)clamp((presses − 20) ÷ 0.9, 0, 100)quick-check completion %, capped at 100100 after all 4 core inputs passclamp(browser Hz ÷ 10, 0, 100)successful target clicks ÷ all attempts × 100Not included in PlayerScore: keyboard rollover and refresh-rate estimates. They provide setup context but do not raise or lower the score. Arcade scores also remain separate.
A repeatable test protocol
- Keep the tab visible and focused.Background throttling can affect animation and event timing.
- Use the same browser and device.Change one variable at a time when testing a setting or hardware change.
- Run more than once.Use a stable range or multi-round average instead of one lucky result.
- Separate symptoms from diagnosis.A missing browser event is evidence; it is not proof of which hardware layer failed.
- Escalate when the decision matters.Use manufacturer diagnostics or lower-level tools for hardware certification or warranty decisions.
Technical references
BenchRush’s browser-side measurement language follows standard Web APIs. These references explain the primitives the tests use; they are not endorsements of BenchRush.
Method changes are versioned in plain English
Current scoring model: PlayerScore v1. Methodology reviewed: 2026-10-05. If a formula changes, BenchRush will update this page rather than silently redefining what an old score meant.
Why BenchRush is built this way → · Read the interpretation guides →