Test your controller's polling rate. Right in the browser.

The JoyCheck controller tester family includes a controller polling rate test: connect a pad, rotate a stick for six seconds, and read how often your browser actually received a fresh state, timed straight from the W3C Gamepad API with nothing sent to a server.

Update rate in Hz · Median interval · Jitter · 6-second run · 6 min read

A controller polling rate test measures how often your pad reports its state, and a browser can time that directly. Every update the browser receives carries a timestamp[1], so the gaps between timestamps are the controller’s real update intervals as the page sees them. JoyCheck collects those gaps for six seconds and reports the median as an observed rate in Hz.

Updated on 2026-07-17 by Taimoor Bamazai, founder of Elites Algorithm Limited (a registered tech company in Dublin, Ireland) and the builder behind JoyCheck.

How do you test controller polling rate in the browser?

You test polling rate by letting the page time the gaps between controller state updates while you keep the pad talking. Connect the controller, start the 6-second run, and rotate one analog stick in slow circles the whole time. The tool waits until movement is flowing, measures, then reports the observed Hz with the interval statistics behind it.

Run it as a routine, because the setup steps decide whether the measurement is valid.

1. Connect and wake the pad. Plug in or pair the controller and press any button, since the Gamepad API stays silent until a button or axis moves.
2. Start the test, then move. Press Start and rotate a stick continuously. The tool arms itself and only begins timing once updates are flowing.
3. Keep the stick moving. A controller reports when its state changes, so a still pad sends nothing and the tool will warn you that the signal paused.
4. Rerun on the other connection. Test once wired and once over Bluetooth, and compare the two results. That difference is your connection’s real cost.

The browser gamepad tester covers the rest of the pad, so the polling test slots into the same no-install checkup as buttons, sticks, and rumble.

What does the polling rate test actually tell you?

The test tells you how often your browser received a fresh state from the controller, as a median rate in Hz plus the spread around it. That is the number that matters for how quickly a browser game, an emulator, or remote play sees your inputs, and it is a floor for what the hardware itself is doing.

These are working bands from our own diagnostic testing, not a manufacturer specification, so treat them as a guide rather than a hard line.

The histogram under the stats is the part worth reading twice. One tight peak means clean, regular timing. Two peaks or a smear means the link is delivering updates unevenly, and that inconsistency is what actually feels laggy in play, even when the average looks fine.

What is a good polling rate for gaming?

For most players, the common wired class around 125 Hz is genuinely fine, because at 8 milliseconds per update the controller is rarely the slowest link in the chain. Competitive players chase 250 to 1000 Hz pads for the last few milliseconds, and those gains are real but small: moving from 125 Hz to 1000 Hz saves at most about 7 milliseconds of worst-case wait.

Consistency is the number people underrate. A pad that holds a steady interval with low jitter feels more predictable than one that nominally polls faster but stutters, which is why the test reports jitter next to the rate instead of a lone headline figure.

Why does my controller show 60 Hz?

A 60 Hz reading almost always means something between the pad and the page is pacing the updates, not that the controller is faulty. The three usual suspects are a Bluetooth link running at a slow connection interval, a browser that refreshes gamepad state once per display frame, and deliberate timer rounding that some browsers apply for privacy.

Split them apart the practical way: retest wired in Chrome or Edge. If the number jumps, the pacing came from the wireless link or the browser, not the hardware. If a wired retest stays low and the pad also feels sluggish in games, the Bluetooth disconnect guide covers the wireless side, and a different cable or port is the next cheap experiment.

Can a browser really measure polling rate?

A browser can measure the update rate it actually receives, and it does so honestly if the tool frames it right. The Gamepad API updates each pad’s timestamp whenever fresh data arrives[2], and JoyCheck samples far faster than any pad reports, so the intervals it times are the API’s own, not an artifact of a slow loop.

What a page cannot see is the raw USB or Bluetooth traffic. A wired pad negotiates its report interval at the USB level[3], and the browser sits above that, free to consume updates at its own pace. So when the observed number is lower than a pad’s advertised rate, the honest reading is that the browser ceiling was reached, not that the pad failed. That is also why this test’s superpower is comparison on one machine: both runs face the same ceiling, so the wired versus Bluetooth gap is real.

What a browser polling test can and cannot do

A browser polling test can time real update intervals, expose a slow or unstable link, and put a measured number on the wired versus Bluetooth difference on your own setup. What it cannot do is certify a manufacturer’s Hz claim, see through the browser’s own input pipeline, or measure end-to-end input lag to your display, because those need hardware instruments.

Used inside those lines, it answers the question people actually have, which is whether this pad, on this connection, on this machine, is updating fast and steadily enough.

For the rest of the pad’s health, the stick drift test reads the analog sticks at rest, the deadzone tester shows the resting and edge band, the controller calibration tester checks center, range, and triggers, and the controller vibration test fires the rumble motors, so polling rate completes the full browser checkup.