Ethernet is often the cleanest troubleshooting baseline because it removes radio interference and shared wireless airtime from the test. Good Wi-Fi can still be fast and reliable. Compare the same device, destination, and workload before deciding which component needs an upgrade.
Check what the Ethernet link actually negotiated
A gigabit router does not guarantee a gigabit link to every client. Inspect the adapter's reported link speed, the switch port, and the cable. A damaged cable, limited dock, old switch, or port setting can leave a connection at 100 Mbit/s. The end-to-end transfer can then be limited even when the Internet plan is faster.
Use automatic negotiation unless the equipment documentation requires otherwise. Mismatched forced settings can introduce problems. For a comparison, swap one known-good cable or port and recheck the negotiated rate before altering advanced driver settings.
Separate Wi-Fi link rate from delivered throughput
A displayed Wi-Fi rate is a physical-link indicator, not a guaranteed application transfer rate. Wireless airtime is shared, and interference, retransmissions, channel width, distance, walls, and client capability affect results. A phone and laptop in the same room can perform differently because their radios and antenna arrangements differ.
A mesh node connected wirelessly also needs backhaul airtime. Excellent signal between the client and nearby node does not prove that the node's uplink is strong. Where supported, wired backhaul can remove that particular wireless constraint.
Run a fair A/B test
- Use the same computer and test destination for both runs.
- Temporarily stop competing transfers and note whether a VPN is active.
- Test Ethernet, then Wi-Fi near the main access point, then Wi-Fi at the problem location.
- Record throughput and latency under load, not just the fastest result.
If Ethernet reaches 400 Mbit/s and Wi-Fi at a distant room reaches 45 Mbit/s with spikes, focus on the wireless segment. If both remain near 90 Mbit/s and the wired link negotiated at 100 Mbit/s, investigate the wired path first. If both vary at the same busy time, inspect WAN demand and provider conditions.
Improve the limiting segment
Place an access point where coverage is needed, using appropriate power, channel planning, and backhaul. Hiding a router in a cabinet or adding repeaters to a weak path can create avoidable bottlenecks. Keep router firmware and adapter drivers supported and current.
For a stationary work PC, console, or media server, a cable may offer predictable latency. For mobile devices, a well-planned wireless network is the practical choice. Buy equipment after identifying the limit: a new high-end router cannot overcome a slow destination server or repair an ISP outage.
Put it into practice
References & further reading
Protocol standards and official documentation supporting this guide. Device menus and provider policies vary; use the documentation for your equipment when applying a change.