How to Test for and Fix WiFi Packet Loss: Tools, Causes, and Step-by-Step Fixes for Dropped Packets on Home Networks

Packet loss means data packets sent from your device never arrive at their destination — or never make it back. Even 1–2% loss is enough to cause stuttering video calls, rubber-banding in online games, and dropped VoIP calls. Unlike a slow connection, packet loss is invisible to a standard speed test, which measures throughput rather than reliability. You need different tools. This guide covers how to test for packet loss, pinpoint exactly where it is occurring, and fix it at every layer of your home network.

What Packet Loss Feels Like vs. Slow Speed

Slow download speed and packet loss produce different symptoms. Slow speed means files take longer to download and pages load gradually — but they load. Packet loss manifests as frozen frames during video calls, lag spikes in games even on fast connections, choppy audio, and web pages that partially load then stall. Real-time protocols like gaming (UDP), video conferencing (RTP), and VoIP are particularly sensitive because they cannot retransmit lost packets without breaking the timing of the stream.

If your speed test shows 300 Mbps but your Zoom calls still break up, packet loss — not bandwidth — is the likely culprit.

How to Test for Packet Loss

Method 1: The Ping Command

Ping is built into every operating system and is the fastest way to check for packet loss between your device and a target server. Open a terminal (Command Prompt on Windows, Terminal on macOS or Linux) and run:

• Windows: ping -n 100 8.8.8.8
• macOS / Linux: ping -c 100 8.8.8.8

This sends 100 packets to Google’s DNS server and reports how many returned. A result of 0% packet loss is ideal. Anything above 1% indicates a problem worth investigating. The time= values show round-trip latency; a high average combined with packet loss points to congestion rather than a broken link.

Method 2: PingPlotter (Find Exactly Where Loss Occurs)

Ping only tells you whether loss exists between your device and a single destination. PingPlotter traces every router hop along the path and shows loss at each node. Download PingPlotter Free (Windows and macOS) from pingplotter.com. Enter 8.8.8.8 as the target and run it for at least 5–10 minutes. Each row in the graph represents one hop — typically your router (hop 1), your modem or ISP handoff (hop 2–3), and progressively farther backbone routers beyond.

How to read the results: Loss only at hop 1 means the problem is between your device and your router — almost always a WiFi radio issue. Loss appearing first at hop 2 or 3 points to the modem or ISP handoff. Loss that first appears at hop 5 or later is an ISP backbone routing problem. Loss only on intermediate hops but not the final destination is usually those routers deprioritizing ICMP — not a real problem.

Method 3: MTR / WinMTR

MTR combines ping and traceroute into a live, continuously-updating view. On Linux and macOS, run mtr --report-cycles 100 8.8.8.8 from the terminal. On Windows, download WinMTR (free, open source). MTR shows per-hop packet loss and average latency simultaneously over a sustained run, making it ideal for catching intermittent loss that a single short ping session might miss. Run it for at least 5 minutes — problems that appear only under load or every few minutes require time to surface.

Common Causes of WiFi Packet Loss

WiFi Interference and Weak Signal

RF interference is the most common cause of wireless packet loss on home networks. When your WiFi radio retransmits frames due to interference, the 802.11 retransmission mechanism absorbs the loss silently — until congestion is severe enough that buffers overflow and frames are actually dropped at the MAC layer. Common interference sources include microwave ovens (2.4 GHz), baby monitors, neighboring networks on overlapping channels, and Bluetooth devices sharing the same radio.

Check your WiFi signal strength at the affected device. A reading below −75 dBm on 5 GHz or below −70 dBm on 2.4 GHz is weak enough to cause regular retransmissions that eventually produce measurable packet loss. Our guide on WiFi signal strength in dBm explains how to read these values on any device.

Channel Congestion in Dense Environments

In apartments and dense neighborhoods, dozens of networks competing on the same channel create airtime contention. Even with a strong signal, MAC-layer collisions cause packets to be queued and dropped when transmit buffers fill under load. On 2.4 GHz, only channels 1, 6, and 11 are non-overlapping — our 2.4 GHz channel overlap guide covers how to pick the least-congested option. On 5 GHz or 6 GHz, use a WiFi analyzer app to identify an open channel before changing settings.

Bufferbloat and Router Overload

Bufferbloat is a condition where your router’s transmit queue fills with download data, forcing latency-sensitive packets to wait behind megabytes of bulk traffic — or be dropped when buffers overflow. Symptoms: packet loss and lag spikes that are worst when another device on the network is downloading a large file. The DSLReports Speed Test includes a bufferbloat grade (A through F) that confirms this quickly. The fix is enabling Smart Queue Management (SQM) or FQ-CoDel on your router if supported — TP-Link, ASUS, and OpenWrt-based routers all offer this under their QoS settings.

Faulty Hardware

A damaged Ethernet cable, failing modem, or overheating router can all introduce packet loss at the physical layer. A Cat5e or Cat6 cable with a damaged pair may pass a basic LED continuity test but drop packets under load at Gigabit speeds. If loss appears on a wired connection, swap the cable first — it is the cheapest test available. Overheating routers thermally throttle their CPU, causing packet processing delays and drops. Our guide on fixing an overheating router covers the symptoms and ventilation fixes.

ISP-Side Problems

DOCSIS cable internet is susceptible to packet loss from degraded coaxial connections, poorly-spliced amplifiers, and node congestion during peak hours. If PingPlotter shows loss starting at hop 2 or 3 (the first ISP device past your modem), the problem is outside your home. Run the test at different times — peak evening (7–10 PM) vs. early morning (5–7 AM) — to check whether loss correlates with network load, which indicates ISP node congestion rather than a hardware fault. Consistent loss at all hours points to a line quality issue worth reporting.

Step-by-Step Fixes

Step 1: Isolate WiFi vs. Wired

Plug your device directly into the router with an Ethernet cable and rerun the ping test. If packet loss disappears on a wired connection, the problem is in your WiFi radio path. If loss persists on a wired connection, the problem is in the router, modem, or ISP. This single test divides every possible cause into two groups and tells you which fixes to pursue first.

Step 2: Change WiFi Band and Channel

If the problem is WiFi-specific, log in to your router’s admin panel and move the affected device to the 5 GHz or 6 GHz band. These bands offer more non-overlapping channels and are immune to 2.4 GHz household interference sources. On 5 GHz, channels 36–48 (UNII-1) avoid DFS radar-detection delays. On 2.4 GHz, confirm which of channels 1, 6, and 11 has the fewest competing networks using a free WiFi analyzer app such as WiFi Analyzer (Android) or WiFi Explorer (macOS).

Step 3: Improve Router Placement or Add a Wired Access Point

If signal is weak at the problem location, moving the router centrally or adding a wired access point in the affected area eliminates the physical-layer cause of packet loss. Mesh systems are the consumer-friendly option; a wired access point via Ethernet or MoCA backhaul over coax is the highest-reliability alternative. Our mesh node placement guide covers optimal positioning for multi-AP setups.

Step 4: Reboot the Router and Update Firmware

Routers accumulate memory fragmentation and stale routing entries over weeks of uptime. A clean reboot resolves many intermittent packet loss cases immediately. After rebooting, check the router admin panel for a firmware update — manufacturers regularly release wireless driver fixes that address known packet-drop bugs.

Step 5: Contact Your ISP With Evidence

If PingPlotter clearly shows loss beginning at hop 2 or 3, save the graph as an image and call your ISP. Ask specifically for a “line quality check” and request that a technician review upstream power level and SNR on your modem. For cable internet, degraded coaxial connections — a bad splitter, a corroded F-connector, or a failing tap — are invisible to you but visible on the ISP’s modem diagnostic page. Providing timestamped PingPlotter evidence of hop-2 loss significantly shortens the support call and reduces the chance of an unnecessary truck roll.