Packet loss can make a game stutter, a video call freeze, or a file transfer crawl. When latency climbs and FPS drops, the cause is not always the app itself. Often, the problem starts somewhere between your device and the network path it uses.

This checklist walks through practical steps to diagnose network troubleshooting packet loss latency fps issues on Wi-Fi and Ethernet – How to fix packet loss for competitive gaming: a. It starts with simple checks, then moves into router settings, routing tests, and validation steps you can repeat after each change.

1. Confirm the problem before changing anything

Start by proving that packet loss is actually happening. Run a few tests at different times of day, because congestion can change by the hour. Use the same device, the same server, and the same connection type so your results stay consistent.

Try a basic ping test to your router first, then to a public host such as 1.1.1.1 or 8.8.8.8. On Windows, open Command Prompt and run ping -n 50 192.168.1.1 for your router, then ping -n 50 1.1.1.1. On macOS or Linux, use ping -c 50 with the same targets.

If you see loss only to the internet host but not to the router, the issue is likely outside your home network. If loss appears even when pinging the router, focus on Wi-Fi, Ethernet, cables, drivers, or the router itself.

2. Separate Wi-Fi problems from Ethernet problems

The fastest way to narrow the cause is to compare Wi-Fi and Ethernet on the same device. If packet loss disappears on Ethernet, the wireless link is the main suspect. If both connections show the same behavior, the issue may be upstream, in the modem, router, or ISP path.

For Wi-Fi, test in the same room as the router and again from your usual location. Walls, microwave ovens, baby monitors, and crowded apartment channels can all affect signal quality. In many homes, the 5 GHz band performs better for low latency, while 2.4 GHz may reach farther but suffers more interference.

For Ethernet, check the cable type and condition. A damaged Cat5e or Cat6 cable can create intermittent errors, especially if it is bent sharply or pressed under furniture. Replace any cable that feels loose at the connectors or has visible wear.

3. Check the router and modem first

Power-cycle the modem and router separately, not just together. Unplug both devices, wait 30 seconds, then power on the modem first and the router second. This helps clear temporary faults and forces a fresh connection to your ISP.

Look at the router status page for signs of trouble. Repeated disconnects, high interface errors, or a weak WAN signal can explain packet loss. If your modem shows DOCSIS or optical signal warnings, that points to a line issue that may need ISP support.

Also review firmware updates. Router firmware fixes sometimes improve stability, Wi-Fi performance, or compatibility with certain devices. Before updating, note your current settings so you can restore them if needed.

4 (more on this topic). Reduce Wi-Fi interference and congestion

When packet loss only appears on Wi-Fi, channel congestion is a common cause. In a dense area, many routers compete on the same channel, which raises retransmissions and latency. Use a Wi-Fi analyzer app to see which channels are crowded, then switch to a cleaner one.

Place the router in an open, central spot, not inside a cabinet or behind a TV. Elevation helps too. A router on a desk or shelf usually performs better than one on the floor, especially for 5 GHz coverage.

If your router supports separate SSIDs for 2.4 GHz and 5 GHz, test both bands. Some devices roam poorly between bands, which can create brief drops. For gaming or video calls, staying on a stable 5 GHz connection often improves latency and lowers packet loss.

Wi-Fi settings worth checking

Review these options in the router admin panel:

• Channel width – wider is not always better; 80 MHz can be fast but less stable in crowded areas.
• Transmit power – higher power can help coverage, but it does not fix interference.
• Band steering – useful for some homes, but it can cause roaming issues on older devices.
• QoS – prioritize gaming or voice traffic if your router supports it.

5. Inspect Ethernet for hidden faults

Ethernet should be the most stable option, but physical issues still happen. A loose port, a failing switch, or a bad patch cable can create packet loss that looks like an internet problem. Swap one item at a time so you know exactly what changed.

Check link speed on the device. If a port that should run at 1 Gbps negotiates at 100 Mbps, the cable or connector may be faulty. That mismatch can also raise latency under load, especially when multiple devices are active.

If possible, connect the device directly to the router with a short known-good cable. Remove powerline adapters, docking stations, and extra switches during testing. Each extra device adds another possible failure point.

6. Run routing tests to locate the loss

Ping tests show whether loss exists, but traceroute-style tools show where the path starts to degrade. On Windows, use tracert or pathping. On macOS and Linux, use traceroute or mtr if available.

Start with the router, then test a stable internet target, and finally test the service you actually use, such as a game server or work VPN endpoint. Compare hop-by-hop results. If loss begins at the first hop after your router, the issue may be your ISP handoff – in our article about Packet loss fix for competitive FPS. If it only appears farther out, it may be route congestion or a remote server problem.

Be careful interpreting traceroute. Some routers deprioritize ICMP responses, so a single high-latency hop does not always mean real packet loss. Look for a pattern across multiple hops and repeat the test several times.

7. Check device settings, drivers, and background traffic

Outdated network drivers can cause drops, especially on laptops and gaming PCs that switch between power states. Update the Wi-Fi or Ethernet adapter driver from the hardware vendor or your system manufacturer. After updating, reboot and retest the same route.

Also look at background traffic. Cloud sync, game downloads, OS updates, and smart home cameras can saturate upload bandwidth. When upload fills up, latency rises quickly and packet loss can appear even on a fast connection.

Pause heavy transfers and test again. If performance improves, enable scheduling for updates or use router QoS to keep real-time traffic ahead of bulk downloads. This is one of the simplest ways to improve network troubleshooting packet loss latency fps results without changing hardware.

8. Validate the fix with repeatable tests

After each change, rerun the same tests you used at the start. That means the same host, the same packet count, and the same connection type. If you changed Wi-Fi settings, test both near the router and from your normal seat.

For gaming, use an in-game network graph if available. Look for stable ping, low jitter, and no packet loss during movement and combat. A connection can feel fine in a simple ping test but still drop packets under real game traffic.

For work calls, watch for voice clipping, delayed screen sharing, or frozen video. For file transfers, compare transfer speed before and after the fix. A clean result should hold under load, not just during idle testing.

9. Know when to call the ISP or replace hardware

If packet loss remains on both Wi-Fi and Ethernet after you have checked cables, drivers, router settings, and local interference, the next step is likely your ISP. Provide them with timestamps, ping results, and traceroute output. Clear evidence shortens the support call.

If the router is older, overheating, or failing to keep a stable WAN link, replacement may be the better option. Consumer routers can age into flaky behavior long before they stop working completely. Frequent reboots, random disconnects, and rising latency under normal load are all warning signs.

Use the checklist in order, and change one thing at a time. That approach makes it much easier to identify the real cause of packet loss, whether it shows up on Wi-Fi, Ethernet, or both.