Slow Wi-Fi? How to measure real speed and packet loss

Why traditional speed tests mislead on Wi-Fi networks

When home internet starts acting up, the automatic reflex is to open a browser and run a commercial speed test. In practice, this means you are testing the entire end-to-end path: your wireless router, the ISP modem, routing across the public internet, and the processing power of the testing website itself. To figure out whether the bottleneck lives in your wireless network card or inside the radio waves traveling through your house, you must isolate variables. If you have ever tried to understand why a wireless connection drops and loses packets in the Linux terminal, you know link-layer diagnostics help, but testing raw throughput requires a dedicated network engineering tool called iperf3.

Setting up the lab: the role of iperf3 on local networks

The iperf3 utility operates on a client-server model, requiring one machine to act as a reference while another initiates traffic streams. In practice, this means plugging one computer directly into your router via a Gigabit Ethernet cable to serve as the official test server. The other machine, which can be a laptop connected via Wi-Fi, takes on the client role to bombard the server with packets and measure actual transmission capacity. This approach bypasses internet service provider limits and focuses exclusively on the wireless infrastructure of your home or office. For those accustomed to monitoring Linux network traffic in real time with iftop, iperf3 complements the analysis by actively forcing maximum load onto the radio channel.

Installing the tool and launching the test server

Before measuring anything, we need to ensure the software is installed on both ends of the test environment. On Debian or Ubuntu-based Linux distributions, installation is straightforward through the standard system package manager. In practice, this means opening a terminal window and running a lightweight command that downloads all necessary dependencies without friction. Once installed on both the wired machine and the laptop, starting the server follows a direct workflow. Below are the basic commands to get the server up and running and start probing the network:

1. Open the terminal on the computer connected to the router via Ethernet and run the installation command:

   sudo apt update && sudo apt install iperf3 -y

2. Start the wired machine in server mode to listen for incoming wireless client connections:

   iperf3 -s

3. On the laptop connected to Wi-Fi, execute the client pointing to the IP address of the server to begin the upload test:

   iperf3 -c 192.168.1.50

Measuring real throughput in the upload direction

When triggering the client command against the local server, iperf3 injects a continuous stream of TCP packets for ten seconds. In practice, this means forcing your wireless network card to transmit as much data as the air can possibly handle at that exact moment. The final report displays the average bandwidth achieved, revealing whether your connection is pushing hundreds of megabits per second or stalling at low speeds due to interference. It is vital to observe whether the traffic remains steady or fluctuates wildly during the testing window. Sharp fluctuations typically indicate signal reflection off walls or heavy interference from neighboring networks operating on the same channel.

Evaluating the impact of reverse traffic on wireless adapters

We often measure how much data a computer can send to the network, but forget that receiving data is usually much heavier during everyday use. In practice, this means downloading large files or streaming high-resolution video requires the router to push data aggressively toward your laptop antenna. To simulate this scenario without swapping machines, we can use a parameter that reverses the packet flow direction during execution. The reverse test evaluates the receiving antenna and radio circuit capacity to handle a flood of incoming air data. If the download rate collapses while upload remains acceptable, it strongly points to channel congestion on reception or physical misalignment.

Identifying packet loss and latency under load on Wi-Fi

Raw throughput does not tell the whole story regarding wireless link quality for real-time gaming or video calls. In practice, this means a connection might look fast on average, yet suffer from micro-stutters caused by dropped packets in the air. To audit this behavior with surgical precision, we can switch the default test protocol to UDP, allowing us to specify a target bandwidth and monitor percentage loss. When packets begin disappearing in the air at rates higher than one percent, latency spikes and browsing acquires that annoying stuttering feel. Measuring latency under maximum load helps expose bufferbloat, which happens when router buffers fill up and delay packet delivery.

Final considerations on wireless network diagnostics

Systematic use of iperf3 transforms how we handle connectivity issues, shifting focus from guesswork to concrete empirical data. In practice, this means you stop blaming your internet service provider for flaws originating from poorly positioned routers or misconfigured wireless network cards. By mastering throughput measurements, reverse traffic behavior, and packet loss ratios, anyone gains the autonomy to optimize their own environment. If doubts persist regarding physical hardware integrity, it is worth reviewing complementary methods such as testing electronic components and hardware interfaces to rule out hardware failures once and for all.