Controller Polling Rate Testbrowser-visible

See how often your browser receives new input from your controller, in Hz, and how steady it is. This is the browser-visible report rate. It isn't the same as the controller's own polling rate.

P1
No controller yet Press any button on your controller to start
Waiting for input
A

Connect a controller and press any button

Plug it in with a USB cable or pair it over Bluetooth. Browsers keep controllers hidden until you press a button, so the test is ready the moment you do.

Controller not detected? →

Live rate browser-visible

Move a stick
—Hz
new readings per second
Average
—
Lowest
—
Highest
—

Time between readings ms

—
0 ms816+
Average gap
—
Jitter
—
Readings
0

Rate over time last 10 seconds

Hz, every quarter second
300 Hz 150 0
10 s agonow

Your runs kept until you close this tab

RunConnectionAverageGapJitterSteadiness

What this number means

Every time your browser receives a new reading from the controller, it updates a timestamp. This test counts how many times per second that happens while you move a stick. That's the browser-visible report rate.

It tells you how smoothly the browser, and usually games on the same device, receive your input. It is not the controller's own polling rate printed on the box.

Why it can be lower than the box says

  • The browser checks on its own scheduleBrowsers look for new controller data at their own pace, which can be slower than the controller reports.
  • Only changes countIf the stick doesn't move, there's nothing new to report. Keep moving it the whole time.
  • The connection mattersBluetooth often delivers readings less steadily than a cable. Run the test both ways to compare.
  • Your system is busyOther apps, power saving and many open tabs can slow how often the browser checks.

How to get a steady reading

  1. Move a stick in circlesfor the whole 10 seconds. Small, constant movement is enough.
  2. Plug in with a cableif you want the best case, then try Bluetooth to see the difference.
  3. Close other heavy apps and tabs,and keep the laptop plugged in so power saving doesn't kick in.

Report rate isn't input lag

A high report rate means readings arrive often. It doesn't tell you how long a press takes to reach the screen. Measuring that needs a camera or dedicated hardware, which a web page can't do. What a browser can't measure →

Related tests

FAQ

Can this measure 1000 Hz?

Usually not. The number here is limited by how often your browser checks the controller, so it's often lower than a controller's rated polling rate, even when the controller itself is fine.

Why does the number drop when I stop moving?

Browsers only deliver a new reading when something changes. A still stick sends nothing new, so the count falls.

Is a higher number always better?

Higher and steadier is better, but past a point you won't feel the difference. A steady rate with low jitter matters more than the top number.

Does Bluetooth lower the rate?

It often does, and it's usually less steady. Run the test once with a cable and once over Bluetooth, and compare the two runs in the table.