Browser support
What this browser can expose to BenchRush
BenchRush can only measure signals that reach normal Web APIs. This live capability check shows which important pieces are available in the browser you are using right now.
Live capability check
Checking this browser…
“Available” means this page can access the API in the current context. It is not a hardware pass/fail result.
Capability is not the same as hardware support
A green capability means the browser exposes the relevant API in this page context. It does not guarantee that every controller maps identically, that fullscreen is available inside every embedded context or that a browser timing number equals raw hardware telemetry.
Browser capability is one layer of the diagnostic path
An available API means the page can ask for that signal; it does not prove the hardware, driver or firmware layer is healthy.
BenchRush API map
| BenchRush area | Browser primitive | What it enables | Important limit |
|---|---|---|---|
| Keyboard / rollover | KeyboardEvent | Browser-visible key presses and held combinations | OS shortcuts and firmware behavior can happen before the page |
| Mouse / polling / accuracy | PointerEvent | Pointer buttons, coordinates and movement events | Not raw USB packets; browsers may schedule or coalesce movement |
| Reaction / target timing | performance.now() | Monotonic short-interval timing | Includes the visible browser/input path around the task |
| Refresh estimate | requestAnimationFrame() | Animation callback cadence before repaints | Background tabs are commonly throttled or paused |
| Controller test | Gamepad API | Browser-visible buttons, axes and connection state | Mapping and platform/controller behavior can vary |
| Screen visual test | Fullscreen API (optional) | Larger solid-color inspection surface | The visual test still works without fullscreen |
| PlayerScore / history | localStorage | Private local progress on this browser | Clearing site data or using another browser removes that local context |
Why a controller may need interaction first
Some browsers do not expose a connected gamepad to the page until the user presses a button or moves a control while the page is visible. That is a privacy/browser behavior, not automatic evidence that the controller is disconnected.
Why refresh tests need a visible tab
requestAnimationFrame() generally follows repaint opportunities, but browsers commonly pause or reduce callbacks in background tabs. Keep the BenchRush tab visible when comparing refresh cadence.
Primary technical references
Questions people ask
If one capability says unavailable, is my hardware broken?
No. The result only describes what this browser/page context exposes. Try the relevant test, another browser or the manufacturer diagnostic before making a hardware conclusion.
Why can Gamepad work differently across controllers?
The browser and platform expose controller state through a mapping layer. Button/axis layout and optional features can vary by controller and operating system.
Why does fullscreen sometimes fail?
Fullscreen can be unavailable or restricted by browser, device or embedding context. BenchRush screen inspection remains usable in-page when fullscreen is unavailable.
Privacy by default
Your personal bests, XP and streak are stored locally in this browser. The current tool does not require an account or upload your individual run to a global leaderboard.