Speed Test & Network Diagnostics: How to Diagnose Why Your Internet Is Slow

Why Your Internet Is Slow (It Is Not Always Your ISP)

When your internet feels slow, the instinct is to blame your ISP. But the reality is more nuanced. Your connection passes through many points between your device and the server you are trying to reach, and a bottleneck at any one of them causes slowness:

Here are the most common culprits, in order of likelihood:

• Your Wi-Fi: Interference, distance from router, too many devices on 2.4GHz band.
• Your device: Background updates, malware, browser extensions, outdated network drivers.
• DNS resolution: Slow DNS servers add 200-2000ms before any page even starts loading.
• Your ISP: Throttling, congestion during peak hours, provisioning errors on your line.
• The destination server: The site you are visiting might be slow — not your internet.

How Internet Speed Actually Works

Internet speed is not a single number. It is a combination of three metrics, and each affects your experience differently:

The Systematic Diagnosis Method

Do not just try random fixes. Follow these 5 steps in order, and you will pinpoint the problem:

Step 1: Run a Speed Test

Start with a baseline. Open the Speed Test and run it. You will get four numbers: download speed, upload speed, latency, and jitter.

Compare your results to what your ISP plan promises:

What the numbers tell you:

• Low download + low upload: Broadband connection issue (ISP, modem, or wiring).
• Low download + normal upload: Possible throttling or congestion on the download path.
• High latency (>100ms): Distance to server, routing issues, or satellite connection.
• High jitter (>30ms): Network congestion or interference (especially on Wi-Fi).

Step 2: Run a Traceroute

If your speed test shows a problem, the next question is: where in the path is the bottleneck? A traceroute shows every hop between you and the destination, with the latency at each step.

Use our Traceroute tool to trace the path from our servers to any destination. Look for:

• A sudden latency spike at one hop: That hop is the bottleneck. If it is in your ISP's network (first 3-5 hops), contact your ISP. If it is further along, the issue is beyond their control.
• Timeouts at a hop: Some routers deprioritize ICMP, so timeouts alone do not always mean a problem. But if hops after the timeout also show high latency, there is a real issue.
• Inconsistent times: If the same hop shows 5ms, then 200ms, then 5ms, there is intermittent congestion.

Step 3: Check DNS Resolution

Slow DNS adds a hidden delay to every new connection. When you type a URL, your device must resolve the domain name to an IP address before it can even start loading the page. If your DNS server is slow, this can add 200-2000ms of invisible latency.

Use the DNS Lookup tool to check how quickly your domain resolves. Compare different DNS providers:

Step 4: Scan Open Ports

If specific services are slow or unreachable, a firewall might be blocking or throttling certain ports. Use the Port Checker to verify:

• Port 80/443: HTTP/HTTPS — if these are blocked, no websites will load.
• Port 53: DNS — if blocked, domain resolution fails.
• Port 25/587: SMTP — if blocked, you cannot send email (many ISPs block these).
• Port 3389/22: Remote Desktop/SSH — if blocked, you cannot remote into servers.

Step 5: Inspect HTTP Headers

Sometimes the slowness is not your network at all — it is the server on the other end. Use the HTTP Headers tool to check:

• Cache-Control headers: Missing or misconfigured caching means the server re-sends everything on every visit.
• Content-Encoding: If gzip/brotli compression is missing, pages are 3-5x larger than they should be.
• Server response time: The X-Response-Time or CF-Ray headers reveal how long the server takes to generate the page.
• Redirect chains: Multiple 301/302 redirects add round trips. Each redirect costs 50-200ms.

Common Culprits and Fixes

When to Call Your ISP (and What to Tell Them)

If you have worked through all five diagnostic steps and the problem persists, it is time to call your ISP. But do not just say "my internet is slow." Arm yourself with specific data: your speed test results showing the gap between promised and actual speeds, traceroute output showing where latency spikes occur, and the times of day when problems are worst. Ask them to check for line noise, signal attenuation, and provisioning errors on your connection. Request they run a line test from their end. If your speeds are consistently below what your plan promises, you may have a provisioning error, a faulty modem, or degraded copper wiring — all of which are the ISP's responsibility to fix. Document everything, including the reference numbers for each call, as this creates a paper trail if you need to escalate or switch providers.