Click Latency Test and Per-Model Notes

Click Latency Test: Measure Button Response Time

Click latency is the time between pressing a mouse button and the browser receiving the button-down event, and it determines how consistently your actions translate to in-game responses. Consistent click timing is only half the equation. High click latency means your click registers later than you pressed; inconsistent click latency means the delay varies unpredictably between actions, making timing-dependent skills harder to execute reliably.¹

This tool logs individual click latency values for each button press. Click within the tracking zone and see the time from physical press to browser event for each click, alongside the running average and per-button breakdown.

What determines click latency

Click latency has three hardware and software sources. First, the switch type: optical switches register when a light beam is interrupted, avoiding the contact bounce that mechanical switches must filter. Mechanical switches close metal contacts, and that contact can bounce before settling, so firmware or software debounce is needed to avoid false extra clicks.²³ Second, the USB polling cycle: a wired 1000 Hz mouse has a 1 ms polling period before the next report slot, so the click is reported in the next available polling interval after the switch fires.⁴ Third, the OS and browser input stack add scheduling overhead before the event reaches this page. All three combine to produce the value you see in this log.

To isolate each contributor, change one variable at a time. Moving from a hub to a direct motherboard port reduces USB scheduling contention, which can show up as a lower average latency and tighter per-click variance in the log. Reducing the debounce setting in companion software can reduce click latency, but it also raises the risk of double-click events on aged mechanical contacts because debounce exists to filter bounce. The individual log values let you verify whether a setting change reduced both the average and the high-end outliers, not just one of them.

Which variable to change first

Start with the variable that is easiest to reverse: port placement. A direct rear USB-A port removes hub contention without changing switch settings. If the log improves there, keep that path fixed and test debounce separately. This order prevents a debounce change from masking a USB issue. Working through port placement, power management, debounce, and firmware in that sequence ensures each change builds on a stable foundation rather than stacking untested variables on top of each other; if you change debounce first and the log improves, you still cannot tell whether the original problem was debounce or the USB hub you have not tested yet.

Optical vs mechanical click latency

Optical switches are designed to reduce one of the largest mechanical sources of click latency: contact bounce. Because they detect the button state with a light beam instead of metal contacts, optical designs can avoid the debounce delay required by many mechanical switches.² Mechanical switches are not inherently unusable, but their bounce behavior varies by switch model, age, and firmware debounce setting. Aged mechanical switches can produce more bounce as contacts oxidise with wear, which can create occasional high-latency outliers in the log even when the switch otherwise functions correctly.⁴ The log view in this tool makes this pattern visible by showing individual click values rather than only averages.

Aging effects on mechanical switch variance

Aged mechanical switches often show increasing outlier frequency before the average latency rises noticeably. As contacts oxidise, bounce patterns become less predictable, and individual click events can occasionally land outside the debounce window. This appears in the log as isolated high-latency results surrounded by otherwise normal values. A small number of outliers per session can be normal for older switches, but tracking the outlier count week over week reveals whether the switch is gradually degrading or still stable. Consistent outliers on most clicks suggest that increasing the debounce window, updating firmware, or replacing the switch should be evaluated.

Troubleshooting high or inconsistent click latency

Start with USB port placement: move to a direct rear motherboard port if you are using a hub or front-panel header. Then check OS power management: disable USB selective suspend in Windows Device Manager, because Windows can suspend an idle USB device until the driver requests the working state again.⁵ Next, check your mouse's companion software for debounce settings; a very long debounce window can add click latency. Finally, update firmware, which sometimes includes debounce tuning. Consistent latency above your normal baseline after all setup steps points to a software or OS conflict rather than the mouse hardware. Inconsistent values with frequent high outliers on a mechanical mouse suggest switch wear.

Separating configuration problems from hardware faults uses the log view most effectively. A mouse reading high latency on every click with low variance is likely set to a long debounce window; reduce it in companion software and retest. A mouse with a low average but frequent spikes points to USB scheduling interference, OS scheduling delays, or a background process briefly blocking the input stack. Average-only readings conceal the spike pattern that individual log values expose.

Building a repeatable click test

Click 20 times at a steady pace, then repeat the same 20 clicks after one setup change. Keep the button, hand position, USB path, and background apps constant so the comparison isolates the variable you changed. This makes the log more useful than a single average taken from a noisy session. Recording the average, the spread, and the number of double events for each 20-click sample gives you three concrete metrics to compare before and after any change, so you can see whether a debounce adjustment reduced latency, increased double events, or produced no meaningful effect.

Comparing the 20-click blocks across sessions shows whether a fix held or drifted back over time. A debounce reduction that lowers the average this week but lets double events creep up next week is not a clean win, so track both metrics each time. When the average, the spread, and the double-event count from this click latency log breakdown all move the right way after one change, you have a result you can trust and reproduce on demand.

When to use this

Use this test when evaluating a new mouse purchase, after a firmware update, when suspecting switch degradation, or when comparing optical and mechanical switch mice side by side.

Examples

Glorious Model O3 Wireless Input Lag Test

Hot-swappable batteries meet 8000 Hz wireless in the Glorious Model O3 Wireless. Glorious's InfinitePlay system lets you swap a depleted battery for a charged one in seconds, and the mouse lists a 66 g closed-shell design, BAMF 3.0 30K optical sensor, optical switches, and up to 8000 Hz polling.¹

Use this tool to verify your O3 Wireless is reporting at 8000 Hz and to measure click latency.

Specifications¹

8000 Hz on the 2.4 GHz dongle

For the Model O3 Wireless, 8000 Hz is the ceiling on its dedicated 2.4 GHz wireless channel. At 8000 Hz, position reports arrive every 0.125 ms. For this browser test, seat the dongle in a rear motherboard USB-A port rather than a hub. Your Hz chart should read close to 8000 on Chrome, Edge, or Firefox when the browser exposes coalesced pointer events; a ceiling at 1000 Hz typically indicates OS input coalescing or USB power-management delays.² Disable USB selective suspend in Windows Device Manager if power-management delays appear.³

For battery-powered wireless mice, maintaining a fully seated, charged battery before testing removes battery state as a variable in your measurements. The O3 Wireless uses Glorious's InfinitePlay hot-swap battery system, so confirming the active battery is seated and the contacts are clean helps rule out intermittent power interruptions before you investigate RF or USB path issues.

Battery state before RF troubleshooting

A low or poorly seated battery can create symptoms that look like wireless contention. Reseat a charged pack, clean the visible contacts if needed, and run a short movement sample before changing dongle placement. If the chart stabilizes after that check, the first result likely reflected power contact rather than RF performance. The InfinitePlay system makes battery swaps quick, but each swap is an opportunity for the contact pins to collect dust or develop mild oxidation; a quick visual inspection of the battery bay before every test session catches this early and prevents you from chasing an RF problem that is actually a power delivery issue.

Optical switches without contact bounce

Glorious optical switches in the O3 Wireless use light-beam actuation with no contact bounce. Mechanical contacts, by contrast, bounce for several milliseconds before settling, which is why they need a firmware debounce filter.⁴ The switch registers the moment the beam breaks; no mechanical contact closure, no debounce filter. Consequently, click latency in this test should consistently fall below 2 ms. Building on this, optical switches do not degrade through mechanical wear the way contact switches do, so latency variance should remain consistent over the mouse's lifetime. Yet the hot-swap battery system adds a thin layer of power management between the battery and switch electronics; if the battery contact is dirty or worn, you may see intermittent polling drops unrelated to the switch itself.

Because the O3 Wireless uses optical switches without mechanical contacts, the primary failure mode to watch for in the click log is battery bay contact issues rather than switch contact degradation. If the log shows sporadic double events that do not appear when you press the button slowly, inspect the battery bay for debris or mild corrosion on the contact pins. Cleaning the pins with isopropyl alcohol and a cotton swab, then reseating the battery, resolves most intermittent click event issues on this model that are unrelated to switch age or debounce configuration.

Battery and contact checks before a session

Before testing, confirm the battery is fully seated and the hot-swap contacts are clean; dirty contacts can cause intermittent power interruptions that appear as polling dropouts in the chart. The mouse's report interval is fixed in firmware as the interrupt endpoint's bInterval value, which drivers cannot change, so a persistent ceiling at 1000 Hz has to originate on the host side.⁵ Connect via the 2.4 GHz dongle and confirm 8000 Hz is selected in Glorious Core software. Your Hz chart should read near 8000 with low variance. If you see intermittent red dropout lines that USB contention does not explain, inspect the battery bay contacts and clean them with isopropyl alcohol.

Two physical checks before each test session

Two physical checks take under 30 seconds and eliminate the most common sources of anomalous readings on the O3 Wireless. First, press the battery firmly into the bay until you feel it seat; a loose contact produces intermittent polling drops that appear as red vertical lines in the Hz chart. Second, confirm the dongle is in a direct rear motherboard USB-A port rather than a hub; hub placement elevates Hz variance and reduces the chart resolution for identifying genuine polling problems versus environment-caused contention.

Battery contact checks before blaming wireless latency

If the battery is seated but the chart still shows intermittent dropouts, remove it, inspect the contacts, and reseat it once more. A clean contact can eliminate false wireless-latency conclusions without changing dongle placement, software, or polling profile. On the O3 Wireless, the battery bay contacts are exposed to pocket lint and desk dust more than on a sealed wireless mouse, so periodic cleaning with a dry cotton swab prevents the gradual buildup that causes intermittent disconnects. If cleaning the contacts does not resolve the dropout pattern, test with a second battery pack to rule out a faulty cell before investigating the dongle or USB path.

Running a second 15 second movement sample in this O3 battery contact dropout trace after any physical fix confirms whether the change solved the problem or merely shifted it. If the red dropout lines disappear in the second sample and stay gone, the contact was the cause. If they return, the issue is genuinely in the wireless path and you should move the dongle before assuming a deeper fault. This two-sample habit prevents you from declaring victory on a result that was simply momentary.

HyperX Pulsefire Haste 2 Input Lag Test

8000 Hz at a budget-accessible price point arrives with the Pulsefire Haste 2. HyperX's wired-only honeycomb mouse weighs 53 g, supports up to 8000 Hz polling over USB, and uses custom HyperX switches rated for up to 100 million clicks.¹

The honeycomb shell reduces weight without compromising rigidity. Use this tool to confirm your Pulsefire Haste 2 is delivering 8000 Hz and to measure click latency.

Specifications¹

Wired polling from 125 to 8000 Hz

The Pulsefire Haste 2 supports 125, 500, 1000, 4000, and 8000 Hz polling over its wired USB-A connection, with 1000 Hz as the default setting. At 8000 Hz, position reports arrive every 0.125 ms. Wired-only design means polling rate is not limited by wireless radio bandwidth; the USB cable and your system's USB controller are the only variables. For this browser test, connect directly to a rear motherboard USB-A port. At 8000 Hz, the Hz chart should read near 8000 on Chrome, Edge, or Firefox when the browser exposes coalesced pointer events; a ceiling at 1000 Hz can mean the OS input pipeline is coalescing reports before the page receives them.² Disabling USB selective suspend in Windows Device Manager typically resolves power-management delays.³

Wired-only design eliminates wireless radio latency entirely and means port quality determines your Hz reading directly. At 8000 Hz over USB-A, the Haste 2 sends eight reports per millisecond; the chart should read near 8000 on Chrome, Edge, or Firefox with USB selective suspend disabled. If the reading caps at 1000 Hz, confirm the polling rate is set to 8000 Hz in HyperX NGENUITY and check that the mouse is in a direct rear motherboard port rather than a front-panel header or hub.

Why a wired 8000 Hz mouse can still cap at 1000 Hz

A 1000 Hz ceiling usually means the OS input path is coalescing reports before the page receives them, or the active NGENUITY profile did not apply. A direct rear motherboard port, a firmware check, and a 15 second movement sample help separate a real reporting issue from a browser or USB power-management limitation. On the Haste 2 specifically, confirming that NGENUITY shows 8000 Hz in the active profile and that the setting was applied rather than just selected resolves most cases; the software requires clicking Apply before the new rate takes effect, and the mouse must be reconnected afterward for the change to persist in onboard memory.

HyperX mechanical switches and debounce

HyperX custom switches in the Haste 2 provide tactile, audible feedback and are rated for up to 100 million clicks. Because a mechanical contact bounces for several milliseconds before settling, firmware has to apply a debounce window to filter it.⁴ Actuation behavior depends on the switch mechanism and firmware debounce setting, so click latency in this test can vary with debounce configuration, USB polling, and OS scheduling. Expect low single-digit latency on a well-configured unit, but do not treat the switch as optical unless your specific firmware or support material identifies it that way.

Comparing Haste 2 click feel to optical designs

Comparing the Haste 2 to optical-switch mice shows why debounce matters: optical designs remove contact bounce at the detection stage, while mechanical-style switches rely on firmware to filter bounce. The Haste 2's click feel can still be fast and consistent, but the latency profile depends on debounce and polling configuration rather than optical actuation alone. In the click latency log, this means the Haste 2 typically shows a slightly wider spread than an optical mouse at the same polling rate, reflecting the firmware debounce window that optical switches can bypass entirely.

Setting the rate in NGENUITY and confirming it

Connect to a direct rear USB-A port and confirm the polling rate setting in HyperX NGENUITY software before testing. At 8000 Hz, your Hz chart should read close to 8000. The mouse's report interval is fixed in firmware as the interrupt endpoint's bInterval value, which drivers cannot change, so a persistent ceiling has to originate on the host side.⁵ If you observe a consistent ceiling at 4000 Hz despite selecting 8000 Hz in NGENUITY, apply any pending firmware update. The Pulsefire Haste 2 is not widely reported to have double-click issues, but if they occur, increasing the debounce threshold in NGENUITY is the first step to resolve it.

If NGENUITY shows 8000 Hz selected but the chart reads 4000 Hz, a firmware update resolves this on most units. Open NGENUITY, navigate to the mouse firmware section, and check for available updates. After applying any update, reconnect the mouse and retest. The Haste 2 does not store firmware changes in a way that persists through USB power cycling on some early production units; if the ceiling returns to 4000 Hz after reconnecting, the firmware update may need reapplication before the setting becomes permanent.

Confirming the update actually changed the reporting path

After any firmware update, run the same movement sample before changing other settings. If the chart returns to 8000 Hz and stays there for 15 seconds, the update likely changed the reporting path. If it drops back after reconnecting, repeat the update or check whether the mouse is entering a fallback mode that your current software version does not preserve.

Documenting the firmware version and the NGENUITY build before testing removes a silent variable that many users overlook. A mismatch between the mouse firmware and the software version can leave a 4000 Hz fallback active even after you think the update applied. Recording both numbers each session lets you confirm the change stuck rather than assuming the rate improved because the chart briefly rose. This habit, paired with a saved chart from this Haste 2 firmware 8000 Hz fix, turns a one-off good reading into a repeatable result you can trust.

Logitech G Pro X Superlight 2 Input Lag Test

At 60 g, the G Pro X Superlight 2 pairs LIGHTSPEED wireless with an 8000 Hz max report rate; the DEX version lists 4000 Hz wireless and 1000 Hz wired.¹² Its LIGHTFORCE hybrid switch combines a physical spring-loaded lever with an optical beam at the actuation point, preserving tactile feel while avoiding mechanical contact bounce.³ Use this tool to measure click latency from button press to browser event and to verify your polling rate.

The symmetrical design accommodates palm, claw, and fingertip grips equally.

Specifications¹

Standard and DEX polling limits

For the standard G Pro X Superlight 2, LIGHTSPEED wireless supports up to 8000 Hz polling; the DEX version supports up to 4000 Hz wireless and 1000 Hz wired. Both versions also support USB-C charging/data operation, but the Hz chart reflects the active report-rate setting and the receiver or cable path you use for testing. LIGHTSPEED assigns a dedicated radio channel, so other 2.4 GHz devices do not contend for bandwidth on the wireless link. For this test, confirm the active polling rate in Logitech G HUB before starting; the current rate persists in onboard memory and the Hz chart will reflect whatever rate the mouse is configured for.

If the chart reads near 4000 Hz, check whether you are using the DEX version rather than the standard Superlight 2; the DEX variant's higher wireless polling rate produces a different chart baseline from the standard 8000 Hz model. Confirming which version you have before interpreting results saves diagnostic time. Both versions read accurately with this tool; the DEX at its configured 4000 Hz wireless rate and the standard model at its configured 8000 Hz rate both reflect normal operation rather than any configuration problem.

Identifying the standard and DEX variants before troubleshooting

Check the product label or G HUB model name before assuming a low reading is a fault. A DEX chart near 4000 Hz can be correct, while the standard Superlight 2 should read closer to 8000 Hz when configured for its maximum wireless rate. Version identification prevents unnecessary firmware changes and keeps the diagnosis tied to the mouse you actually have.

LIGHTFORCE hybrid switches on the Superlight 2

LIGHTFORCE is a hybrid design that places an optical beam at the physical lever's actuation point.³ The lever provides traditional tactile feel while the beam registers the event without contact bounce. Eliminating contact bounce removes the debounce filter mechanical switches require, typically 2 to 5 ms. Consequently, click latency in this test should consistently fall below 2 ms on most setups. The pre-tensioned lever design also means actuation force is consistent across the full button surface, which reduces the variation you see between clicks in the latency log.

Why LIGHTFORCE latency stays consistent across the full button surface

The pre-tensioned lever in LIGHTFORCE places the optical beam at a specific point on the travel arc, so the beam fires at the same positional moment regardless of where on the button surface your finger contacts. Side-of-button presses and center presses both interrupt the beam at the same lever position. This mechanical consistency produces click latency values in the log that show low per-click variance; it contrasts with mice where off-center contact changes the effective actuation depth before the beam fires, which produces wider log scatter.

Dongle placement and version checks

Place the LIGHTSPEED dongle in a direct rear USB-A port on your motherboard. Close other applications to minimise OS scheduling noise in the measurements. Your Hz chart should read near the configured polling rate with low variance. If you see a reading significantly below your configured rate, check that USB selective suspend is disabled in Windows Device Manager.⁴ The mouse's own report interval is fixed in firmware as the interrupt endpoint's bInterval value, which drivers cannot change, so a persistent shortfall in the chart has to originate on the host side.⁵ The Superlight 2 is not commonly reported to double-click, but if you see repeated button events from a single physical press, apply any pending firmware update in G HUB.

After confirming a correct polling rate reading, run the click latency log by clicking 20 times at a steady pace inside the tracking zone. For the Superlight 2, expect values to cluster between 0.5 and 2 ms with low per-click variance. Values that consistently read 3 ms or above on a Superlight 2 in good condition usually point to OS scheduling interference rather than LIGHTFORCE behavior; close background applications and retest to isolate whether a process is blocking the input stack between clicks.

Why version identification matters before troubleshooting

Confirm whether your mouse is the standard Superlight 2 or the DEX model before interpreting a low polling-rate reading. The DEX model has a different wireless ceiling, so a 4000 Hz chart can be correct on that version and incorrect on the standard model. Version checks prevent unnecessary firmware changes when the expected rate is simply different. Checking the product label or the model name displayed in G HUB before running any diagnostic test saves time and prevents false conclusions; a DEX unit reading 4000 Hz is operating correctly, while a standard Superlight 2 reading 4000 Hz when set to 8000 Hz indicates a genuine delivery problem worth investigating.

Running the polling check and click log back to back in this Superlight 2 polling and click pair, from the same USB port, gives you the most meaningful comparison because both readings share one input path. When the Hz chart holds at the configured rate but the click log shows scatter, the issue is almost always scheduling or press technique rather than the wireless link. Treat a stable chart as your anchor before chasing switch-level causes that the data does not support.

Logitech G PRO X2 SUPERSTRIKE Input Lag Test

The G PRO X2 SUPERSTRIKE changes the measurement story before you click the first sample. H.I.T.S. replaces traditional microswitches with an inductive haptic design that can tune actuation, reset points, and click feel.¹ At up to 8000 Hz and 60 g over LIGHTSPEED wireless, it targets players who want fast registration with an actively calibrated physical response.

The symmetrical shape and long wireless battery life make it viable for both tournament and daily use. This tool measures click latency and verifies that your mouse is reporting at its rated polling rate.

Specifications²

8000 Hz over LIGHTSPEED 2

Operating at up to 8000 Hz over LIGHTSPEED 2 wireless, the G PRO X2 SUPERSTRIKE can deliver position updates every 0.125 ms when that report rate is active. At 8000 Hz, position updates arrive every 0.125 ms, while lower configured rates produce proportionally longer intervals. Your Hz chart should read close to the configured rate on browsers that support the getCoalescedEvents() call this tool uses for high-frequency measurements.³ If the chart reads below the configured rate, check the G HUB report-rate setting, reconnect the LIGHTSPEED adapter, and retest before assuming mouse hardware failure.

Verifying that 8000 Hz is active requires the configured profile to be applied in G HUB and the LIGHTSPEED adapter to be connected directly to the computer. Before attributing a below-rated reading to hardware, confirm the polling-rate setting, reconnect the dongle, and retest. USB-C wired testing is useful for isolating whether a wireless polling issue is radio-related, while a direct USB path helps rule out hub or adapter contention.

Using wired mode to isolate wireless polling issues

USB-C wired testing separates the mouse hardware from the LIGHTSPEED radio path. If wired mode holds the configured rate but wireless mode does not, move the dongle, remove nearby 2.4 GHz transmitters, and retest before changing haptic or actuation settings. If both modes read low, the active G HUB profile or USB path is the better place to investigate. This two-mode comparison is especially valuable on the SUPERSTRIKE because the H.I.T.S. haptic actuator behaves identically in both modes; the only variable that changes is the radio link, so any polling rate gap between wired and wireless directly reflects the wireless path quality rather than a switch or firmware difference.

Inductive H.I.T.S. switches and haptic clicks

H.I.T.S. is a novel switch design. Logitech describes it as replacing traditional microswitches with inductive sensing and haptic feedback, while G HUB exposes actuation point, rapid-trigger reset, and click-haptic controls.⁴ The mechanism is designed to reduce the latency path associated with traditional contact switches and to provide consistent feedback without relying on a mechanical spring.¹ Because the actuator and firmware layer sit between finger input and the final USB report, measured click latency still includes the browser, OS, and USB delivery path rather than only the switch mechanism.

For players comparing the H.I.T.S. actuator feel to traditional mechanical switches, the click latency log shows timing results rather than a feel comparison. Optical or inductive beam detection fires independently of when the actuator delivers its haptic pulse, so the measured click latency reflects the registration event rather than the subjective perception of the click sensation. The log is most useful for comparing average latency and spike patterns across settings on the same setup.

Low wireless readings and the wired comparison

Seat the LIGHTSPEED dongle in a rear motherboard USB-A port rather than a hub. G HUB can run in the background without affecting measurements, but closing unnecessary applications reduces OS scheduling noise in the results. The mouse's own report interval is fixed in firmware as the interrupt endpoint's bInterval value, which drivers cannot change, so a shortfall in the chart has to originate on the host side.⁵ Your Hz reading should stay near the configured polling rate with low variance. If the chart consistently reads below 8000 Hz when 8000 Hz is configured, confirm the G HUB setting, reconnect the adapter, and retest before treating it as a hardware limitation. USB-C wired testing is useful for isolating whether a wireless polling issue is radio-related or profile-related.

Diagnosing a low wireless polling-rate reading

When the chart reads below 8000 Hz over LIGHTSPEED, testing with the adapter in a direct rear USB-A port is the most effective first step to isolate radio or adapter contention. If the reading recovers after moving the adapter, the wireless path was the constrained element. If the reading remains below the configured rate, reopen G HUB, confirm the polling-rate setting, click Apply, and reconnect before retesting.

Separating wireless polling from click latency

A low wireless polling-rate reading and a high click-latency reading do not always share the same cause. First confirm the Hz chart holds near the configured rate; then run click latency with the same adapter position and background state. If the Hz chart is stable but click spikes remain, inspect debounce, firmware, and press consistency before assuming the wireless link is unstable.

Keeping the dongle's surroundings consistent between runs removes the most common source of confusion in wireless tests. Nearby 2.4 GHz transmitters, metallic surfaces, and USB 3.0 ports can all perturb the LIGHTSPEED link without any change to the mouse itself. When you retest with this LIGHTSPEED dongle radio check after moving the dongle and the chart recovers, you have confirmed a radio-path problem rather than a switch or firmware fault, which tells you exactly where to focus the fix.

Razer DeathAdder V3 Input Lag Test

DeathAdder V3 is an ultra-lightweight ergonomic mouse at 59 g.¹ Its wired design can be configured up to 8000 Hz, with 1000 Hz as the default polling rate.² It uses Razer Optical Mouse Switches Gen-3 for fast, consistent gameplay response.

Specifications¹

HyperPolling up to 8000 Hz

By default, the DeathAdder V3 reports at 1000 Hz over USB-A, and Razer Synapse can configure it up to 8000 Hz with HyperPolling. At 1000 Hz, each position update arrives every 1 ms. The V3 Pro wireless variant uses Razer HyperSpeed 2.4 GHz, so treat wired and wireless readings as separate baselines rather than assuming one setup will match the other.

Plugging the V3 into a rear USB-A port before opening the test eliminates a common source of Hz variance on this model. Front-panel headers and USB hubs share bandwidth with other connected devices, which can produce an uneven Hz chart even when the mouse hardware is functioning correctly. If your reading on a rear port still sits well below the configured rate, check Windows USB power-management settings; disabling USB selective suspend is a reasonable check when a wired mouse repeatedly reconnects or reads below its configured rate.³

A direct port also gives you a cleaner baseline for comparing settings. Run the same 15 second movement sample after each change, such as port selection, polling profile, or Synapse background state. Keeping the movement pace and duration consistent prevents the chart from rewarding a lucky burst rather than a stable configuration.

Gen-3 optical switches without debounce

Optical mouse switches use light-based actuation rather than contact closure, so they avoid the contact-bounce problem that mechanical switches need to filter.⁴ Razer describes the DeathAdder V3 gen-3 switch as having no debounce delay and 0.2 ms actuation. Mechanical switches require firmware debounce because metal contacts bounce for several milliseconds before settling.⁴ Consequently, click latency measurements in this tool should generally run lower and more consistently than on mechanical mice.

Gen-3 click latency compared to earlier optical designs

Gen-3 Razer optical switches improve on earlier designs through light-based actuation rather than contact closure. In the click latency log, this means optical-switch readings are less affected by contact bounce than mechanical-switch readings. Readings that spread across a wider range, such as some clicks at 1 ms and others at 4 ms, usually trace to OS scheduling variation rather than the switch itself.

Separating switch behavior from system noise

Use the individual click log to separate a switch issue from a noisy system path. A stable switch produces a tight cluster even when the average moves slightly between runs. If only one session produces tall spikes, close background apps, keep the dongle or cable path unchanged, and retest before changing firmware settings. Comparing the spread of values within a single session against the spread across multiple sessions on the same USB port tells you whether the variation originates in the switch mechanism or in OS scheduling; consistent within-session spread points to switch behavior, while session-to-session differences point to system load.

Reading the click log after each change

Plug the DeathAdder V3 into a rear USB-A port on your motherboard. Your Hz chart should read close to the configured polling rate; a reading well below that points to USB contention rather than a mouse problem. The reporting interval itself is fixed in the mouse's firmware as the interrupt endpoint's bInterval value, which drivers cannot change, so a shortfall has to come from the host side.⁵ If the log shows two button events per physical press, check your Synapse profile and firmware state before concluding the switch is faulty.

Reading the click log after each setup change

If double events continue after checking profile settings, compare a wired baseline with a clean USB path before changing hardware assumptions. Gen-3 optical switches do not develop contact bounce, but aggressive click-response settings can still affect how rapid intentional presses are reported. Adjusting click response one step toward the slower setting in Synapse and retesting with 20 deliberate clicks confirms whether debounce configuration is the cause rather than a firmware fault.

For a useful diagnosis, record the average and the spread, not only the lowest value. A low average with many spikes usually points to system scheduling or USB contention. A consistently high average with low spread points more directly to debounce, firmware, or press technique. This DeathAdder V3 latency spike source gives you a practical next step instead of treating every outlier as a hardware fault.

Razer DeathAdder V4 Pro Input Lag Test

Razer positions the DeathAdder V4 Pro as a lighter wireless version of its right-hand ergonomic identity, with the black model starting at 56 g and other finishes listed up to 58 g, while HyperSpeed Wireless Gen-2 and wired USB both support up to 8000 Hz polling.¹ Razer pairs the chassis with a Focus Pro 45K Optical Sensor Gen-2 and Razer Optical Mouse Switches Gen-4, so this page is aimed at players who want to verify the mouse is actually reporting at its configured rate.

Use this tool to measure click latency from the primary button press to the browser event and to watch whether your Hz chart stays near 125, 500, 1000, 4000, or 8000 Hz depending on the active Synapse profile.

Specifications²

HyperSpeed Gen-2 and wired 8000 Hz

The V4 Pro reaches up to 8000 Hz through Razer HyperSpeed Wireless Gen-2 or a wired USB connection. For the wireless test, use the HyperSpeed dongle in a direct rear motherboard USB-A port and keep other 2.4 GHz transmitters away from the signal path. Your Hz reading reflects the browser's getCoalescedEvents() output, which exposes un-coalesced pointer changes where the browser supports that API.³ Confirm the active polling rate in Razer Synapse before testing; the mouse stores the last-used Synapse profile in onboard memory, and the chart will follow the rate the mouse is currently configured to report.²

A chart near 1000 Hz usually means the mouse is running a 1000 Hz profile, the dongle is not connected correctly, or the OS input path is coalescing reports. If the chart shows intermittent drops, move the dongle to a direct rear USB-A port, close unnecessary background applications, and retest before changing the mouse profile again. The key comparison is not a single click value, but whether the Hz chart holds close to the configured rate with low variance.

Why 8000 Hz can still read as 1000 Hz

An 8000 Hz-capable mouse can still report a 1000 Hz chart when the active profile, dongle path, or browser event path is not passing every high-frequency sample. That result does not prove the mouse is faulty; it tells you which part of the input chain to check first. Reconfirm the Synapse profile, reconnect the adapter, and compare the chart before changing switch or actuation settings.

Gen-4 optical switches and grip shape

Razer describes the Gen-4 optical switches as redesigned from the ground up, with improved tactility, speed, and a click lifecycle rated above 100 million actuations.¹ In this browser test, the optical beam registration removes the contact-bounce behavior associated with mechanical switches, but the logged click latency still includes browser event handling, OS scheduling, USB delivery, and your own press consistency.

How shape affects click latency variance

The V4 Pro's right-hand contour gives palm and claw grip players a larger contact area under the primary button. That can make repeated presses land at a similar depth and angle, which often reduces scatter in the click latency log. It does not make the browser report a lower hardware latency number by itself; it mainly helps you compare settings without grip position changing between clicks.

Wired and wireless baselines on the V4 Pro

Set the polling rate in Synapse first, then close Synapse if you want the cleanest baseline measurement. Run the test with the dongle in a direct rear USB-A port or with the mouse connected by its USB cable, then compare the chart against the configured rate rather than against a marketing maximum. If the Hz chart drops intermittently, check whether Windows USB selective suspend is affecting the port before assuming the mouse cannot hold the selected rate.⁴

For click latency, click 20 times at a steady pace inside the tracking zone and look for the average and the spread of the log. A few high outliers are more likely to come from scheduling noise than from the switch, while a consistent pattern across wired and wireless modes points to a setup issue worth isolating. Test one change at a time: dongle position, polling profile, USB cable path, then background applications.

Interpreting wired and wireless baselines separately

A wired baseline is useful because it removes the 2.4 GHz path from the diagnosis. If wired readings hold near the configured rate but wireless readings drop, investigate dongle placement, battery level, and nearby RF sources. If both paths behave the same, the more likely cause is the polling profile, USB path, or system scheduling rather than the wireless link.

Logging the battery level alongside the polling profile keeps wireless comparisons honest because a low charge can force the mouse to reduce its report rate before you notice. Run a wireless baseline in this DeathAdder V4 battery latency check with the battery above half and compare it to the same profile on a full charge if the chart dips. A drop that tracks battery level is a power-management effect, not a fault in the switch or the wireless receiver. The mouse's own report interval is fixed in firmware as the interrupt endpoint's bInterval value, which drivers cannot change, so a persistent shortfall in the chart has to originate on the host side.⁵

Razer Viper V3 Pro Input Lag Test

Razer's Viper V3 Pro is a 54 g wireless esports mouse with HyperSpeed wireless, HyperPolling 8000 Hz, a Focus Pro 35K Optical Sensor Gen-2, and Razer Optical Mouse Switches Gen-3.¹

This tool measures click latency and verifies that your Viper V3 Pro is reporting at 8000 Hz, the polling rate that defines its competitive positioning.

Specifications¹

8000 Hz over HyperSpeed and USB

Supporting up to 8000 Hz over HyperSpeed 2.4 GHz wireless and wired USB-A, the Viper V3 Pro can deliver a 0.125 ms report interval when that rate is active.² The V3 Pro uses the HyperSpeed dongle and wired USB-A; Bluetooth is not a V3 Pro connectivity mode. For this browser test, seat the dongle in a rear motherboard USB-A port. Your Hz chart should read close to 8000 on Chrome, Edge, or Firefox when the browser exposes coalesced pointer events; a ceiling at 1000 Hz can come from browser coalescing or OS input coalescing.³ Confirm the polling rate in Razer Synapse before testing; the V3 Pro supports 125, 500, 1000, 4000, and 8000 Hz.

Confirming 8000 Hz on the V3 Pro in three steps

Confirming the full 8000 Hz rate requires three conditions. First, open Synapse and verify 8000 Hz is selected in the performance settings. Second, seat the HyperSpeed dongle in a rear motherboard USB-A port, not a hub or front-panel header. Third, open Device Manager, find each USB Root Hub, and confirm USB selective suspend is disabled under Power Management; disabling it can address power-management delays.⁴ Meeting all three conditions and running this test for 15 seconds produces a chart that sustains near 8000 Hz; missing any one of them can produce a lower ceiling.

Gen-3 optical switches and session averages

Gen-3 Razer optical switches register via a light beam at the actuation point with no mechanical contact. Mechanical contacts bounce for several milliseconds before settling, which is why they need a firmware debounce filter.⁵ This eliminates the debounce window required by mechanical switches. Consequently, click latency in this test should consistently fall below 2 ms. The V3 Pro's flat hump and forward button position place your finger at a direct contact angle, which tends to produce lower click-latency variance than mice with more curved profiles. Building on this, the gen-3 optical switch design has a strong reliability track record in high-click-count esports use; double-click events are rare and typically indicate a firmware debounce issue rather than switch wear.

For players running the V3 Pro at competitive events, the flat shape and forward button placement produce consistent actuation geometry that makes per-session click latency highly repeatable. Comparing click latency averages across multiple test sessions on the same unit shows low variance because grip style and button contact angle stay stable for most players with a defined preferred grip. If your per-session averages vary by more than 1 to 2 ms, the more likely cause is a difference in OS background load between sessions rather than any change in the switch hardware.

Why one-session averages can mislead

One session can look unusually clean if background load is low or unusually noisy if a background process blocks the input stack. Compare at least two short runs with the same dongle position and background state before changing settings. The pattern across sessions is more trustworthy than a single best value. On the V3 Pro, a well-configured unit at 8000 Hz should sustain a tight cluster across multiple sessions; if one run shows 0.8 ms average and the next shows 2.1 ms with the same USB path and no hardware change, the difference almost certainly comes from OS scheduling variance rather than the mouse itself.

Comparing against community baselines

Confirm the polling rate in Synapse and seat the HyperSpeed dongle in a rear USB-A port before running the test. Close Synapse and other background applications to minimise OS scheduling noise. Your Hz chart should read near 8000 with low variance. The V3 Pro is the most widely tested mouse in community polling rate tests; if your reading differs significantly from 8000 Hz after verifying the setup, the likely cause is USB selective suspend on your system rather than a mouse hardware fault. Disable USB selective suspend in Windows Device Manager's Power Management settings, then retest.

Testing on a community-benchmarked mouse model like the V3 Pro has a practical advantage: there is a large body of reference data from other users for comparison. A reading near 8000 Hz in this tool matches what the community consistently reports for correctly configured units. A reading substantially below that, after confirming your setup against the three-step checklist above, helps distinguish between a genuine hardware issue and a configuration problem; the V3 Pro's well-understood baseline makes out-of-range readings easier to investigate than on less widely tested models.

Comparing community baselines without overfitting

Community data is useful as a sanity check, not as a promise that every unit must match exactly. Your browser, USB controller, background processes, and grip pressure all affect the final number. Treat a nearby 8000 Hz reading with low variance as a good sign, and investigate only when the chart repeatedly misses the expected baseline under the same setup.

Saving the chart image from each session in this Viper V3 saved chart library builds a personal reference library that beats memory when you revisit a setup months later. A saved near-8000 Hz chart with the dongle port and background state noted lets you spot slow drift in your own hardware before it becomes a problem. Treat those saved charts as your own baseline rather than chasing the exact figure another user posted, because USB controller and browser differences make perfect matches unlikely.

Zowie EC2 Input Lag Test

For players who want a driverless baseline, the EC2 keeps polling rate, DPI, and button behavior in hardware. ZOWIE lists it as a medium ergonomic mouse with a 3360 sensor, 400/800/1600/3200 DPI, 125/500/1000 Hz report rate, 5 buttons, and 90 g weight.¹ Use this tool to verify click latency and button response without installing drivers on Windows.

Specifications¹

Setting the report rate with buttons 4 and 5

The EC2's report rate is a hardware setting, not a software profile. ZOWIE's FAQ says to unplug the mouse, hold button 4+5 for 125 Hz, button 5 for 500 Hz, or button 4 for 1000 Hz, then plug it in until the wheel lights up.² At those rates, reports arrive every 8 ms, 2 ms, and 1 ms respectively. Run this test after setting the rate; the Hz chart reflects whatever rate is active, not the rate you intended. Because polling rate is set at connection time, reconnecting is necessary to switch rates.

Confirming the active polling rate before running any latency test saves time on the EC2 because the rate is set during plug-in only. If the chart reads near 500 Hz when you expected 1000 Hz, unplug the cable and repeat the 1000 Hz button-hold procedure on reconnect; the polling rate changes only at plug-in. A reading near the expected rate with low variance confirms the correct rate is active before you proceed to click latency measurements.

Checking rate before interpreting click latency

Run a short movement sample before the click test so the Hz chart confirms the active polling rate. If the chart shows 500 Hz while you intended 1000 Hz, click latency will still be valid as a browser measurement, but it will not represent the setup you meant to test. Reconnect with the correct button held, then rerun both measurements.

Mechanical switches with fixed debounce

Mechanical contact switches can bounce briefly after actuation; firmware debounce filters those secondary transitions so one press registers cleanly.³ The EC2 has no software-adjustable debounce threshold, so switch condition and firmware handling are the main variables. In this browser test, expect click latency to vary with polling rate, OS scheduling, USB polling jitter, and button travel before actuation.⁴

When double-click behavior appears on the EC2

Double-clicking can come from worn or unstable mechanical contacts. Because the EC2 is driverless, there is no app slider for debounce; repair or warranty support is the practical path if retesting does not clear the issue. Switch replacement is a repair task rather than a quick settings change, so treat it as a repair rather than a routine adjustment. Before pursuing replacement, rule out USB path issues by testing from a direct rear motherboard port with no other devices on the same hub; a noisy USB connection can occasionally produce duplicate events that mimic contact bounce but disappear when the port path is cleaned up.

Driver-free testing at each rate

The EC2 requires no driver software, which makes testing straightforward. Plug into a rear USB-A port, confirm the polling rate, then start the test. Your Hz chart should read near the expected rate with low variance. A common issue is an EC2 remaining at 500 Hz when 1000 Hz is intended; polling rate is only set during plug-in, so reinserting with the correct button held is necessary to switch. Persistent readings below the expected rate that survive a port change may involve Windows USB power management; Microsoft documents selective suspend as default behavior that can suspend individual USB ports.⁵

If your EC2 reads 500 Hz consistently despite following the polling-rate change procedure, power management may be reinitialising the USB port. Disabling selective suspend can be a troubleshooting option, but Microsoft's driver guidance says selective suspend is enabled by default and strongly recommends not disabling it, so weigh stability and battery tradeoffs before changing it.

Keeping setup variables constant while comparing rates

Keep the port, cable bend, and surface constant while comparing polling-rate settings. The EC2 has no software profile to blame, so small setup changes can otherwise look like mouse behavior. A repeatable chart from the same USB path gives you a cleaner basis for deciding whether the issue is rate selection, power management, or contact wear. Changing the polling rate requires unplugging and reconnecting with a different button combination, so using the same USB port for every rate test ensures the only variable is the rate itself; swapping ports between tests introduces a second variable that can make a rate difference look like a port quality difference.

Documenting each run helps you separate a real rate problem from a setup artifact because the EC2 offers no software profile to absorb the blame. Write down the USB port, the button combination held at plug-in, and the Hz reading before moving to click latency. A short record like that, kept alongside this EC2 driverless run record's Hz chart, turns a confusing session into a repeatable procedure, so the next time the chart disagrees with your intent you can retrace the exact steps instead of guessing which variable shifted.

ENDGAME GEAR OP1 8K v2 Input Lag Test

The OP1 8K v2 gives you sub-50 g weight and field-replaceable switches in a wired esports mouse. ENDGAME GEAR's model pairs a PixArt PAW3950 sensor with Kailh GX hot-swap sockets, letting you replace the primary switches without soldering. At 49.5 g and supporting up to 8000 Hz over USB-A, it targets players who want complete control over both hardware performance and switch feel without the wireless dependency of flagship mice.¹ ENDGAME GEAR lists 8000 Hz as the default polling rate, with 4000, 2000, and 1000 Hz options available.²

The default Kailh GX optical switches provide zero-debounce registration. Use this tool to verify 8000 Hz reporting and measure click latency.

Specifications¹

Six polling steps up to 8000 Hz

The OP1 8K v2 supports 125, 500, 1000, 2000, 4000, and 8000 Hz over USB-A, with 8000 Hz listed as the default setting.² At 8000 Hz, position reports arrive every 0.125 ms. The wired-only design means polling rate depends entirely on USB port quality; no wireless radio scheduling introduces additional latency. For this browser test, connect to a rear motherboard USB-A port. Your Hz chart should read near 8000 on Chrome, Edge, or Firefox when the browser exposes coalesced pointer events; a ceiling at 1000 Hz despite selecting 8000 Hz in ENDGAME GEAR software indicates OS USB power management is coalescing events.³ Disable USB selective suspend to resolve power-management delays.⁴

Diagnosing a polling rate ceiling at 1000 Hz

If the chart reads at 1000 Hz despite selecting 8000 Hz in ENDGAME GEAR software, the fix follows a standard sequence. First, verify the polling rate was applied and saved in the software rather than just selected without applying. Second, move to a direct rear motherboard USB-A port. Third, disable USB selective suspend in Windows Device Manager. After each step, reconnect the mouse and rerun the test; improvement after a specific step identifies which constraint was holding your reading at 1000 Hz.

Kailh GX optical and mechanical switches

Kailh GX optical switches use a light-beam design with no mechanical contacts.⁵ The default GX switches register actuation without debounce delay. Building on this, the hot-swap sockets accept alternative Kailh GX variants; GX mechanical switches are available for players who prefer a different click feel at the cost of reintroducing a debounce window. Swapping to mechanical GX switches will increase click latency from the sub-2 ms optical range to approximately 3 to 8 ms. The switch type installed when you run the test determines which range your measurements fall in.

Swapping to Kailh GX mechanical switches to assess the feel difference is one of the practical advantages of the OP1 8K v2's hot-swap design. After installing mechanical switches for evaluation, run the click latency log to measure the latency increase relative to the optical baseline. Typical increases run from sub-2 ms with optical switches to 4 to 8 ms with GX mechanical switches at the default debounce setting, giving you a concrete latency cost to weigh against the preferred click feel before choosing a permanent switch configuration.

Measuring optical and mechanical baselines separately

Run the optical baseline first, then swap switches only after recording the average, spread, and any double-event count. That sequence keeps the comparison fair because the USB port, surface, and background load stay constant while the switch type changes. If the mechanical baseline is slower but stable, the result is a real debounce tradeoff rather than a setup change. Documenting both baselines in the same session with the same click technique isolates the switch variable completely; without that controlled sequence, a difference in grip or background load between sessions could make a mechanical switch look worse than it actually is.

Hot-swap socket checks before testing

Before testing, confirm the switch sockets are fully seated; a partially inserted switch in a hot-swap socket can cause intermittent contact that produces erratic button events in the log. Connect to a rear USB-A port and confirm polling rate in ENDGAME GEAR software. Your Hz chart should read near 8000 with low variance. If you see occasional double-click events with optical GX switches installed, try removing and firmly reinserting the switch to eliminate socket contact as a variable before adjusting debounce settings.

Hot-swap socket reliability affects this test more than it affects general mouse use. A switch that seats well enough for gaming may produce intermittent contact events when pressed off-center or at low force, which the click latency log captures as occasional double entries. Removing the suspect switch, inspecting the socket pins for bent contacts, and reinserting the switch with firm pressure until fully seated resolves most log anomalies on this model. If double events persist after reseating, testing a second switch rules out the individual switch as the cause.

Seating checks before changing switch type

A partially seated optical switch can look like a debounce problem, so inspect the socket before swapping to mechanical switches. If the socket pins look straight and the switch sits flush, then a controlled optical-to-mechanical comparison becomes much more meaningful. On the OP1 8K v2, the hot-swap sockets accept both 3-pin mechanical and 5-pin optical switches, so verifying that the switch type matches the socket pin count prevents a poor seating that produces intermittent contact. Run a quick 10-click test after each reseating to confirm the log shows clean single entries before proceeding to the full baseline measurement.

Rotating the mouse a quarter turn between reseating checks exposes socket pins that only fail under a particular hand angle. A switch that reads clean when pressed straight down may still double-fire when your grip presses it at the off-axis angle you use in game. Including that rotated press in a 10-click run through this OP1 8K socket seating test catches seating problems that a straight-down test would miss and keeps your baseline honest.

Razer Viper V4 Pro Input Lag Test

Designed for competitive wireless play, the Viper V4 Pro pairs an ultra-light body with HyperSpeed Wireless Gen-2 and Razer Optical Mouse Switches Gen-4. RTINGS lists the mouse at 48.9 g and describes its low click and sensor latency suitable for competitive gaming.¹ Use this tool to verify your polling rate and measure click latency from button press to browser event during matches.

Specifications²

8000 Hz and HyperSpeed motion latency

At 8000 Hz, the Viper V4 Pro reports position every 0.125 ms, compared with 1 ms at 1000 Hz. Razer's HyperSpeed Wireless Gen-2 technology page lists the Viper V4 Pro at 8000 Hz and 0.36 ms average motion latency.³ For the Hz chart to reflect the full rate, set 8000 Hz in Synapse, use the HyperSpeed dongle, and test in a browser that exposes PointerEvent.getCoalescedEvents(); MDN says browsers may coalesce pointer updates into a single event, which reduces tracking granularity.⁴

What a correctly configured 8000 Hz reading looks like

If the chart reads near 1000 Hz, the mouse is probably not reporting at the intended polling rate or the browser is receiving coalesced events instead of the high-frequency samples. Use a direct rear USB-A port for the dongle, recheck the Synapse setting, and compare movement readings before switching to click-latency measurements. Persistent low readings are a setup or OS-input-pipeline issue first; they do not automatically mean the mouse hardware is faulty.

Gen-4 optical switches and click latency

Razer describes the Viper V4 Pro's gen-4 optical switches as using optical actuation with no debounce delay and a 100-million-click lifecycle.² Razer's HyperSpeed page lists about 0.204 ms average click latency for the Viper V4 Pro at 8000 Hz, but your browser measurement includes OS scheduling, USB reporting, and how far the button travels before the optical beam is interrupted.³

Reading click-latency variance

For this mouse, look for repeated spikes rather than expecting hardware latency to match Razer's lab figure exactly. A tight cluster means the test conditions are stable; isolated spikes usually point to background scheduling or USB contention rather than a switch problem. At 8000 Hz, the USB report interval is short enough that most click latency variation comes from OS scheduling jitter and the physical consistency of your press technique rather than from the polling cycle itself. Comparing the per-click spread at 1000 Hz versus 8000 Hz on the same mouse and same USB path shows how much of the variance is polling-related versus system-related.

Polling and click readings from one setup

Use the HyperSpeed dongle for testing; Razer positions 8000 Hz around HyperSpeed Wireless Gen-2 rather than Bluetooth. Place the dongle in a direct USB-A port, keep the mouse powered on, and run the test after confirming 8000 Hz in Synapse. If the Hz chart remains near 1000 Hz after a port change and Synapse recheck, Windows USB power management may be involved; Microsoft documents selective suspend as default behavior and recommends not disabling it, so treat that change as a tradeoff rather than a guaranteed fix.⁵

Closing Synapse before a baseline run removes it as a background variable. Compare a Synapse-closed run with a Synapse-active run on your own machine if you want to see whether background software changes your chart. If the Synapse-closed run shows a noticeably higher Hz reading or a tighter click-latency spread, the Razer software was consuming USB or CPU cycles that affected the measurement, and you can decide whether to keep it closed during competitive sessions or accept the overhead for the convenience of on-the-fly DPI and profile switching.

For high polling rate mice, the most useful comparison is sustained behavior rather than a single peak. Run at least 15 seconds of steady movement and watch whether the line stays near 8000 Hz with only small jitter. A chart that repeatedly falls back to 1000 Hz is telling you about the active input path, not about the mouse capability on paper.

Wireless placement matters at 8000 Hz because the browser sees the final event path, not only the mouse specification. Keep the dongle away from metal obstructions, avoid moving it between runs, and compare only after the chart has time to settle. This makes a failed high-rate test easier to diagnose.

Comparing polling and click readings from the same setup

After the polling sample, keep the same dongle position and background state for click latency. Changing the USB path between measurements can make a clean switch reading look inconsistent. If click latency spikes appear only during the Synapse-active run, close unnecessary background processes and retest before changing mouse settings. Running both measurements in the same session with identical dongle placement isolates the switch behavior from environmental variables; if the Hz chart holds near 8000 Hz but click latency still shows tall spikes, the cause is more likely press technique or OS scheduling than the wireless link itself.

Treat the polling chart and click log in this Viper V4 wireless path baseline as two views of the same input path rather than separate checks. When both stay stable across repeated sessions with the dongle in one position, you have a trustworthy baseline for judging the mouse. When one drifts while the other holds, the change is almost always a setup variable such as port, background process, or dongle placement, so reset those before assuming the switch or receiver has failed.

SteelSeries Rival 600 Input Lag Test

With adjustable weight and a dual-sensor tracking system, the Rival 600 focuses on aim stability rather than ultra-light ergonomics. It uses mechanical TrueMove3 switches rated for 60 million clicks, so debounce behavior matters more than on optical-switch mice.¹ Use this tool to measure click latency and verify button response.

Specifications¹

1000 Hz with onboard profile storage

The Rival 600 operates at 1000 Hz over USB-A with no wireless option.² Its onboard profile saves polling rate settings when SteelSeries Engine exits.³ Both the primary TrueMove3 sensor and the depth sensor share the same USB connection, but the depth sensor generates minimal traffic and does not affect polling rate in this test. At 1000 Hz, each position report arrives every 1 ms. Plugging into a dedicated rear motherboard port removes the most common source of polling inconsistency on this model; front-panel headers and USB hubs share bandwidth with other devices and often produce scheduling jitter that appears as variance in the Hz chart.

For most setups, the primary TrueMove3 sensor dominates USB bandwidth and determines the Hz reading you see in this test. The depth sensor generates a lower-frequency tracking signal for lift detection and does not contribute polling events that compete with primary sensor reports. Connecting to a dedicated rear USB-A port ensures both sensor streams share a direct path to the host controller, eliminating hub-contention interference that can otherwise appear as variance in the chart even when only one sensor actively reports at 1000 Hz.

Mechanical switches and wear in the click log

The Rival 600 uses standard mechanical switches rated at 60 million clicks. Mechanical contacts introduce a brief bounce period when they close; firmware filters secondary contact events for a fixed window, typically 5 to 8 ms on this mouse.⁴ This debounce window produces consistent but slightly higher click latency than optical-switch mice. In this test, expect click latency between 3 and 8 ms.⁵ Keep debounce settings conservative on older switches because tightening the window can expose contact wear as accidental double-click events.

A fresh Rival 600 at the default setting typically produces click latency in the 5 to 8 ms range, which reflects the standard mechanical debounce window rather than any hardware fault. Reducing the debounce window can bring the average lower, though on switches with cumulative wear this risks producing occasional double events during rapid clicking sequences.

Reading wear from the click log

Watch for the pattern as much as the average. A new or healthy switch usually keeps values clustered around the debounce window, with most clicks landing within a narrow 2 to 3 ms band. A worn switch may show a normal average but occasional paired events from one press, where two rapid consecutive log entries appear after a single physical click. If those pairs appear more often across successive test sessions, increase debounce one step in SteelSeries GG and retest before deciding whether the switch needs replacement; the goal is to catch the wear trend early while a small adjustment still resolves it.

Reading the log across several sessions matters more than a single snapshot because contact bounce degrades gradually rather than all at once. If the same switch shows a slowly rising share of paired events across repeated 30-click checks, that upward trend is the clearest signal the debounce window is no longer masking worn contacts. Acting on the trend early lets you raise the debounce setting by a single step and keep the Rival 600 usable instead of waiting until double-clicks become constant.

Slow click checks for early double-clicking

Before testing, confirm your USB port is a direct motherboard connection rather than a hub or front-panel header. The Rival 600's dual-sensor design does not affect browser measurements; the depth sensor only influences lift-off tracking, which this tool does not measure. The most commonly reported reliability issue is double-clicking on aged primary buttons. Mechanical contacts develop surface oxidation over time that the debounce filter cannot suppress. If the test log shows consistent double events per physical press, increase the debounce window in SteelSeries GG before concluding the switch needs replacement.

A slow 30 click check is more useful than rapid clicking for this diagnosis

Press deliberately, release fully, and note whether each physical press produces one event or two. Rapid clicking can blur the difference between true contact bounce, normal firmware filtering, and accidental extra presses, making it harder to distinguish a genuine switch problem from normal high-speed behavior. A controlled 30-click sequence at roughly one click per second gives the firmware time to register each press independently, so any double entries in the log clearly indicate contact bounce rather than overlapping intentional clicks. Counting the total number of log entries after 30 deliberate presses gives you a concrete ratio to track over time.

Detecting early double-click failure before it becomes consistent

Because bounce amplitude increases gradually rather than suddenly, early-stage double-click failure on the Rival 600 produces intermittent rather than consistent double events. The click latency log makes this pattern visible: a series of normal single-click entries interrupted by the occasional pair of rapid consecutive events from one press. Seeing this pattern once or twice per 30 clicks in this Rival 600 double-click wear signs indicates developing contact wear rather than a firmware issue; increasing the debounce window in SteelSeries GG by one step suppresses the intermittent bounce and extends the switch's usable life before replacement becomes necessary.

Corsair M65 RGB Ultra Input Lag Test

An aluminium chassis and adjustable weight system make the M65 RGB Ultra a stable FPS-aim mouse rather than an ultra-light ergonomic pick. It uses Corsair Quickstrike optical switches with zero gap between the primary buttons and their optical switches.¹ Use this tool to measure click latency and check all button responses.

Specifications¹

Onboard polling settings and iCUE

By default, the M65 RGB Ultra connects via USB-A and supports selectable polling rates including 1000 Hz.² Polling rate changes require Corsair iCUE, but the mouse stores the selected rate in onboard memory and applies it without Corsair iCUE running after the change. At 1000 Hz, click and movement events arrive at 1 ms intervals. The aluminium chassis and adjustable weight system change physical feel but have no effect on USB timing. Your Hz chart should read close to 1000 on any rear motherboard USB-A port.

Onboard polling settings after iCUE closes

Onboard memory is useful when you want iCUE closed during testing. Set the polling rate once, disconnect and reconnect the mouse, then run the same movement sample again. If the Hz chart stays close to 1000 after the software exits, the mouse is applying the profile correctly and the browser test is measuring the configured hardware path rather than a software-driven exception.

If your reading sits below 1000 Hz despite using a rear USB-A port, check USB selective suspend and other Windows USB power-management settings before assuming a mouse fault.³ The M65 stores its polling rate in onboard memory and applies it immediately on connection, making a low reading after confirming 1000 Hz in iCUE a system configuration problem rather than a mouse issue. Open Device Manager, expand USB Root Hub under Universal Serial Bus Controllers, open Properties, select Power Management, and uncheck the option that allows the computer to turn off the device to save power before retesting.

Quickstrike optical switches

Corsair Quickstrike is an optical switch design. The button lever pre-tensions so the optical beam fires at the first point of physical contact rather than at the bottom of travel, and the primary buttons sit with zero gap above their optical switches.⁴ Eliminating pre-travel reduces the gap between finger intention and register event. The absence of mechanical contacts also means the Quickstrike switch should not develop the contact-bounce double-click failure common on aged mechanical switches.⁵ Consequently, click latency in this test typically sits between 1 and 3 ms, lower than standard mechanical mice and comparable to other optical designs.⁶

Running the test without iCUE open reveals the baseline latency the switch hardware produces without software scheduling overhead. Comparing with iCUE running using 20 clicks per state can show whether your software configuration contributes meaningfully to total click latency on your system. If the iCUE-closed average is consistently lower, the difference quantifies how much the Corsair software layer adds to your specific Windows installation, which is useful information when deciding whether to keep iCUE running during competitive play or to close it and accept the tradeoff of losing real-time DPI-shift and macro functionality.

Testing without iCUE and the sniper button

Connect the M65 to a rear USB-A port and run the test without iCUE open to see the baseline switch and USB path. Your Hz reading should stay near 1000 with minimal variance. If you see unexpected double events, verify your iCUE button assignment configuration before interpreting the test output as a hardware issue.

Sniper button behavior in the browser event log

The sniper button on the M65 uses a DPI-shift firmware mechanism that does not send a standard mouse button event to the browser.⁴ Pressing the sniper button changes DPI in onboard memory while held and releases the change on release. The click latency log does not show a sniper button entry; you may observe the movement Hz chart shift briefly as the DPI change alters how sensor displacement scales, but the log entry count stays unchanged. All five primary and side buttons that do generate mouse events appear in the log correctly and can be verified in sequence.

Why the sniper button behaves differently in the log

The sniper button is still useful, but it changes DPI rather than emitting a standard browser mouse button event. Pressing the sniper button shifts the sensor to a lower DPI profile while held, which can cause the Hz chart to briefly fluctuate as the cursor scaling changes mid-movement. Treat it as a DPI-shift control and verify the primary, right, middle, and side buttons separately in the click latency log of this M65 sniper button event gap. This prevents a false hardware diagnosis when one button intentionally operates outside the browser event model, and it also explains why the movement chart may show a brief anomaly when the sniper button is pressed during a polling rate test.

Glorious Model O Input Lag Test

The Model O became a lightweight wired choice for players who wanted a simple honeycomb-shell mouse at 67 g. It uses Omron mechanical switches rated for 20 million clicks and connects over USB 2.0 with a default 1000 Hz polling rate.¹ Use this tool to measure click latency and verify button response for fast, consistent competitive play.

Specifications¹

1000 Hz and the Ascended Cord

Polling via USB at 1000 Hz, the Model O delivers one position update every 1 ms.² At that rate, position reports arrive every 1 ms. The Ascended Cord flexible cable is designed to minimise drag during movement, but cable type does not affect the Hz reading. A damaged or kinked cable can introduce electrical noise that appears as dropout events on the chart; vertical red lines indicate polling gaps above 8 ms. If you see frequent dropouts, inspect the cable for visible kinks and try a different USB port before attributing them to the mouse hardware.

Cable routing and its effect on dropout markers

Dropout markers indicate polling gaps above 8 ms and appear as red vertical lines on the chart. Cable drag on the Model O can trigger brief dropout patterns during rapid directional changes where cable tension peaks. Routing the Ascended Cord in a loose parabolic arc behind the mouse prevents tension buildup during movement and removes cable drag as a potential source of false dropout readings. If dropouts persist on a rear port with clean cable routing, USB hub contention or power management is the remaining cause to investigate.

Omron switches and adjustable debounce

Omron mechanical switches use physical contacts that can bounce briefly after actuation; firmware debounce filters those secondary transitions so one press registers cleanly.³⁴ The Model O Wired V1 debounce range is 4–16 ms with a 10 ms default, adjustable in the Model O Wired software rather than Glorious CORE.⁵

In this browser test, expect click latency around the debounce window, with variation from OS scheduling, USB polling jitter, and how far the button travels before the switch actuates.⁶ Contact pressure can become unstable near the switching point, which is why worn mechanical switches can start producing chatter or double events.

At the default debounce setting, most Model O units produce click latency between 4 and 7 ms in this test. Lowering debounce toward 4 ms can reduce the average, but only if the switch still settles cleanly; raise it again if the log shows repeated double events from a single physical press.

When a lower debounce setting is not an improvement

A lower average is only useful if the switch still reports one clean event per press. If the log gains occasional double entries after reducing debounce, the old setting was masking contact bounce that the shorter window can no longer filter. Step back to the previous value and compare the average, spread, and double-event count together before deciding what feels fastest. The right debounce setting is the one that produces the lowest average without introducing repeated double events; chasing the absolute lowest latency means nothing if the log shows two entries for every other click during rapid gameplay sequences.

Cable routing and retesting before replacing switches

Connect to a rear USB-A port and verify the cable is not kinked during the test; the Ascended Cord's flexibility is an asset for gaming but means you should route it cleanly for measurement. Move steadily inside the tracking zone; erratic bursts lower the average Hz reading and can mask the true polling behavior you are trying to observe. Double-clicking is the most reported issue on this model, particularly after extended use where the Omron switch contacts begin to degrade. If the log shows two button events per physical press, open the Model O Wired software and raise the debounce threshold before concluding the switch is worn, because a higher debounce value can suppress contact bounce that a shorter window lets through as duplicate events.

Retesting before deciding the switch is worn

Because the original Model O is not factory hot-swappable, switch replacement is a repair task rather than a quick settings change. If increasing debounce does not resolve repeated double events, use a service guide for disassembly and switch replacement or replace the mouse. The honeycomb shell panels must be removed first to access the internal PCB, and the soldered Omron switches require a desoldering pump or solder wick before new switches can be fitted, so the repair demands basic soldering tools and steady hands rather than just a screwdriver.

Document the exact software version and debounce setting when you retest. The Model O Wired software path differs from newer Glorious CORE workflows, so recording the setting prevents a confusing repeat session where the switch condition and configuration no longer match. Without a record from this Model O debounce setting log, you may inadvertently compare a test run at 4 ms debounce against one at 10 ms and draw the wrong conclusion about whether the switch itself has degraded or whether the software setting is simply filtering more aggressively.

Logitech G502 X Input Lag Test

The Logitech G502 X uses Logitech G's LIGHTFORCE hybrid optical-mechanical switches, which combine optical actuation speed with mechanical tactile feel.¹ Its main buttons register via optical sensing rather than mechanical contact, which reduces debounce delay compared with standard mechanical switches. Use this tool to measure click latency from button press to browser event.

Specifications²

1000 Hz in the default gaming profile

The G502 X connects via USB-A and reports at 1000 Hz, with a 1 ms report interval in the default gaming profile.³ Each position update arrives every 1 ms, which sets the theoretical floor for tracking latency between hardware and cursor. Wired 1000 Hz gives you the most direct path: no wireless radio stack, no scheduling overhead from a 2.4 GHz protocol, just USB delivering reports at the rate the mouse firmware generates them. Consequently, polling drops on this mouse point you toward USB path or Windows power-management variables before you assume mouse hardware failure. Plugging directly into a rear motherboard port, rather than a front-panel header or hub, removes extra devices from the same USB path and makes the test easier to interpret.

Polling drops and what they indicate on this mouse

Polling drops on the G502 X often point to USB path or Windows power-management variables rather than the mouse hardware. The wired-only design eliminates wireless radio scheduling as a variable, so the Hz chart reflects the USB path more directly. A reading that sits well below 1000 Hz on a mouse rated at 1000 Hz points to a hub, front-panel header, or power-management setting worth checking. Moving to a rear motherboard USB-A port and running the test again confirms whether port selection resolves the drop before you investigate other OS settings.

LIGHTFORCE switches on the G502 X

LIGHTFORCE is a hybrid design. The button uses a physical lever with an optical beam at the actuation point; actuation fires when the beam breaks rather than when contacts close.⁴ Removing contact bounce eliminates the debounce window mechanical switches require. Building on this, LIGHTFORCE registration should produce lower and more stable click latency than a standard mechanical switch in this browser test. Yet the lever still travels physically before the beam fires, so the tactile feel remains similar to a mechanical switch despite the faster registration.⁴

Comparing the G502 X click latency to a mechanical switch mouse shows the LIGHTFORCE advantage most clearly in the log. On a mechanical switch mouse, debounce filtering happens before the event fires; the LIGHTFORCE optical beam fires without waiting for contact bounce to settle. Most presses cluster tightly with low per-click variance. Occasional high-latency outliers reflect OS scheduling delays rather than switch behavior and can appear on all mice regardless of switch type.

Comparing a clean baseline with a noisy baseline

Run the test twice before drawing conclusions: first with companion software closed, then with your normal gaming setup active. If the average stays close but outliers increase, the switch is probably stable and the extra noise comes from background scheduling rather than a hardware fault. A clean baseline run with no background applications gives you the lowest realistic average; a second run with your typical gaming overlay, chat client, and Discord active shows how much scheduling overhead your real setup adds. CapyToolkit keeps the measurement local, so you can compare both runs side by side without uploading logs or changing mouse hardware between sessions.

A direct-port baseline for the G502 X

Connect the G502 X to a rear USB-A port before running the test. Front-panel headers and USB hubs can add other devices to the same USB path, which makes polling jitter harder to interpret in the chart. Move the mouse steadily inside the tracking zone for a representative Hz reading. If you see repeated button events from a single press, check Logitech G HUB for firmware or profile changes before interpreting results as a hardware fault.

Interpreting a direct-port baseline

A direct motherboard port gives you the cleanest baseline for the G502 X. If the Hz chart stabilizes after you remove hubs, passthrough docks, or front-panel headers, the first test likely reflected USB path noise rather than mouse performance. Keep that clean setup for later comparisons so click latency and polling readings stay easier to explain.

Before committing to any firmware update interpretation, verify that the G502 X is connected directly rather than through a USB passthrough port if you use a charging dock or hub. Passthrough connections add one USB hop, which can introduce another power-management or scheduling variable. Windows USB selective suspend can suspend individual USB ports or devices to save power, so disabling that setting is a reasonable check when a wired mouse repeatedly reconnects or reads below its configured rate.⁵ Running the test from the passthrough port versus a direct rear motherboard port, using the same G502 X passthrough port latency embedded on this page, shows whether that hop produces a measurable difference on your setup before drawing conclusions about firmware performance.