Wired vs Wireless Peripherals, on Latency

On a dedicated 2.4 GHz link, the latency difference is around a millisecond and nobody perceives it. On Bluetooth, the difference is real. Those two facts get collapsed into one argument, which is why this discussion never ends.

A note on this comparison: this rests on how each link is designed and specified rather than on latency measured here. See how we test.

The short version

Wired. No battery, no interference, no pairing. The cable is the entire cost, and cable drag is a real ergonomic annoyance rather than a performance one.

Dedicated 2.4 GHz. A receiver that talks to one device on a link built for input. Within a millisecond or two of wired, sometimes indistinguishable, and occasionally better than a wired device running at a low polling rate.

Bluetooth. Built for power efficiency and coexistence, not for timing. Higher and less consistent input latency, and the reason "wireless feels laggy" survives as a belief.

What actually separates them

The claim was true, and then it stopped being true

Early wireless peripherals genuinely were slower, and enough people experienced that first-hand for it to become received wisdom.

Dedicated receivers have since closed the gap to the point where the remaining difference is smaller than the variation introduced by the display, the game engine and the polling rate. The belief outlived the hardware it was formed on, which is a normal thing for beliefs to do.

Polling rate is the bigger lever, and it is free

How often a device reports its position matters more than how the report travels.

A device left at a low polling rate gives up more than the entire wired-versus-wireless difference, and raising it costs nothing. Anyone worried enough about input latency to be reading this should check that first — and note that a slow USB port or hub can cap it regardless of the device, which is what the TESmart KVM review found on its USB 2.0 hub.

Interference presents as latency without being latency

A wireless device that stutters intermittently is usually not slow — it is dropping packets in a congested band.

The 2.4 GHz spectrum carries Wi-Fi as well, and a receiver plugged into the back of a metal case standing on the floor has both distance and shielding working against it. Moving the receiver onto the desk on a short extension fixes a large share of these complaints, and costs almost nothing.

If the Wi-Fi is also struggling, the two problems share a cause — fixing bad gaming Wi-Fi covers the band side of it.

The real cost of wireless is the battery

Not latency. A battery is a thing to charge, a thing that degrades over years, and a thing that runs out at an inconvenient moment.

That is a genuine trade and it is the one worth deciding on. Most wireless mice charge over the same cable they would have used wired, which makes the fallback painless.

The decision, plainly

• Competitive play, and you want the argument settled → wired or 2.4 GHz, either is fine
• You dislike cable drag → 2.4 GHz, and the latency question is closed
• Work, typing, general use → anything, including Bluetooth
• A device shared between a laptop and a phone → Bluetooth, and accept the input latency
• You have measured genuine input lag → none of these, the cause is elsewhere
• You have not checked your polling rate → do that first

This page contains affiliate links. If you buy through them, Ugly Fixes may earn a commission at no extra cost to you. Products are selected independently.

A receiver extension suits any 2.4 GHz device that stutters, and it is the first thing to try before concluding wireless was a mistake.

A mouse bungee suits someone whose objection to wired is drag rather than timing, which is most people who think they object to wired.

A replacement cable suits a wired keyboard where the cable is the annoyance, and detachable cables make that a small fix rather than a new keyboard.

A powered hub suits a desk short of ports, with the caveat that a slow hub can cap polling rate on anything behind it.

The mistake to avoid

Buying wired to fix a latency problem you have not measured. If a machine genuinely feels unresponsive, the cause is far more likely to be the display, the frame rate, a background process or a polling rate left at its default than the link between the mouse and the port — and switching to wired changes none of those.

The second mistake is treating Bluetooth and 2.4 GHz as one category because both are wireless. They are different technologies aimed at different goals, and almost every "wireless is laggy" experience worth taking seriously was Bluetooth.