<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Andrew Williams</title>
    <description>The latest articles on DEV Community by Andrew Williams (@andrew_williams_20edd340b).</description>
    <link>https://dev.to/andrew_williams_20edd340b</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4102659%2F8ddf4e80-f5a1-4023-ad4e-c7c1aa0a176d.jpeg</url>
      <title>DEV Community: Andrew Williams</title>
      <link>https://dev.to/andrew_williams_20edd340b</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/andrew_williams_20edd340b"/>
    <language>en</language>
    <item>
      <title>Your 1000 Hz Mouse Might Not Be Testing at 1000 Hz</title>
      <dc:creator>Andrew Williams</dc:creator>
      <pubDate>Mon, 31 Aug 2026 11:47:27 +0000</pubDate>
      <link>https://dev.to/andrew_williams_20edd340b/your-1000-hz-mouse-might-not-be-testing-at-1000-hz-57j</link>
      <guid>https://dev.to/andrew_williams_20edd340b/your-1000-hz-mouse-might-not-be-testing-at-1000-hz-57j</guid>
      <description>&lt;p&gt;Ever tested your mouse polling rate online and wondered why a 1000 Hz mouse sometimes shows something like 60 Hz or 144 Hz?&lt;/p&gt;

&lt;p&gt;The problem may not be your mouse. There is another possibility: the test is measuring the browser's rendering rate instead of the mouse's actual input reports. A common mistake with browser-based polling-rate tests is counting mouse movement once per screen frame. On a 60 Hz display, that can make a 1000 Hz mouse look like a 60 Hz device.&lt;/p&gt;

&lt;p&gt;Mouse polling rate ≠ monitor refresh rate.&lt;/p&gt;

&lt;p&gt;A better test needs to look at the actual mouse input events and their timing, not just how often the browser renders a frame. That's what &lt;a href="https://inputprobe.com/polling-rate-test/" rel="noopener noreferrer"&gt;InputProbe's polling rate test&lt;/a&gt; is designed to do.&lt;/p&gt;

&lt;p&gt;Move the mouse continuously and the test analyzes the incoming input reports. If there isn't enough reliable data, it doesn't simply make up a number.&lt;/p&gt;

&lt;p&gt;You can also use InputProbe to check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://inputprobe.com/dpi-test/" rel="noopener noreferrer"&gt;Mouse DPI&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://inputprobe.com/button-test/" rel="noopener noreferrer"&gt;Mouse buttons&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://inputprobe.com/double-click-test/" rel="noopener noreferrer"&gt;Double-click issues&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://inputprobe.com/keyboard-tester/" rel="noopener noreferrer"&gt;Keyboard input&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  The key takeaway:
&lt;/h4&gt;

&lt;p&gt;A good hardware test should measure what your device is actually reporting—not what your screen happens to be displaying.&lt;/p&gt;

&lt;p&gt;Try the tests at &lt;a href="https://inputprobe.com/" rel="noopener noreferrer"&gt;InputProbe&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>programming</category>
      <category>monitoring</category>
    </item>
  </channel>
</rss>
