How to Run a Speed Test in Terminal and Understand the Results

If you want a quick way to check network performance, running a speed test in terminal is often the fastest option. It can show download speed, upload speed, and latency without opening a browser, and it is useful when you want to compare Wi-Fi, Ethernet, or different ISP paths under similar conditions.

What the terminal speed test is showing

A terminal speed test measures how your device exchanges data with a nearby test server. The main numbers are download speed, upload speed, and latency. Some tools also report jitter or packet loss. A low result does not always mean your ISP is failing; it can also reflect local Wi-Fi quality, router load, or a server choice that is farther away than expected.

Common reasons the result looks lower than expected

Wi-Fi signal quality

Weak signal, channel congestion, and interference from walls or neighboring networks can reduce throughput. This is one of the most common reasons a laptop tests well in one room and poorly in another. If the result improves on Ethernet, the wireless link is likely the main constraint.

Router or modem bottlenecks

An aging router, overloaded modem, or outdated firmware can limit performance before traffic even reaches your ISP. If every device on the network shows the same slowdown, the local network gear is a strong suspect. Reboots may help temporarily, but repeated issues usually point to hardware or configuration limits.

Background traffic on the device or network

Cloud backups, OS updates, game downloads, and streaming devices can consume bandwidth while the test runs. That makes the result look unstable or artificially low. A clean test should run when other traffic is paused and the device is not pushing large uploads in the background.

Server distance and routing

Speed tests depend on the selected server and the route between your network and that destination. A server that is geographically close can still produce poor results if the path is congested or inefficient. This is why one terminal test may look fine while another run minutes later appears worse.

How to judge whether the number is real

Run the test more than once and compare the trend, not a single reading. Repeat it on Wi-Fi and on Ethernet if possible. If the wired test is much better, focus on the local wireless setup. If both are low, check whether the problem appears only at peak hours, which can point to ISP congestion or neighborhood contention on cable broadband or shared infrastructure.

• Test at different times of day to see whether peak-hour congestion changes the result.
• Compare multiple servers if your tool allows it.
• Run the test from more than one device to isolate whether the issue is device-specific.
• Watch for unusually high latency or jitter, which often affects calls and gaming more than raw download speed.

Which terminal tools to use

Many users start with speedtest-cli or the official speedtest tool from Ookla. On Linux, package managers often provide one of these. On macOS, Homebrew is common. The practical difference is usually server selection, reporting detail, and how easy it is to automate repeated checks. For a basic health check, either tool is enough if it returns consistent download, upload, and latency data.

What to change when the results are poor

Start with the lowest-cost fixes. Move closer to the router, switch to 5 GHz or 6 GHz Wi-Fi if supported, and test again. If the signal is unstable, use Ethernet for the device that needs the most reliable connection. Update router firmware, replace worn cables, and restart the modem if the connection has not been refreshed in a long time. If the problem persists across devices and times of day, contact your ISP and provide the repeated terminal results along with timestamps.

When you speak with support, describe the pattern: whether the drop affects download, upload, or both, whether latency rises under load, and whether the issue happens on Wi-Fi, Ethernet, or both. That makes the conversation more useful than sharing a single slow result.

A practical troubleshooting order

1. Run the terminal speed test twice on the same connection.
2. Repeat the test on Ethernet if available.
3. Pause backups, updates, and streaming on every active device.
4. Try a different test server or tool.
5. Check router placement, firmware, and cabling.
6. Escalate to the ISP only after local causes are ruled out.

Used this way, a terminal speed test is not just a number generator. It is a fast diagnostic tool that helps separate Wi-Fi issues, router limits, device load, and ISP-related problems so you can fix the right layer first.