Last updated:
If a call or game responds slowly on WiFi but works better over Ethernet, measure where the extra delay begins. The wireless link, a busy upload, mesh backhaul or the internet path can each contribute. A faster advertised WiFi rate does not by itself guarantee lower latency.
Run a fair comparison
- Use the same computer, app and internet connection for the tests.
- Pause large downloads/uploads and note the device’s location and connected band.
- Test WiFi near the main router, then at the problem location.
- Repeat over Ethernet with the same workload where possible.
- Repeat while the network is busy, since idle and loaded latency can differ substantially.
Separate local delay from internet delay
Find the actual default gateway in your network details. On Windows, a short sample to the router is:
ping -n 30 192.168.1.1Replace the address with your gateway. On Linux or macOS, the comparable count option is ping -c 30. Microsoft documents the Windows ping options. Record loss and the spread of responses, not just the lowest number.
Then compare an external endpoint that responds to ping, and the actual app’s connection statistics if available. Some endpoints or routers block or deprioritize ICMP, so a poor ping response alone does not prove that normal application traffic is failing.
Interpret the pattern
| Observed pattern | Likely area to investigate |
|---|---|
| Router delay worsens only on WiFi | Signal, interference, retries, airtime or wireless backhaul |
| Router stays responsive; external delay rises on both connections | WAN congestion, routing or the destination |
| Delay spikes during uploads | Saturated queues and available traffic-management features |
| Only one device behaves badly | Adapter driver, power-saving settings or that device’s load |
Try the simple corrections first
- Move the router/node away from obstructions and test a closer position.
- Check channel congestion and use supported automatic selection or a sensible channel plan.
- Try an appropriate band: 5/6GHz can avoid some congestion but has different coverage and compatibility limits.
- Update the router and adapter through their official support channels.
- Reduce competing transfers or evaluate supported queue-management settings after confirming a loaded-network problem.
Very wide channels are not automatically best in a crowded environment. Change one setting at a time and repeat the same test so you know which change helped.
Check the mesh and the specific service
A weak wireless connection between nodes can add delay even when the phone is close to its nearest node. Our Ethernet-backhaul guide explains a supported wired alternative. It cannot guarantee zero loss or delay on the remaining wireless link.
If the issue is reaching a printer or another PC rather than slow internet, check client and guest isolation. For a game or call that remains poor over Ethernet, collect the app’s own statistics and investigate the external path before buying a new router.