Logitech G PRO X2 SUPERSTRIKE Input Lag Test

Test click latency and verify 8000 Hz polling on your Logitech G PRO X2 SUPERSTRIKE. Measure button response time in your browser. No download required.

ZERO UPLOAD · ALL LOCAL
  1. Connect your mouse to a direct motherboard USB port — avoid hubs for accurate readings.
  2. Click "Start Session" and move your mouse continuously inside the tracking zone.
  3. Leaving the tracking zone pauses the measurement; re-entering resumes it automatically.
  4. Read the live metrics: Current Hz, Avg Hz, Max Hz, and Longest Gap.
  5. Click "Stop" to end the session and view the final results card.
  6. Red vertical lines indicate polling dropouts (below 125 Hz) — frequent red lines suggest USB contention or power management issues.

Expected result for Logitech G PRO X2 SUPERSTRIKE

Polling Rate for this mouse typically reads 7200–8400 Hz (rated 8000 Hz).

Run the test below to see your result.

Move your mouse continuously inside the tracking zone to measure your mouse's polling rate. The tool calculates Hz from the time between each PointerEvent, then displays a live rolling chart of stability over time.

Works with any USB or wireless mouse. For best results, use a direct USB port — no hubs. A 1000 Hz mouse should read 900–1050 Hz; a 4000 Hz mouse should read 3600–4200 Hz.

Move your mouse continuously inside this area
Leaving this area will pause the measurement

Current Hz
Avg Hz
Max Hz
Longest Gap

Session Results

Avg Hz
Max Hz
Longest Gap
Samples

Red lines = polling dropout (<125 Hz). Move mouse continuously for an accurate reading.

Logitech G PRO X2 SUPERSTRIKE Input Lag Test: Click Latency Check

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.1 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.

Specifications2

SensorLogitech HERO 2 25K
Max DPI44 000
Primary switchLogitech H.I.T.S. haptic inductive
Weight60 g
Polling rateUp to 8000 Hz (LIGHTSPEED wireless)
Battery life90 hours (constant motion, wireless)

Polling rate and connectivity

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.3 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.

Switch technology and click latency

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.4 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.1 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.

Testing this mouse

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. 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.

Sources
  1. 1.

    Logitech G, "PRO X2 SUPERSTRIKE Wireless Gaming Mouse | Logitech G," logitechg.com, accessed June 2026. https://www.logitechg.com/en-nz/products/gaming-mice/pro-x2-superstrike-mouse.html

  2. 2.

    Logitech, "Specification - PRO X2 SUPERSTRIKE," support.logi.com, accessed June 2026. https://support.logi.com/hc/en-us/articles/35026563405591-Specification-PRO-X2-SUPERSTRIKE

  3. 3.

    Mozilla Developer Network, "PointerEvent: getCoalescedEvents() method," developer.mozilla.org, accessed June 2026. https://developer.mozilla.org/en-US/docs/Web/API/PointerEvent/getCoalescedEvents

  4. 4.

    Logitech G, "G HUB HITS: Advanced Haptic Click Technology | Logitech G," logitechg.com, accessed June 2026. https://www.logitechg.com/en-us/software/guides/ghub-hits

FAQ