Latency Test

What This Controller Latency Test Measures

"Input lag," "input delay," and "latency" all describe the same thing from different angles: the time between you pressing a button on your gamepad and the game (or browser, in this case) actually registering that press. This tester measures that interval in real time, in milliseconds, by polling your controller as fast as your browser allows and timing how long each press takes to surface in the input stream. The result is a real, comparable number rather than a vague feeling that something is sluggish.

The tester runs entirely in your browser using the Gamepad API. Nothing is sent to a server, no driver is installed, and the controller never leaves your machine. Plug in via USB or pair over Bluetooth, press any button to wake the page, then start mashing — every press is timestamped and the running statistics update live.

The Latency Scale: What's "Good"?

Raw millisecond numbers mean nothing without context. Most gaming forums throw around figures like "8 ms is great, 30 ms is awful" without explaining where the line really sits. Here's a calibrated scale based on actual measurements from common setups:

A wired Xbox or DualSense controller on a modern PC usually lands in the 4–10 ms range. Bluetooth typically adds 8–20 ms on top of that depending on the radio. PlayStation Portal and other cloud-streaming devices commonly land at 35–80 ms total because there's a network round-trip baked in. If your number is far above what your setup implies, something's wrong and the rest of this guide narrows it down.

Reading Min, Avg, Max — And Why Jitter Matters Most

The tester reports four numbers for a reason. They tell you different things about the same controller, and the one most people ignore (jitter) is usually the most telling.

Where Your Input Lag Actually Comes From

People talk about "controller input lag" as if it's one thing. It isn't. Every button press passes through five stages on its way to becoming a pixel changing color on your screen — and each stage adds time. Knowing the breakdown tells you where to look first.

The browser-based test on this page can only see the first three stages directly — controller polling, transport, and OS/driver. The game engine and display stages happen entirely outside the browser. That's actually useful: if your test result is low but the game still feels laggy, you've isolated the problem to the game's render pipeline or your monitor, not your controller.

The Diagnostic Flow: Where's Your Lag?

If your test result is higher than the scale above predicts, run through this flow in order. Each step rules out one possible cause, and the first three together resolve roughly 90% of "my controller feels laggy" reports.

Wired vs Bluetooth vs Cloud: What to Expect

Connection type is the single biggest factor for the latency you can ever achieve. Here's the realistic range for each on healthy hardware, before any optimization:

How to Fix High Controller Input Lag

If your number is sitting in the "Noticeable" zone, work through these in the order they appear. Each one targets a different layer of the stack, and the first three are free.

Switch from Bluetooth to USB

The single biggest single-step improvement available. Every controller mentioned in this guide has a USB-C or micro-USB port. Plug it in, wait for the OS to switch over (you may need to disable Bluetooth temporarily to force it), and re-test. Expect to lose 10–20 ms instantly.

Update or roll back your controller driver

On PC: open Device Manager → expand "Human Interface Devices" or "Xbox Peripherals" → right-click your controller → Update Driver. If updating doesn't help, roll back — in some cases the newest Microsoft driver has higher latency than the previous version.

Close background apps that hook input

RGB control software (iCue, Synapse, GHub), screen recorders (OBS, ShadowPlay), and overlay tools (Discord overlay, Steam in-game overlay) all attach to the input pipeline. Quit them entirely — not minimize — and re-test.

On Xbox: enable wired connection priority

Xbox Series consoles will use wireless even when a controller is connected via USB-C unless you explicitly tell them not to. In Settings → Devices & connections → Accessories, select your controller and check the connection mode. Confirm the cable is a known-good data cable, not charge-only.

On PS5: turn off "Communicate Features" you don't use

Settings → Accessories → Controllers → the DualSense's haptics and adaptive triggers consume extra bandwidth on Bluetooth. Disabling features you don't actively want frees that bandwidth back to input polling, which can shave 4–8 ms off Bluetooth latency on busy radios.

On PC: prefer Xbox Wireless Adapter over Bluetooth

Microsoft's official Xbox Wireless Adapter (a small USB dongle) talks to Xbox controllers directly using the same proprietary protocol the consoles use, bypassing Bluetooth entirely. The latency difference vs Bluetooth is usually 8–15 ms in favor of the adapter.

Why "Latency" and "Polling Rate" Aren't the Same Thing

This trips up a lot of buyers reading controller spec sheets. Polling rate is how often the controller reports its current state — 250 Hz means once every 4 milliseconds, 1000 Hz means once every 1 millisecond. Latency is the full end-to-end time from press to register, which includes polling but also adds transport delay, OS scheduling, and any debouncing the controller firmware does.

A controller that polls at 1000 Hz can still have 15 ms of latency if its Bluetooth transport is slow. A controller that polls at 250 Hz can hit 5 ms of latency over USB. Polling rate is a ceiling on how fast the controller could respond — latency is how fast it actually does. To measure the polling rate side of the equation specifically, our dedicated Polling Rate Check isolates that number.

Once you've nailed down your input latency, the other free checks on the same controller are worth a quick pass too. The Joystick Test rules out stick drift that can feel like aim lag, the Gamepad Tester confirms every button and trigger registers correctly, and the Vibration Check verifies your rumble motors are healthy.

Display Lag: The Hidden Multiplier

One of the most common confusions in latency discussions is blaming the controller for what's actually a screen issue. Display lag — how long your monitor or TV takes to draw a pixel after receiving the signal — is invisible to controller tests but very much part of the felt latency. The numbers vary wildly: a competitive gaming monitor in fast mode might add 4 ms, a mid-tier 4K TV might add 30 ms, and a budget TV in standard picture mode can add 80–120 ms on top of everything else.

How to identify a display-lag problem

If your browser latency test reports clean numbers (say, 6–12 ms) but games still feel sluggish, the bottleneck is almost certainly downstream of the controller. The classic signature is delay that gets worse on a 4K TV but disappears on a PC monitor with the same controller. The fix is in your display's picture settings, not the gamepad.

The "Game Mode" fix that actually works

Virtually every modern TV has a setting called Game Mode (sometimes labelled PC Mode or Low Latency Mode). It disables the post-processing the TV normally applies — motion smoothing, noise reduction, edge enhancement — that collectively add 30–80 ms of processing lag. Turning it on for the HDMI input your console is plugged into typically cuts display lag by half or more. If the option isn't obvious, search "[your TV model] game mode" — manufacturers hide it in different sub-menus.

Variable refresh and the hidden cost of V-Sync

On PC, V-Sync trades input lag for visual smoothness — classic implementations can add a full frame or two of latency, which at 60 Hz is 16–33 ms on top of everything else. Modern alternatives like NVIDIA Reflex, AMD Anti-Lag, and FreeSync/G-Sync with V-Sync disabled give you most of the smoothness with a fraction of the latency cost. If your in-game settings menu offers these, switch to them.

Common Input-Lag Myths Worth Ignoring

Latency is a topic with more folklore than facts. A few persistent myths are worth setting straight before they cost you money or time.

"Wireless controllers can't compete with wired"

True for cheap Bluetooth setups, false for modern proprietary 2.4 GHz wireless. The Xbox Wireless Adapter and high-end gaming peripheral protocols like Logitech Lightspeed regularly match or beat USB latency in independent tests. The "wireless is always worse" rule is two console generations out of date.

"Higher polling rate always feels better"

Up to a point. Going from 125 Hz to 250 Hz is clearly perceptible. From 500 Hz to 1000 Hz is debatable in blind tests. Above 1000 Hz the gains are real but smaller than the marketing suggests — and any controller hitting 4000 Hz is almost certainly trading battery life or driver stability for the headline number.

"Latency is just about the controller"

The full chain — controller, transport, OS, game engine, display — routinely adds up to 50–100 ms before you've even talked about network play. The controller is one stage among five. Optimizing only the controller can leave 80% of your felt lag untouched.

"You can't feel single-digit-millisecond differences"

The truth is more nuanced. Most people genuinely can't distinguish 8 ms vs 12 ms in isolation. But a difference between 8 ms (consistent) and 8–30 ms (jittery) is felt by almost everyone, because the brain calibrates to the average and reacts badly to the spikes. This is why jitter matters more than the headline number.

Hardware vs Software Latency: Where to Spend Your Money

If your goal is competitive responsiveness rather than just diagnosing a problem, it's worth knowing which upgrades actually shave milliseconds and which are placebo. Not all latency improvements cost the same, and the curve is sharply diminishing — the first 10 ms of improvement is cheap; the last 5 ms gets expensive fast.

The free wins (do these first)

Switching from Bluetooth to wired USB, closing background overlay apps, plugging directly into a motherboard port instead of a hub, and enabling Game Mode on your display together remove 20–50 ms of latency for zero cost. If you haven't done all four, the most expensive controller in the world won't help you.

The cheap wins (under $30)

A known-good braided USB-C data cable (some "charging" cables can't sustain high data rates), a wired Ethernet connection for your console replacing Wi-Fi, and a Microsoft Xbox Wireless Adapter for PC each cost under $30 and each shave 5–15 ms in real testing. These are the highest-return upgrades after the free ones.

The expensive wins (the diminishing returns zone)

A 240 Hz monitor with sub-5 ms response time replacing a 60 Hz TV typically removes 15–30 ms of display latency — significant, but you're paying $300+ for it. A premium pro controller with Hall-effect sticks and 1000 Hz polling might shave 4–8 ms over a stock controller, costing $150–200. These are real improvements, just at much higher cost per millisecond removed.

What's mostly hype

"Gaming-grade" USB cables marketed for low latency add nothing measurable over a known-good standard cable. Most software "latency optimizers" do less than turning off RGB software. And on Bluetooth specifically, no firmware setting can match the latency floor of a wired connection — if Bluetooth is your bottleneck, the only real fix is to stop using Bluetooth for that controller.

Frequently Asked Questions