You don't need a browser or an app to check your internet speed. Your computer's Command Prompt (CMD) can do it with a few typed commands. This method is great when your browser is acting up, when you want raw data without ads, or when you're troubleshooting network issues. Let's walk through exactly how to do it.
Why Use CMD for Speed Tests?
Most people test their speed by visiting a site like Speedtest.now and clicking a button. That works great for everyday checks. But CMD-based testing has a few advantages worth knowing about.
No Browser Overhead
Your browser uses RAM, CPU, and network bandwidth just to run. Extensions, tabs, and background syncing can all eat into your results. CMD skips all of that. You get a cleaner measurement because there's less software between you and the network.
Better for Troubleshooting
When your internet feels slow, you need to figure out where the problem is. CMD tools like ping, tracert, and netstat let you check specific parts of your connection — not just overall speed. If you're already wondering why your internet is slow, CMD can help you pinpoint the cause.
Works Without a GUI
If you're working on a server, a remote machine, or a computer with a broken display driver, CMD is sometimes the only option. It's also scriptable, meaning you can schedule tests to run automatically and log results over time.
Built-In CMD Commands for Network Testing
Windows comes with several network tools already installed. None of them measure download or upload speed directly like a browser test does, but they give you data that matters just as much — especially latency (delay), packet loss, and route hops.
Ping
The ping command sends small packets of data to a server and measures how long the round trip takes. Open CMD (press Windows + R, type cmd, hit Enter) and type:
ping google.com
You'll see four replies with times in milliseconds (ms). A good result is under 20 ms for nearby servers and under 100 ms for servers across the country. If you want to understand what those numbers mean, check out our guide on what is good ping.
Tracert
Tracert (short for "trace route") shows every stop your data makes between your computer and a destination. Type:
tracert google.com
Each line shows a "hop" — a router or server your data passes through. If one hop shows a huge spike in time (say, jumping from 15 ms to 300 ms), that's likely where a bottleneck lives. This is one of the best ways to find out if the problem is your ISP, your home network, or the destination server.
Netstat
The netstat command shows all active connections on your computer. Type:
netstat -e
This displays the total bytes sent and received since your last reboot. It won't give you a speed number, but it helps you spot if something on your PC is secretly using a ton of bandwidth — like a background update or malware.
| CMD Command | What It Measures | Typical Good Result | Best For |
|---|---|---|---|
ping |
Latency & packet loss | Under 30 ms, 0% loss | Quick connection check |
tracert |
Route hops & per-hop latency | Under 15 hops, no huge spikes | Finding bottlenecks |
netstat -e |
Total bytes sent/received | Depends on usage | Spotting bandwidth hogs |
nslookup |
DNS resolution time | Instant response | DNS troubleshooting |
Using the Speedtest CLI for Actual Speed Numbers
If you want real download and upload speeds from CMD — not just latency — you need a third-party tool called Speedtest CLI by Ookla. It's free, lightweight, and runs entirely in the command line.