A speed test against a remote server mixes the wireless link, your router, your ISP, and the remote path. A transfer to a known wired device on your network can isolate several of those variables. Put the test server on Ethernet and keep it fixed while comparing clients.

sh
# On a trusted, wired machine on the LAN:
iperf3 -s

# On the client, replacing this address with the server's LAN IP:
iperf3 -c 192.168.1.20 -t 15
iperf3 -c 192.168.1.20 -t 15 -R

Compare the same path

Test a wired client first, then a wireless client from the spot where you noticed the slowdown. The reverse test sends traffic from the server to the client. Measuring both directions can reveal unequal performance caused by signal, interference, or device radios.

If wired throughput is also poor, check the link speed on both ends. A port negotiating at 100 Mbps often points toward a cable, connector, or link partner worth checking. Change one thing and repeat the same test.

If the LAN test is fast but a remote speed test is slow, repeat the remote test from the wired client. Look upstream when both clients show the same limit. Stop the local iperf server after the comparison.

References