How to Test Internet Speed Using CMD

You don't always need a browser to check your connection. Windows Command Prompt can measure ping, packet loss and the route your traffic takes — and with one free tool, full download and upload speed too.

First: open Command Prompt

Press the Windows key, type cmd, and press Enter. A black window opens — that's Command Prompt. Type the commands below and press Enter after each one.

1. Check ping and packet loss

ping google.com -t

This sends a small packet to Google every second, continuously, and shows the round-trip time for each one. Let it run for 20–30 seconds, then press Ctrl + C to stop it. The summary shows the minimum, maximum and average ping, and how many packets were lost.

  • Average under 50 ms — good for browsing, calls and gaming.
  • Average 50–100 ms — usable, but games will feel laggy.
  • Wildly varying times (20 ms, then 300 ms, then 40 ms) — high jitter, which freezes video calls even when speed looks fine.
  • "Request timed out" — packet loss. Occasional timeouts happen; regular ones mean an unstable line.

Try pinging your own router too — ping 192.168.1.1 -t (or 192.168.10.1 on newer PTCL modems). If ping to the router is slow or lossy, the problem is inside your home (Wi-Fi or the router itself). If ping to the router is clean but ping to Google is bad, the problem is your line or beyond.

2. Trace the route to see where it slows down

tracert google.com

This lists every hop your traffic takes to reach Google, with the ping at each one. The first hop is your router (should be 1–5 ms on a cable). A sudden jump at one hop — say from 10 ms to 150 ms — shows where the delay starts. If the jump is at hop 1 or 2, it's your home network or your provider's local equipment; if it's several hops in, it's further up the network, and there's little you can do except report it.

3. Run a full speed test from the terminal

For download and upload speed (not just ping), install the free Ookla Speedtest command-line tool:

winget install Ookla.Speedtest
speedtest

The first run asks you to accept the licence; after that, speedtest prints your download speed, upload speed, ping and jitter, and the server it tested against — no browser needed. It's the same measurement engine as speedtest.net, so results are comparable with a browser test.

Prefer the browser? Our online speed test measures the same four numbers with a visual gauge and saves your history.

4. Check your Wi-Fi signal strength

netsh wlan show interfaces

This shows the Wi-Fi network you're connected to, the band (2.4 GHz or 5 GHz), the channel, and the signal strength as a percentage. Below about 50% signal, Wi-Fi becomes the bottleneck no matter how fast your line is — move closer to the router or switch to a cable and test again.

What the numbers mean

MeasurementGoodPoor
Ping to google.comUnder 50 msOver 100 ms
Ping to your router1–5 ms wired, under 20 ms on Wi-FiOver 50 ms, or timeouts
Packet loss0%Over 2% — calls and games suffer
Jitter (ping variation)Under 30 msOver 50 ms — stuttering calls

When CMD is better than a browser test

  • Diagnosing with support. Ping and tracert output is exactly what a technician asks for — copy it into your complaint.
  • Watching stability over time. A continuous ping shows drops and spikes a 30-second browser test can miss.
  • Testing without a browser. Useful on servers, remote machines, or a PC with browser problems.
  • Separating Wi-Fi from the line. Ping the router vs ping Google — the comparison locates the fault.

Frequently asked questions

How do I check my internet speed using CMD?

Open Command Prompt and run "ping google.com -t" for continuous ping and packet loss, or "tracert google.com" to see where latency builds up on the route. For a full download/upload speed test from the terminal, install the Ookla Speedtest CLI with "winget install Ookla.Speedtest" and then run "speedtest".

What is a good ping in CMD?

To a nearby server (google.com from Pakistan), under 50 ms is good and under 30 ms is excellent. Over 100 ms will feel laggy in games and calls. More important than the number itself is consistency: if ping jumps between 20 ms and 300 ms, you have a jitter problem even if the average looks fine.

What does "request timed out" mean in ping?

It means a packet never came back — packet loss. A few timeouts in a long test can be normal, but regular timeouts mean an unstable connection: a damaged line, a congested link, or a failing router. Note how often they happen and report it to your provider with the numbers.

Is the CMD speed test more accurate than a browser test?

For ping and packet loss, yes — the terminal has no browser overhead and shows every packet. For download/upload speed, the Ookla CLI and a good browser test measure the same thing; the CLI is mainly useful for scripting, remote help, and testing on machines without a browser.

Want the full picture?

Run the visual speed test for download, upload, ping and jitter in one go.