Ethernet vs Wi-Fi for your desk setup: where a cable still wins
Direct answer: for a fixed desk, cable the machines that sit there and leave everything portable on Wi-Fi. Not because Wi-Fi is slow — its headline speeds are fine — but because the desk is the one place in the house where a cable costs nothing in convenience and buys the one thing Wi-Fi cannot guarantee: latency that stays put. The decision is per-device, not per-house. This guide runs the two side by side, then walks the desk device by device.
The numbers: latency is the argument
Gemwell's Ethernet explainer puts LAN latency at about 0.3–1 ms for a wired connection against 2–10 ms for Wi-Fi. TRTech's comparison makes the sharper point: latency, not headline speed, is the real Ethernet win, because Wi-Fi latency can spike past 50 ms under congestion — the busy-evening moment when everyone in the house is streaming and your call is the thing that stutters. Averages flatter Wi-Fi; spikes are what a desk worker actually feels.
| Gigabit Ethernet | Wi-Fi | |
|---|---|---|
| Typical LAN latency | 0.3–1 ms | 2–10 ms |
| Latency under congestion | Holds near its typical range | Can spike past 50 ms |
| Real throughput | ~940 Mbps TCP on a gigabit link | Shared airtime; falls as more devices talk |
| Duplex | Full-duplex: sends and receives at once | Half-duplex: one direction at a time on shared airtime |
Latency and duplex figures: Gemwell's Ethernet explainer. Congestion spikes: TRTech. Read the throughput row carefully — a gigabit cable's ~940 Mbps is delivered to one machine, while Wi-Fi's capacity is a pool every nearby device draws from, one speaker at a time. At a desk, where the machine does not move for eight hours, giving up that pool for a private lane is nearly all upside.
Device by device: who earns a cable
The docked laptop or desktop — cable it. This is the machine that carries your calls, your uploads, and your working day. It sits within a cable's reach of where a cable can live permanently, so it collects the full latency win at zero daily cost.
A NAS or regular large file transfers — cable it. TRTech names local transfers as the other case where wired clearly wins. Moving big files between a desk machine and network storage uses the full-duplex lane in both directions, instead of taking turns on shared airtime against the rest of the household.
Calls and gaming at the desk — cable the machine. These are the uses that feel a 50 ms spike rather than a slower average. The win is not a faster headline speed; it is the spike going away.
The printer and the smart speaker — leave them. Nothing in the numbers above argues for cabling them. Their traffic is small and indifferent to latency, and a cable buys them nothing while adding one more run to manage. A decision framework that cables everything has stopped being a framework.
The laptop problem: the port may not exist
The desk decision is easy; the connection point is the fiddly part. Work through it as a short procedure:
- Check the machine for an Ethernet port. Desktops and older laptops usually have one. If yours does, the run is a single cable from the router — or from a small desk switch, if several wired devices share the desk — straight to the machine.
- If there is no port, route through the dock. A laptop that already sits on a USB-C dock for its monitor and keyboard takes its network connection through that dock or a USB-to-Ethernet adapter: one cable into the dock, and the laptop is wired every time it is docked, with nothing extra to plug in.
- Run one cable to the desk, not one per device. Where a desktop, a docked laptop, and a NAS share a desk, a small switch at the desk turns a single run from the router into a port for each of them.
- Confirm the machine is actually using the wire. With the cable connected, check the connection details in your system settings and confirm the active connection is the wired one, then run the task that used to stutter — a call, a large transfer — on it.
What success looks like: the desk machine shows a wired connection whenever it is at the desk, calls hold steady through the household's busy evening instead of stuttering when others stream, and large transfers to local storage run at a steady rate rather than rising and falling with the house's wireless traffic. If the machine quietly falls back to Wi-Fi when docked, the dock connection — not the idea — is what needs fixing.
The hybrid desk: wired core, wireless edges
The verdict, keyed to your desk. Cable it if the machine is fixed, latency-sensitive, or moving large files locally: the docked laptop, the desktop, the NAS. Leave it wireless if it moves, trickles, or cannot feel a spike: the phone, the tablet, the printer, the speaker. Whole-home rewiring is a different and much larger project; nothing here needs it. One run to one desk captures most of what Ethernet still wins — the spike-free call, the private full-duplex lane — and leaves Wi-Fi doing what it is genuinely good at: everything that was never sitting still anyway.
— Dex Carter, Tech Writer