Mouse Polling Rate Test

Press Start, then circle the mouse fast for five seconds to read its polling rate in Hz.

Press Start, then sweep the mouse in fast circles for 5 seconds. Anywhere on the page counts.

0 reports

More options

Your last five runs

  1. No run yet.

Nothing from this test is stored unless you tick the box. Kept runs are numbers only and never leave this browser.

How to read it

Mouse report rate

The peak is the number to compare with the rate on the box. A slow hand pulls the average down, so look at the peak first.

This is an estimate. A browser sees the reports the system passes on, and only while the mouse is moving fast.

  • The page counts the pointer reports your browser hands over while the mouse moves, using raw pointer updates where the browser has them.
  • The peak is the busiest tenth of a second of the run, and the average leaves out every pause longer than 50 ms.
  • Where a browser hands over one movement per frame and no more, the page says it cannot measure and shows no number at all.

Result

No run yet. Press Start and keep the mouse moving for 5 seconds.

What this means

Peak
-
Average
-
Median gap
-
Reports
-

Next step Now check the scroll wheelCheck the buttons for double clicks

All 12 readings

Standard report rates 8

  • 100 Hz One report every 10 ms. This is the default of the old PS/2 mouse port, which can be set as high as 200 Hz.
  • 125 Hz One report every 8 ms, the default rate for USB mice. A mouse with no rate setting will normally read here.
  • 250 Hz One report every 4 ms, a middle step in the settings software of many adjustable mice.
  • 500 Hz One report every 2 ms, a quarter of the gap at the 125 Hz default.
  • 1,000 Hz One report every millisecond, the most that full-speed USB allows. A 60 Hz screen draws one frame in the time this mouse reports 16 or 17 times.
  • 2,000 Hz One report every 0.5 ms. Rates above 1,000 Hz need a mouse and receiver built for high-speed USB.
  • 4,000 Hz One report every 0.25 ms. At 1,600 DPI the mouse has to travel 2.5 inches a second just to have one new count for every report.
  • 8,000 Hz One report every 0.125 ms, the ceiling of high-speed USB polling. The browser and the rest of the computer have to keep up too, so a reading below 8,000 is not proof of a fault.
Show all 12 readings (4 more)

Readings that need a second look 4

  • A different rate in another USB port A hub, a front-panel socket or a pass-through port on a keyboard can limit what reaches the computer. Test again with the mouse or its receiver in a port on the machine itself.
  • A figure between two steps, such as 700 Hz Report rates are fixed steps, so an in-between average means some intervals went unused: slow movement or a busy computer. Look at the peak and the graph, not only at the average.
  • An average far below the peak You slowed down or paused during the run. A mouse has nothing to report while it is still, so only fast, continuous movement shows its full rate.
  • The same number as your screen: 60, 120, 144 or 165 Hz The browser is handing over movement once per frame, so you are reading the display and not the mouse. Use a browser with raw pointer updates. The page warns you when it has fallen back.

How this list was compiled: Table written for this page. The interval for each rate is 1,000 ms divided by the rate. The USB default of 125 Hz for mice, the PS/2 default of 100 Hz (adjustable up to 200 Hz), the 1,000 Hz ceiling of full-speed USB and the 8,000 Hz ceiling of high-speed USB are given at https://en.wikipedia.org/wiki/USB_human_interface_device_class (checked 2026-09-18). How browsers deliver pointer movement is documented at https://developer.mozilla.org/en-US/docs/Web/API/Element/pointerrawupdate_event and https://developer.mozilla.org/en-US/docs/Web/API/PointerEvent/getCoalescedEvents, and browser support was read from the compatibility data at https://github.com/mdn/browser-compat-data (all checked 2026-09-18): raw pointer updates exist in Chrome from version 77, in Edge, which follows Chrome, and in Firefox from version 148, need a secure (HTTPS) page, and are not in Safari, which has offered coalesced events since version 18.2. The entries read were api.Element.pointerrawupdate_event in api/Element.json and api.PointerEvent.getCoalescedEvents in api/PointerEvent.json. The pointerrawupdate entry was read again on 2026-09-19 and still gives Chrome 77, Firefox 148 (a partial version from 140 to 148) and no support in Safari. Licence: own work

How it works

This mouse polling rate test counts how many times a second your mouse reports its position: the mouse report rate, in Hz. It shows an average and a peak, or warns when the browser passes on one report per frame.

Read the full guide

How to test mouse polling rate properly

Sweep in quick, wide circles for the full five seconds. A mouse only sends a report when it has moved, so slow movement reads low whatever the setting. The average counts every report in the run. The peak is the busiest tenth of a second, and that is the figure to set against your mouse's setting.

Match your mouse Hz to a step

Report rates come in fixed steps. 125 Hz is the USB default, one report every 8 ms. 1,000 Hz is one every millisecond, the most that full-speed USB allows, and 8,000 Hz is the ceiling of high-speed USB.

  • A result between two steps, such as 700 Hz, points to slow movement or a busy computer. Press Run again.
  • Raise the DPI for high rates: at 800 DPI, 8,000 counts a second takes 10 inches of travel a second.
  • Plug the mouse or receiver straight into the computer, not a hub. The last five runs stay listed to compare.

Questions and answers

What is mouse polling rate?

It is how often the computer asks the mouse for news. The computer polls a USB mouse at a fixed interval, and the mouse answers with how far it has moved since the last poll. The rate is polls per second, in Hz.

Why does my result equal my monitor's refresh rate?

Browsers hand a page mouse movement once per frame, so an ordinary counter reads 60 on a 60 Hz screen. This test reads raw pointer updates, sent by Chrome, Edge and Firefox 148 or later. Safari sends none, so numbers there are coarser or absent.

Is the number exact?

No, it is an estimate. The page times only reports the browser passes on, and the browser and operating system add small delays. A figure just off a step, say 970 on a mouse set to 1,000 Hz, points to the measurement, not the mouse.

Is a mouse rate checker the same as a polling rate test?

Yes. Polling rate, report rate and mouse rate are names for the figure this page counts: how many reports a second a moving mouse sends, in hertz (Hz). A USB mouse reports only when polled, so the two rates match while it keeps moving.

More tests

Show 7 more

Browse Device Tests