Controller Input Latency
Input latency is the total time from pressing a button to seeing it on screen. Your controller is one link in that chain — here is where delay lives.
The latency chain
Input → report: the controller digitizes your press and transmits it (USB or wireless). Then the report → game: the engine may only read inputs once per frame. Then game → display: the render, scan-out and the panel's own response time. Your monitor often contributes more than your controller does.
Wireless controllers add a small, measurable transport delay compared to USB — usually a few milliseconds, and it varies with the wireless stack and interference, not with "gaming mode" marketing.
What you can actually control
Use a low-latency connection mode when it matters (wired or a low-latency wireless mode), keep the battery from draining (some controllers poll differently on low battery), and match refresh rate to frame rate. Most of the chain is the display, not the pad.
Measure your own feel
Our Latency Estimator measures reaction-and-input time with a browser timer. Be clear about what it measures: human reaction plus input pipeline feel, not lab-grade input latency. For a controller that drifts or reports unreliably, fix the sensor before chasing milliseconds.
Quick Answers
Is Bluetooth controller input lag bad?
Modern controllers over Bluetooth add roughly a few milliseconds of transport delay versus USB — measurable, but usually below perception for casual play. Competitive play on 240Hz+ setups favors wired for consistency, not dramatic gains.
How do I reduce controller input lag?
Order of impact: cap frame rate to a stable target (frame time dominates), use a low-latency display, then wire the controller. Fixing a drifting stick also "reduces" perceived lag — a stick fighting your inputs feels delayed.