Why does the page need Gamepad.timestamp?
The controller timestamp is the only admitted source for report intervals. Animation frames and local observation times are never substituted as samples.
BROWSER-OBSERVED TIMING · LOCAL EVIDENCE
Controller Polling Rate Test
Run a gamepad polling rate test to inspect controller report intervals visible through this browser, using an explicit warm-up, bounded sample window, and local-only report.
GAMEPAD.TIMESTAMP · LOCAL INTERVAL WINDOW
No controller selected
Observe report intervals exposed to this browser from distinct, increasing controller timestamps.
No controllers detected.
Waiting for controller
0 valid intervals retained
Browsers expose a controller after it sends an input. Keep this page active, then press a physical controller button.
- Index
- Not available
- Mapping
- Not available
- Connected
- No
- Stale
- No
SAME WINDOW · SAME STATISTICS
Valid report intervals
0 retained
- Browser-observed rate
- Unavailable
- Average interval
- Unavailable
- Minimum interval
- Unavailable
- Maximum interval
- Unavailable
- P50 interval
- Unavailable
- P95 interval
- Unavailable
- Jitter (population standard deviation)
- Unavailable
Local report
The report is created in this browser and downloaded directly to your device. Nothing is uploaded.
Raw controller samples are excluded unless you opt in. At most 5,000 samples are included.
Timestamp evidence
What this timing test measures
The instrument admits only distinct, finite, strictly increasing Gamepad.timestamp values. It derives each interval from adjacent admitted timestamps, then calculates browser-observed rate, average, minimum, maximum, P50, P95, and population-standard- deviation jitter from one shared bounded set.
Four deliberate steps
How to collect a stable timing window
01
Connect and choose
Connect a controller, activate it with a physical input, and choose the intended device if the browser exposes more than one.
02
Start a clean run
Select Start and keep this tab active. The first second is warm-up and contributes no report intervals.
03
Collect 60 valid intervals
Continue providing controller input until at least 60 distinct, increasing timestamp intervals enter the bounded window.
04
Stop and compare
Stop to freeze the current summary, then compare the average, range, percentiles, and jitter from that same interval set.
Evidence boundary
Browser and timestamp limitations
Results include controller firmware, transport, operating-system, driver, browser, tab activity, and page-scheduling effects. This page does not prove physical USB polling rate, device firmware behavior, or true end-to-end input latency. Compare runs only when the browser and connection conditions are equivalent. Treat each polling rate controller test as browser-observed evidence rather than hardware certification.
When no stable summary appears
Troubleshooting unavailable timing
- Keep this tab active and provide a physical controller input after connecting.
- Choose the intended controller when the selector lists multiple devices.
- Try a current desktop browser if the exposed timestamp remains zero or unavailable.
- Restart the run after changing cable, port, Bluetooth pairing, browser, or device.
Plain answers
Frequently asked questions
Why is timing unavailable in my browser?
Some browser and controller combinations expose zero, missing, non-finite, repeated, or backward-moving timestamps. This page reports that limitation explicitly.
Why do earlier intervals disappear?
The tool retains the newest 250 valid intervals or five seconds of controller timestamp span, whichever bound is reached first.
Does the local report include identifying data?
The report excludes the controller identifier, browser user agent, and network data. Raw interval samples remain unchecked unless you opt in.
What does the polling rate test controller measure?
It summarizes browser-observed Gamepad timestamp intervals and does not certify a controller's physical USB polling rate.