Estimate how often the browser receives a fresh controller timestamp while you move a stick or press controls. The rolling counter shows recent update frequency and short-term stability so you can compare connections or controller settings.
Move one stick in small circles for several seconds. Compare the rolling value rather than a single instant reading.
This page counts fresh Gamepad API timestamps observed by the browser. That is useful for comparing browser-visible controller update activity, but it is not guaranteed to equal the physical USB report rate advertised by the controller manufacturer.
A relatively steady rolling rate during continuous motion is more informative than the absolute number by itself. Large swings can come from wireless conditions, browser scheduling, controller firmware, background load or the way a specific device updates timestamps.
Repeat the same movement pattern several times before comparing two connection modes.
Some controllers or browsers do not produce a new timestamp when nothing changes. That means an idle controller can show a low or zero fresh-update count even though it remains connected and responsive.
For this reason, GearCheck Lab asks you to keep a stick moving during the measurement.
Not necessarily. It is the browser-observed rate of fresh Gamepad API updates. A low-level USB analyzer can measure a different layer of the input path.
Wireless transport, power management and radio conditions can affect update timing. Compare repeated samples rather than one short run.
No. Polling/update frequency is only one part of end-to-end latency. Controller firmware, wireless transport, operating-system scheduling, the game engine and display latency also matter.