Few computer problems are as annoying as “the internet feels slow.” Your browser opens, eventually. Your video meeting works, until everyone sounds like a robot trapped in a soup can. Your online game loads, but your character moves three seconds after your brain has already filed a complaint. That delay is usually called latency, or more casually, lag.
The tricky part is that latency is not the same thing as download speed. A connection can advertise 500 Mbps and still feel sluggish if every request takes too long to travel out and come back. Think of bandwidth as the width of a highway and latency as the time it takes the first car to reach the destination. A wide highway is great, but if the route includes twelve toll booths, a confused goat, and a router from 2009, you will still be late.
Fortunately, Microsoft Windows includes several built-in tools that can help you test network and internet latency without installing mysterious “PC booster” software that promises miracles and delivers pop-ups. In this guide, we will cover three practical ways to test latency in Windows: Ping, Tracert and PathPing, and PowerShell with Resource Monitor. You will learn what each tool measures, how to run it, how to read the results, and what those numbers actually mean in real life.
What Is Network Latency?
Network latency is the delay between sending data and receiving a response. In most Windows tests, latency is shown as round-trip time, or RTT, measured in milliseconds. A lower number is better. A 15 ms response feels snappy. A 150 ms response may still be usable for browsing but can be noticeable in gaming, video calls, remote desktops, and cloud apps. A 500 ms response is when your video meeting starts to resemble a badly dubbed movie.
Latency can be affected by many things: physical distance, Wi-Fi signal quality, router performance, ISP congestion, VPN routing, DNS delays, overloaded servers, packet loss, and even other devices in your home network. That is why a good latency test should not rely on only one number. You want to compare local latency, internet latency, route behavior, and application-specific connections.
Before You Test: Prepare Windows for Cleaner Results
Before running any test, close large downloads, cloud backups, game updates, and streaming apps. If someone in the house is downloading a 90 GB game update, your latency test may accuse your internet provider when the real villain is a console in the living room wearing a tiny crown.
For the most accurate baseline, test from a wired Ethernet connection first. Wi-Fi is convenient, but it adds variables such as interference, distance, walls, signal strength, and competing wireless devices. If Ethernet latency is stable but Wi-Fi latency jumps wildly, you have probably found a local wireless issue rather than a full internet problem.
You should also test more than one destination. Try your router, a reliable public internet host, and the specific service that feels slow. This helps separate local network lag from broader internet lag.
Way 1: Use Ping to Measure Basic Latency
Ping is the fastest way to test latency in Microsoft Windows. It sends small ICMP echo requests to a destination and reports how long the replies take to return. Ping is excellent for answering the first big question: “Is this connection responding quickly, slowly, or not at all?”
How to Run Ping in Windows
Press Windows + R, type cmd, and press Enter. In Command Prompt, type:
Windows will usually send four requests and display results similar to this:
The most important values are time, packet loss, and the average round trip time. The time value shows the latency for each reply. The packet loss percentage shows whether any requests failed. The average gives you a quick overall view.
Useful Ping Commands
To send more than four requests, use:
To run a continuous ping until you stop it, use:
Press Ctrl + C to stop the test. Continuous ping is useful when the problem happens randomly. For example, if your internet feels fine for two minutes and then freezes, run continuous ping while using your connection normally. Look for sudden spikes, timeouts, or packet loss.
To test your local router, first find your default gateway:
Look for Default Gateway, then ping that address:
If your router ping is consistently under 5 ms on Ethernet, your local connection is likely fine. If it jumps from 2 ms to 300 ms or shows timeouts, the issue may be inside your home or office network.
How to Read Ping Results
Here is a simple way to interpret ping results:
- 0-20 ms: Excellent for gaming, calls, remote work, and browsing.
- 20-50 ms: Very good for most internet use.
- 50-100 ms: Usable, but real-time apps may begin to feel less crisp.
- 100-200 ms: Noticeable delay, especially in gaming and video calls.
- 200 ms or higher: High latency; interactive tasks may feel laggy.
- Any packet loss: Worth investigating, especially if repeated.
Remember that ping is not perfect. Some servers block or deprioritize ICMP traffic, which can make ping look worse than the actual app experience. Also, ping measures round-trip time, not one-way delay. Still, as a first diagnostic tool, it is fast, built in, and surprisingly useful.
Way 2: Use Tracert and PathPing to Find Where Lag Starts
If ping tells you that latency exists, Tracert helps show where packets travel on the way to a destination. It lists the routers, or “hops,” between your PC and the target. This is useful because lag is not always caused by your computer or your ISP. Sometimes the delay appears several hops away, somewhere out on the internet where your packets are apparently taking the scenic route.
How to Run Tracert in Windows
Open Command Prompt and type:
You may see output like this:
Each line is a hop. Each hop usually shows three time measurements. If the first hop is already high, the issue may be your router, cable, Wi-Fi, or local network. If the first few hops are fine but latency jumps later, the issue may be with the ISP route, a backbone provider, or the destination network.
What Asterisks Mean in Tracert
If you see asterisks like this:
Do not panic. Some routers simply do not respond to traceroute-style probes. If later hops continue normally, that hop may be ignoring diagnostic traffic while forwarding real traffic just fine. In other words, the router may be rude, not broken.
Use PathPing for Deeper Latency and Packet Loss Testing
PathPing combines ideas from ping and tracert. It traces the route, then sends repeated probes to each hop and calculates packet loss and latency statistics. It takes longer than tracert, but it can provide a clearer picture when packet loss is suspected.
Run:
Or use /n to skip name resolution and make the first stage faster:
PathPing may take a few minutes. When it finishes, look for packet loss percentages. If loss starts at your first hop, suspect your local network. If loss appears after your ISP gateway and continues to later hops, the issue may be upstream. If one middle hop shows loss but later hops do not, that device may simply be limiting diagnostic replies.
When to Use Tracert vs. PathPing
Use tracert when you want a quick route overview. Use pathping when you need more detail about packet loss and latency across multiple hops. For everyday troubleshooting, tracert is the flashlight; PathPing is the flashlight with a clipboard and a suspiciously serious expression.
Way 3: Use PowerShell and Resource Monitor for App-Specific Latency
Ping and tracert are great, but sometimes you need to test a specific service, port, or application. That is where PowerShell and Resource Monitor become useful. These tools help you move beyond “Is the internet slow?” and toward “Is this exact service responding properly?”
Test Latency with PowerShell Test-NetConnection
Right-click the Start button and choose Terminal or Windows PowerShell. Then run:
You may see output showing whether ping succeeded and the round-trip time. For more detail, run:
To test whether a web server is reachable on port 443, use:
This is helpful because a server may block ping but still accept normal HTTPS traffic. If PingSucceeded fails but TcpTestSucceeded is true on port 443, the website may be reachable even though ICMP ping is blocked.
Run a Route Trace in PowerShell
PowerShell can also perform route tracing:
This gives you a PowerShell-friendly way to inspect the route without switching back to Command Prompt. It is especially useful for administrators, support technicians, or anyone who wants structured diagnostic output.
Use Resource Monitor to Watch Live Network Activity
Windows Resource Monitor can show which processes are using the network and what remote addresses they are connected to. To open it, press Windows + R, type:
Then press Enter and select the Network tab.
Look at these sections:
- Processes with Network Activity: Shows apps currently sending or receiving data.
- Network Activity: Shows remote addresses and transfer rates.
- TCP Connections: Shows active TCP connections, packet loss, and latency where available.
- Listening Ports: Shows services waiting for network connections.
This is useful when one app feels slow but everything else seems fine. For example, a browser, game launcher, VPN client, or cloud backup tool may be generating traffic in the background. Resource Monitor helps reveal which process is talking the most, which remote server it is contacting, and whether connection latency looks suspicious.
Common Causes of High Latency in Windows
Weak Wi-Fi Signal
Wi-Fi is one of the most common causes of inconsistent latency. A weak signal can produce spikes, jitter, and packet loss even when download speed looks acceptable. Move closer to the router, switch from 2.4 GHz to 5 GHz or 6 GHz if available, or test with Ethernet.
Router Overload
Routers can get overwhelmed by too many devices, old firmware, heat, or heavy traffic. Restarting the router is not magic, but it can clear temporary issues. Updating firmware and replacing outdated hardware can also help.
Bufferbloat
Bufferbloat happens when network equipment queues too much data during heavy uploads or downloads. The connection may have high bandwidth, but latency spikes under load. If your ping is fine when idle but terrible during uploads, bufferbloat may be the culprit. Router quality-of-service settings, smart queue management, or a better router can help.
VPN Routing
A VPN can improve privacy or access, but it may add distance and extra processing. If latency rises only when the VPN is enabled, try another VPN server location or test without the VPN.
DNS Delays
DNS does not usually affect the ping time after a connection is established, but slow DNS can make websites feel delayed before they load. If websites pause before opening but then load quickly, DNS may be part of the problem.
ISP Congestion
If latency is fine in the morning but awful every evening, congestion may be occurring during peak hours. Run tests at different times and keep screenshots or logs before contacting your provider.
Practical Testing Workflow
Here is a simple Windows latency testing workflow you can use whenever your connection feels laggy:
- Ping your router:
ping -n 20 192.168.1.1 - Ping a public destination:
ping -n 20 google.com - Run a route trace:
tracert google.com - Check packet loss:
pathping google.com - Test the app port:
Test-NetConnection example.com -Port 443 - Watch live apps: Open Resource Monitor and inspect the Network tab.
This sequence helps you move from local to external testing. If the router ping is bad, fix the local network first. If the router is fine but the internet ping is bad, investigate ISP, routing, VPN, or congestion. If only one service is slow, test that service directly.
Experience Notes: What Real-World Latency Testing Teaches You
After testing network latency on Windows machines in homes, small offices, classrooms, and remote-work setups, one lesson becomes obvious: the first result is not always the truth. A single ping test is like checking the weather by looking out the window for two seconds. Useful, yes. Complete, absolutely not. Latency problems often appear in patterns, and those patterns matter more than one dramatic number.
One common experience is the “perfect speed test, terrible meeting” problem. A user runs a speed test and proudly reports 600 Mbps down. Meanwhile, their video call sounds like a fax machine arguing with a blender. The issue is usually not raw speed. It is jitter, packet loss, or upload congestion. A continuous ping while joining a video meeting often reveals the truth: latency stays low while idle, then jumps wildly when the camera turns on or when cloud backup starts uploading files.
Another frequent discovery is that Wi-Fi can look innocent until you compare it with Ethernet. On Wi-Fi, ping might bounce from 8 ms to 140 ms every few seconds. On Ethernet, it stays at 2 ms like a well-trained golden retriever. That comparison instantly changes the troubleshooting plan. Instead of blaming Windows, the ISP, or the moon, you focus on router placement, channel interference, signal strength, or upgrading the wireless access point.
Tracert also teaches humility. Many people see a timeout in the middle of a route and assume they found the broken router. Sometimes they have. Often they have not. Some routers ignore diagnostic probes while forwarding real traffic normally. The better clue is whether high latency or loss continues to every hop after that point. If one hop looks bad but later hops are fine, that hop may simply be too busy to answer your diagnostic knock at the door.
PathPing is especially useful when dealing with intermittent packet loss. It takes patience, but it can show whether loss starts inside the local network, at the ISP edge, or farther away. In support situations, PathPing results can be more persuasive than saying, “The internet feels weird.” Providers and IT teams respond better to actual numbers, timestamps, and repeated evidence.
PowerShell is the tool that often saves time when ping is blocked. Many modern services do not respond to ICMP, but their web ports still work. Running Test-NetConnection against port 443 can confirm whether the service is reachable even when ping fails. This prevents false alarms and avoids the classic mistake of declaring a website “down” just because it refuses to answer ping.
The most practical habit is to test during the problem, not after it disappears. Lag is sneaky. It arrives, ruins your call, eats your patience, and vanishes right when you open a diagnostic tool. Keeping a Command Prompt window ready with continuous ping during work, gaming, or streaming can capture the spike when it happens. Those logs are far more useful than memory, especially because memory tends to become dramatic under stress.
Finally, good latency testing is about comparison. Compare Wi-Fi to Ethernet. Compare idle latency to loaded latency. Compare your router to an internet host. Compare one website to another. Compare morning to evening. The answer is usually hiding in the difference between two tests, not in one lonely number. Windows gives you the tools; your job is to make the tools tell a consistent story.
Conclusion
Testing network and internet latency in Microsoft Windows does not require expensive software or advanced certification. Start with Ping to measure basic round-trip time and packet loss. Use Tracert and PathPing to see where delays or loss begin along the route. Then use PowerShell Test-NetConnection and Resource Monitor to test specific services, ports, and applications.
The key is to test methodically. Do not stop at “my internet is slow.” Find out whether the lag begins at your PC, your Wi-Fi, your router, your ISP, a VPN, or the destination service. Once you know where the delay starts, fixing it becomes much less like guessing and much more like troubleshooting. Your network may still misbehave occasionally, but at least now you can catch it in the act.
Note: The commands in this guide are read-only diagnostic commands. They are safe for normal Windows troubleshooting, but results can vary because some servers and routers block or limit diagnostic traffic.
