Why is my internet slow?
Why is my internet slow?. A practical guide for network diagnosis and careful interpretation. One technical signal does not describe the whole path, so each connection layer should be checked independently and in a reproducible order.
Which metrics describe connection quality
Why is my internet slow? should not be reduced to one Mbps number. Throughput, latency, jitter and packet loss describe different properties, while Wi-Fi, Ethernet, competing devices, VPNs, routing and the test server all affect results. High throughput can coexist with poor latency under load.
How to isolate the bottleneck
Separate the LAN from the ISP path: check signal or cable, then ping while idle and under transfer, then throughput. Repeat measurements under controlled conditions. A problem that occurs only in the evening, only through a VPN, or only toward one destination points to different bottlenecks.
Concrete examples and values
Use these values as anchors when reading documentation or test output: throughput; latency; packet loss; Wi-Fi contention; VPN overhead; server/CDN limit.
Compare idle latency with latency during a saturated upload and download, not just headline Mbps. Also compare Ethernet with Wi-Fi and one destination with another so local radio contention, ISP congestion, VPN overhead, and remote-server limits are not mistaken for each other.
Common causes and mistakes
A common mistake is to treat one successful test as proof that the whole path is healthy. A reachable IP address does not prove DNS works, an open port does not validate the application protocol, and a fast speed test does not rule out latency, packet loss, or Wi-Fi contention. NAT, CGNAT, firewalls, CDNs, Anycast, and caches can also change what an observer sees and must be considered according to the question.
What the result does not prove
A technical result has limits. It normally cannot establish a person’s identity, the owner of a device, or the single root cause of an outage without additional evidence. IP geolocation is approximate, registration data can be redacted, and Internet routes can change. Security should not be reduced to one flag, address, or status value. A conclusion should match the specific property that was actually measured.
A reproducible troubleshooting sequence
Begin with a reproducible symptom, then verify local configuration, addressing, and DNS. Continue with routing, ports, and the application protocol. Make one change, repeat the measurement, and compare the outcome. This sequence reduces false conclusions and produces useful evidence for an administrator or Internet provider. After fixing the problem, repeat the original test to confirm that the observed symptom, rather than an unrelated condition, actually changed.