Polling rate test: the mouse events (Hz) your browser receives

Move across the pad to measure browser-delivered pointer events. The live chart, run average and peak use those events only.

Move your mouse inside this area

Ready. Nothing leaves your device.

What it may mean

These numbers are the mouse events your browser delivered to this page in one-second windows, not your mouse's USB polling rate. The system and browser can merge or cap movement events, so a 1,000 Hz mouse often shows fewer here, and stopping or slowing down lowers the count. Move steadily in circles for a few seconds and read the peak.

Live log and download (advanced)

Your latest presses show here. The download keeps every press, up to the log limit.

    No download, no account: it runs in your browser, Chromebooks included.

    Pointer lagging, freezing or jumping? Find the cause and fix it.

    Is this my USB polling rate?

    No. The live rate counts delivered pointermove events in the last second. The run average divides intervals between events by elapsed seconds. The peak is the largest rolling one-second event count in this run.

    What this browser can measure

    The browser and operating system can merge, delay or cap movement events. This page does not promise the device’s USB polling frequency or raw input. See how presses are timed.

    Where input lag comes from

    A click passes four steps before you see it. A browser cannot time any of them on its own, but two follow from settings you can look up: your mouse's polling rate and your display's refresh rate.

    1. SwitchThe button closes and the mouse decides it was a press. The time depends on the mouse and never reaches the browser.
    2. USB reportAt 1000 Hz the mouse reports every 1.0 ms, so a press waits up to 1.0 ms for the next report.
    3. Computer and browserThe system passes the event to the browser and the page. This varies with load, and a page sees only part of it.
    4. DisplayAt 60 Hz a new frame starts every 16.7 ms, so the change waits up to 16.7 ms for the next frame, then the screen's own response time.

    From the polling rate and the refresh rate alone: up to 17.7 ms, about 8.8 ms on average. The switch, the system and the screen's response add their own time.

    The polling test above counts the events your browser delivers, not the mouse's USB polling rate.

    What polling rate means, and which to pick

    Polling rate, which Logitech calls report rate, is how often the mouse sends its movement and clicks to the computer: 125 Hz is once every 8 ms, 500 Hz every 2 ms, 1,000 Hz every 1 ms and 8,000 Hz every 0.125 ms. Logitech's G304 and G305, for example, report at 1,000 Hz by default and drop to 125 Hz in their battery-saving mode, and Logitech's PRO LIGHTSPEED receiver reaches 8,000 Hz with some of its mice.

    For most players 1,000 Hz is plenty. Going higher cuts the wait for the next report from at most 1 ms to at most 0.125 ms, a small share of a 60 Hz or 144 Hz screen's frame (the figure above adds them up), and on a wireless mouse it uses more battery. You set the rate in the mouse maker's app. This page cannot read rates that high: Logitech says browser testers cannot correctly process high report rates, and its mice change the rate as you use them to save battery.

    Try a related test