d to type in a different command prompt.
This new prompt will be Ping www.thewebsitename.com
Keep in mind that by using the ping command, you’re only sending and receiving four packets. If you want a more extended test, you’ll have to type the following: Ping www.thewebsitename.com -t
This test will continue until you press the Ctrl + C key combination to put a stop to it.
Seeing Packet Loss in macOS
For Mac devices, you can use the Terminal folder to run the command prompt: Ping 127.0.0.1.
You’ll find this folder either pinned to the dock (the lower menu bar you see as soon as you open your device) or in the Other folder after clicking on the Launchpad icon.
Seeing Packet Loss in Linux
For Linux, also you need to click on Terminal to run the command prompt.
You’ll find Terminal in the Linux apps folder on the Launcher. And in this case, the command will be the same as macOS (Ping 127.0.0.1).
Once you run the ping command, the test will run indefinitely, just like the ping -t command in Windows. You’ll have to type the Ctrl + C or Command + C key combination, depending on your device, to stop the test.
While carrying out these tests, you’ll notice that random drops are inevitable, and that’s okay. It’s a continuous packet loss that’s the problem.
Step 2 — Diagnose the Different Causes of Packet Loss
There are four different causes of packet loss. I’ll explain how you can detect each one of them below.
Detecting Bandwidth Congestion
Congestion is inevitable, especially during the busiest time of the day. A congested network experiences high latency, higher than normal loss rates, and jitter increases, which is why they’re so undesirable.
Monitor your network by looking at your latency, loss rates, and jitter to measure congestion and see how they vary during the day. If you’re lucky, the congestion will only last a few minutes, but it can also take longer.
Detecting Faulty Network Wires
Wired networks handle a lot of traffic. If they start to deteriorate, you will face packet loss issues as data sent inefficiently—precisely why you should check the ethernet cables.
If you think wires are the main cause of your packet loss, check your cables thoroughly to ensure no visible exterior damage. Even dirty fiber connectors can lead to packet loss. Your network connection points should also be secure.
Detecting Software Issues
The whole point of using a software tool is to transfer data. Therefore, when it stops working properly, it can lead to packet loss.
An error in the programming can make the software dysfunctional, which, in turn, could cause unexpected behavior on the network. This can be because of software bugs or a long due update.
A slow connection is a dead giveaway of pending software issues.
Open Task Manager on your computer to see how the apps are communicating with the network. After that, check whether the specific software or application uses a lot of bandwidth even when it’s not in use.
A tab within Task Manager will show you the application history of the past 30 days. You can use the information to compare the usage with the latency you’re experiencing.
Detecting Weak Wi-Fi networks
Weak Wi-Fi signals hinder the transmission of information packages you send across your network. Even interference over the radio frequency or traveling through thick walls can cause destruction.
Since it’s usually wireless networks or Wi-Fi that suffer more setbacks and interference than wired connections, you should check your Wi-Fi status to determine the packet loss source.
Check the internet on your device. This will have several lines that indicate your Wi-Fi’s strength.
If you see a weak signal, it means the network is overloaded and hence cannot accommodate all of your devices adequately.
Step 3 — Fixing the Different Causes of Packet Loss
Now that you know how to detect the four causes of packet loss, the next step is knowing how to fix it.
Similar to how I explained detection, I’ll tell you how to fix packet loss issues based on the cause.
Fixing Bandwidth Congestion
By tracking your network performance, you can identif