By john 
While Windows does not include a full internet speed test, its command-line tools can measure components of your connection like latency and, with a download, throughput. These give useful indicators when a TANGKAS39 browser-based speed test is not convenient.
The Command
ping -n 20 google.comWhat It Does
Sending 20 pings with `-n 20` and reviewing the average round-trip time gives a measure of your connection’s latency, how quickly it responds. The summary at the end shows minimum, maximum, and average times. Lower and more consistent times indicate a responsive connection, while high or varying times suggest latency issues affecting responsiveness.
When You’d Use This
This is useful for a quick check of connection quality when a full browser-based speed test is inconvenient, or when you specifically want to measure latency and reliability rather than raw download speed. Gamers concerned about latency, or anyone diagnosing an unresponsive connection, benefit from seeing round-trip times and whether any packets are lost, which raw speed figures do not reveal.
Useful Variations
To gauge download throughput, downloading a known-size file with PowerShell’s `Measure-Command` around an `Invoke-WebRequest` times the transfer, from which speed can be estimated. To check for packet loss, a longer continuous ping with `-t` reveals whether any replies are dropped, which affects connection reliability beyond raw speed.
If It Doesn’t Work
If times are high or vary a lot, your connection has latency issues that could stem from congestion, Wi-Fi interference, or distance from the router, so testing on a wired connection helps isolate the cause. Remember these tools measure latency and reliability rather than sustained throughput, so for a true broadband speed figure, a dedicated browser-based speed test remains the right tool.
Good to Know
These tools measure latency and can estimate throughput but do not replace a dedicated speed test, which measures sustained download and upload rates against optimized servers. For a true broadband speed figure, a browser-based test remains the standard, while these commands are useful for quick latency and reliability checks.
Putting It Together
Once you have run it once or twice, this becomes second nature. As part of diagnosing and configuring your connection, this command belongs in your toolkit for whenever the network acts up. Used alongside the other networking commands here, it helps you methodically work from confirming basic connectivity to pinpointing exactly where a problem lies. Like anything in the terminal, the real value comes from trying it on your own system and adapting the variations above to what you actually need, so it is worth experimenting with in a safe, low-stakes situation before relying on it in a script or during troubleshooting. Keeping a note of the commands you find most useful, along with the variations that fit your workflow, turns scattered one-off tricks into a personal reference you can draw on whenever a similar task comes up again.