Controller Latency Test: Millisecond Input Lag and Jitter Analyzer

How to Measure Millisecond Input Delay Step by Step

1. Set Your Monitor to Its Highest Refresh Rate and Close Heavy Tabs: Because web browsers synchronize requestAnimationFrame polling with your display refresh cycle, verify in your OS Display Settings that your gaming monitor is running at its maximum native refresh rate (such as 120Hz, 144Hz, or 240Hz) and close background video tabs.
2. Connect Your Gamepad via USB Cable, 2.4GHz Dongle, or Bluetooth: Plug your device in or pair it via Bluetooth, then press any face button to wake the browser Gamepad API and initialize the timestamp delta buffer.
3. Rotate Both Analog Thumbsticks Continuously for 5 Full Seconds: Operating systems only increment gamepad.timestamp when an input value changes. Rotate both the Left Stick and Right Stick in smooth, continuous circles for five seconds to force your gamepad to transmit a fresh packet on every single polling cycle.
4. Read Your Millisecond Interval (ms) and Polling Rate (Hz): Inspect the Polling Rate and Latency readout box in the top telemetry strip (for example, 250 Hz / 4.00 ms or 125 Hz / 8.00 ms) while maintaining continuous stick rotation.
5. Compare Wired USB vs Wireless Bluetooth on the Same Device: Click Copy Diagnostic Report to record your wired USB millisecond interval, then unplug the cable, pair the same unit over Bluetooth, click Reset Data, and repeat the 5-second rotation to measure wireless overhead and jitter.

How to Interpret Your Millisecond Interval Readings

Every video frame on a 60Hz monitor lasts 16.67 milliseconds, every frame on a 120Hz monitor lasts 8.33 milliseconds, and every frame on a 240Hz monitor lasts 4.17 milliseconds. Your update interval (ms = 1000 / Hz) determines whether your button press lands in the immediate next frame. Compare your measured score from the controller latency test against this hardware benchmark table.

What a Browser Controller Latency Test Measures (and How Timestamp Deltas Work)

To understand what a browser controller latency test measures, it helps to distinguish between two components of total input lag: End-to-End Hardware Latency (the physical time from a switch closing to a USB packet arriving, which requires an external hardware oscilloscope wired to your PCB) and Host Update Interval and Jitter Latency (the millisecond spacing between consecutive HID state updates received by your operating system and browser).

Our online controller latency test measures Host Update Interval and Jitter with high precision using the W3C Gamepad.timestamp property. Whenever your USB or Bluetooth driver delivers a new state report containing changed axis or button values, the browser records a high-resolution monotonic timestamp (DOMHighResTimeStamp, accurate to thousandths of a millisecond). As you rotate your thumbsticks continuously, our engine collects a rolling window of 90 consecutive timestamp deltas (Delta_t = Timestamp_n - Timestamp_n-1), filters out stationary frames, and computes the average millisecond interval and effective Hertz rate.

Why is timing stability (low jitter) just as important as raw speed? Suppose Pad A updates at a rock-solid 8.00 ms every single cycle over a USB cable, while Pad B over a noisy Bluetooth link averages 5.00 ms but periodically spikes to 22.00 ms when wireless packets collide and retransmit. Even though Pad B has a lower mathematical average, those sudden 22.00 ms spikes cause your crosshair to lurch unpredictably during fast tracking.

• High-Resolution Delta Sampling: Measures millisecond intervals across 90 rolling hardware packets.
• Transport Mode Inference: Automatically identifies whether your update interval matches standard USB/HID, Bluetooth, or high-speed 2.4GHz/overclocked polling.
• Zero-Install Browser Execution: Benchmark wired versus wireless delay on Windows, macOS, Linux, Android, and iOS in seconds.

The Role of Monitor Refresh Rate (60Hz vs 120Hz vs 240Hz) in Browser Testing

When running any web-based controller latency test, you must account for how modern browser engines schedule JavaScript execution. For security and power efficiency, Chrome, Edge, Firefox, and Safari update the state snapshot returned by navigator.getGamepads() in step with the display's vertical blanking interval via window.requestAnimationFrame.

What does this mean for your millisecond reading? If you run this check on a standard 60Hz laptop or office monitor, the browser checks the gamepad buffer once every 16.67 milliseconds, so even a 1000Hz pad will display roughly 60 Hz (16.67 ms) unless multiple sub-frame timestamps are exposed. When you run the exact same controller latency test on a 120Hz monitor (8.33 ms frame time), 144Hz monitor (6.94 ms), 240Hz monitor (4.17 ms), or 360Hz monitor (2.78 ms), the browser samples the hardware buffer two to six times faster, revealing your device's true 125 Hz (8.00 ms), 250 Hz (4.00 ms), or 500 Hz+ polling cadence.

Per-Controller Latency Architecture: PS5, PS4, Xbox, Switch, and 8BitDo

Every major console manufacturer programs a specific USB endpoint polling descriptor (bInterval) and Bluetooth report schedule into its firmware. Compare your results from our controller latency test against these published hardware specifications:

Sony PS5 DualSense (VID 054C, PID 0CE6) and DualSense Edge (PID 0DF2): Over a stock wired USB-C connection on PC, the standard PS5 DualSense sets its USB bInterval to 4 milliseconds, resulting in a 250 Hz update rate (4.00 ms interval). The pro-grade DualSense Edge sets its native wired USB descriptor to 1 millisecond, polling at 1000 Hz (1.00 ms interval) right out of the box. Over a clean Bluetooth 5.0+ connection on PC, Sony pads can transmit reports at 400 Hz to 800 Hz (1.25 ms to 2.50 ms), though Bluetooth is far more susceptible to radio jitter than wired USB.

Sony PS4 DualShock 4 V1 and V2 (VID 054C, PID 05C4 and 09CC): Like the standard DualSense, the DualShock 4 polls at 250 Hz (4.00 ms) over wired Micro-USB by default, and up to 500 Hz to 800 Hz over clean Bluetooth.

Microsoft Xbox Series X and S, Elite Series 2, and Xbox One (VID 045E): Microsoft prioritizes rock-solid deterministic timing across console and PC. Over both wired USB-C and the official Microsoft Xbox Wireless Adapter for Windows (which uses Microsoft's proprietary 2.4GHz/5GHz GIP protocol), Xbox Series X and S and Xbox One models lock their report interval to 8.00 milliseconds (125 Hz). Over standard Bluetooth on PC or mobile, Xbox units typically report every 8.00 ms to 15.00 ms depending on the host Bluetooth stack.

Nintendo Switch Pro Controller and Joy-Cons (VID 057E): Over Bluetooth on PC and mobile, Switch units typically operate at a 60 Hz to 125 Hz cadence (8.00 ms to 16.67 ms). Over wired USB-C on Windows without custom drivers, the Switch Pro Controller defaults to 60 Hz to 125 Hz.

8BitDo, Gamesir, Gulikit, and Flydigi Third-Party Pads: Many modern third-party models include a dedicated 2.4GHz USB dongle and wired USB mode engineered for 250 Hz, 500 Hz, or 1000 Hz (1.00 ms to 4.00 ms) polling.

Wired USB vs 2.4GHz Dongle vs Bluetooth: Which Has the Lowest Input Lag?

Using our controller latency test to benchmark your own desk setup often uncovers important differences between wired and wireless connections:

1. Wired USB-C / Micro-USB: Delivers zero radio packet retries, zero battery voltage sag, and virtually zero interval jitter. On PlayStation and third-party pads that support 250 Hz to 1000 Hz USB polling, wired USB is the top choice for competitive consistency.

2. Dedicated 2.4GHz Proprietary USB Dongles (Xbox Wireless Adapter, 8BitDo 2.4GHz Dock): Unlike general-purpose Bluetooth, a dedicated 2.4GHz dongle runs a lightweight gaming protocol tuned for fixed time slots. It matches wired USB delay within a fraction of a millisecond while providing wireless freedom.

3. Standard Bluetooth: While Sony DualSense and DualShock 4 units can achieve fast raw report rates over Bluetooth when sitting 30 centimeters from a high-gain PCIe Wi-Fi/Bluetooth antenna, Bluetooth shares the crowded 2.4GHz ISM radio band with Wi-Fi routers, wireless mice, keyboards, and microwave ovens. Even minor radio interference forces Bluetooth Link Layer packet retransmissions, which show up on our telemetry bar as sudden millisecond spikes.

Common Causes of High Input Latency and Jitter on PC and Mobile

If this test shows your update interval jumping above 16 ms or fluctuating erratically, check these four hardware bottlenecks:

First, USB 3.0 Radio Interference on Bluetooth Dongles: Intel and USB-IF engineering whitepapers document that active USB 3.0 Type-A ports and cables emit broadband radio noise across the 2.4GHz to 2.5GHz spectrum. If you plug a tiny nano Bluetooth USB adapter directly into a blue USB 3.0 port on the back of your PC motherboard right next to an external hard drive or mouse receiver, the noise floor degrades Bluetooth range and causes latency spikes.

Second, Unpowered USB Hubs and Daisy-Chained Monitor Ports: Plugging a high-speed gamepad into an unpowered 4-port splitter shared with a USB headset or webcam can introduce bus scheduling delays.

Third, Background Remapper and Overlay Loops: Running multiple input wrappers simultaneously (for example, DS4Windows feeding into Steam Input while Nvidia GeForce Experience and Discord overlays hook the window) adds extra user-space thread hops.

Fourth, Power-Saving Bluetooth Coexistence Modes on Laptops: Many Windows laptops share a single M.2 combo card for both 2.4GHz Wi-Fi and Bluetooth. Downloading or streaming over 2.4GHz Wi-Fi while gaming on a Bluetooth pad forces the combo card to time-slice its single antenna, doubling your input delay.

Step-by-Step Fixes to Reduce Gamepad Input Latency

Follow these proven engineering steps to lower your millisecond score and eliminate jitter on this test:

1. Move Bluetooth Dongles Onto a Short USB 2.0 Extension Cable: If you use a USB Bluetooth adapter on a desktop PC, plug it into a 1-meter shielded USB 2.0 extension cradle placed on top of your desk in direct line-of-sight to your hands, at least 50 centimeters away from rear USB 3.0 ports.

2. Switch Your PC or Phone Wi-Fi from 2.4GHz to 5GHz or 6GHz (or Ethernet): Moving network traffic off the 2.4GHz band clears the radio spectrum for your Bluetooth or 2.4GHz gamepad.

3. Plug Wired Gamepads Directly Into Rear Motherboard Ports: Connect your USB-C cable directly to a rear I/O motherboard port tied to the CPU or primary chipset controller.

4. Optional USB Polling Rate Overclock (For PlayStation and DirectInput Pads on Windows): Advanced competitive players using wired PS5 DualSense or PS4 DualShock 4 pads on Windows often use the signed open-source HIDUSBF filter driver to lower the USB host bInterval from 4 ms (250 Hz) down to 1 ms (1000 Hz).

When to Replace Cables, Dongles, or Hardware for Latency Faults

Timing issues rarely require replacing the entire gamepad. If your device shows erratic disconnects over wired USB when you move your hands, the internal wires inside your USB-C cable are fatigued or the USB port on the chassis has loosened; replacing the cable with a braided USB-IF certified data cable solves it for under $10. If Bluetooth timing remains unstable even with fresh batteries, replacing a legacy Bluetooth 4.0 nano dongle with a Bluetooth 5.3 adapter equipped with an external high-gain antenna (or switching to a wired connection) restores deterministic performance.

Browser and OS Troubleshooting for Latency Measurements

If the Polling Rate and Latency box stays at 0 Hz (0.0 ms) during this test, remember that stationary thumbsticks do not generate timestamp deltas. You must keep rotating one or both analog thumbsticks continuously for at least three to five seconds so the sampler receives a nonstop sequence of changed coordinates. Additionally, ensure that browser hardware acceleration (Use graphics acceleration when available in Chrome or Edge settings) is enabled so requestAnimationFrame runs at your monitor's full 120Hz, 144Hz, or 240Hz refresh rate rather than throttling to 30fps or 60fps.