Your browser spins. The page times out. You reload twice and nothing changes. The first instinct is to blame your internet provider, but that might be the wrong call entirely. A single unresponsive website and a genuinely broken connection can feel identical from where you sit, yet each one needs a completely different fix. This guide walks you through a real diagnostic flow so you can stop guessing and start solving.
Diagnostic Snapshot
- Run a speed test first to establish whether your connection is actually healthy before blaming any specific site.
- If your speeds look normal, verify whether the site is down for everyone or failing only on your end.
- ISP-specific quirks for Xfinity, AT&T Fiber, and Starlink can make a good connection feel broken even when the numbers say otherwise.
Start with a Speed Test, Not a Hunch
Before touching anything else, run an internet speed test. It hands you hard numbers instead of impressions. A page timing out feels identical whether your download speed has cratered to 1 Mbps or the target server is simply offline, but a speed test separates those two scenarios right away.
Run the test from a device connected directly to your router with an ethernet cable if possible. Wi-Fi introduces variability that muddies the picture. Run the test two or three times in a row and note the average. Speeds fluctuate slightly between runs, and that is normal. A consistent reading gives you something reliable to build on.
Pay attention to more than just the download number. Upload speed matters if you are on a video call or sending large files. Ping measures how fast your connection responds to a request, and it affects gaming and voice calls far more than raw throughput does. The FCC publishes broadband speed benchmarks that break down what different activities actually require, which gives useful context when you read your own results.
Reading What Your Speed Test Results Are Actually Telling You
A speed test result is a map. You just have to know how to read it. Numbers that fall well below what your ISP advertises point toward a connection problem at the network level. Numbers that land close to your plan's rated specs suggest the problem lives somewhere else entirely.
These results tend to signal a genuine connection problem rather than a site-specific one:
- Download speed is 50% or more below your plan's rated speed on a wired connection
- Ping is consistently above 150ms, even outside of peak evening hours
- Any packet loss appears during the test, even a small percentage
- Multiple websites and apps are failing simultaneously, not just one
- The problem clears up after you restart your modem and router
If none of those describe your situation, your connection may actually be working fine. The problem is likely somewhere downstream of your home network, and that changes everything about how you troubleshoot it.
When the Speed Test Looks Fine but a Page Still Won't Load
This is where the real detective work begins. Your speed test came back healthy. Download is close to what your ISP promised. Ping looks reasonable. Yet the page you need is stuck at a white screen or throwing a connection error.
The most likely explanation at this point is that the website itself is having trouble. Servers go offline. Maintenance windows get miscommunicated. A sudden traffic spike can overwhelm a smaller site's infrastructure in minutes. None of that is something you can fix from your end, but knowing it matters because it tells you not to spend the next hour restarting hardware that works perfectly well.
The reliable next step is to check a website against real-time monitoring data. If the tool confirms the site is down for everyone, stop troubleshooting immediately and wait for it to come back online. If it shows the site is up everywhere except for you, that is a more specific problem worth digging into.
When a site shows as accessible globally but still will not load on your device, a few things are worth ruling out. Your browser cache may have stored a broken version of the page. Your DNS resolver could be returning a stale or incorrect address for the domain. A local firewall or parental control setting might be silently blocking the request. A simple test is to open the same URL in a different browser or on your phone using mobile data. If it loads there without trouble, the issue is device-side, not connection-side.
Narrowing It Down to Your Home Network
Your speed test looked fine. The site is confirmed live for everyone else. You still cannot reach it from your main computer. At this point, the problem is almost certainly between your device and your router.
Start by flushing your DNS cache. On Windows, open a command prompt and type ipconfig /flushdns. On a Mac, the command varies slightly by OS version but typically involves running dscacheutil -flushcache in the terminal. DNS issues are surprisingly common and surprisingly easy to overlook. Your device may have cached an old or incorrect IP address for the site, and no amount of page reloading clears that on its own.
If flushing DNS changes nothing, try switching your DNS resolver. Your router likely defaults to your ISP's DNS servers, which can sometimes lag behind or return errors. Switching to a public resolver like Cloudflare's 1.1.1.1 or Google's 8.8.8.8 takes about two minutes and eliminates the ISP's DNS infrastructure as a variable entirely.
Running a traceroute is another useful step. On Windows the command is tracert [site address]. On Mac and Linux it is traceroute [site address]. The output shows each hop your traffic takes on the way to the destination. If it stops at your router, the issue is local. If it travels several hops and stalls somewhere inside your ISP's network, the problem is upstream, and a call to your provider is the right next move.
ISP-Specific Patterns Worth Knowing
Speed test numbers can look acceptable on paper and still reflect a degraded experience. The reason depends heavily on which ISP you use and what technology delivers your service. Xfinity, AT&T Fiber, and Starlink each have characteristic failure patterns that a single midday speed test can easily miss.
How Xfinity, AT&T Fiber, and Starlink Behave Differently Under Stress
| Provider | Common Frustration | What to Test |
|---|---|---|
| Xfinity (cable) | Node congestion during evening hours causes speeds to drop sharply between 7pm and 10pm even when daytime tests look healthy | Run tests at 9am and again at 9pm on the same day and compare upload alongside download |
| AT&T Fiber | Gateway firmware bugs or optical network terminal faults cause intermittent drops that a single speed test can miss entirely | Check the gateway's diagnostic page for error log entries and fully power cycle both the ONT and the gateway |
| Starlink (satellite) | Physical obstructions to the dish cause brief but repeated outages that register as normal on a one-off speed test | Open the Starlink app and review obstruction history; even a small blockage can cause dozens of drops per hour |
One thing all three providers share: their speed test results can look fine precisely because speed test traffic itself sometimes gets prioritized on the network. That is a known behavior in cable infrastructure especially. If your test shows 400 Mbps but streaming video still buffers every few minutes, run the test several times at different points in the day before concluding everything is working as it should.
A few things worth trying when your ISP tests look acceptable but something specific still refuses to load:
- Test from a second device on the same network to confirm whether it is device-specific or affects everything
- Connect one device directly to the modem with ethernet, bypassing the router, to rule out router-level issues
- Call your ISP and ask them to run a line diagnostic from their end, which surfaces signal or provisioning problems invisible from inside your home
- Check your router's event log for repeated disconnects, even brief ones that would not register on a standard speed test
Putting the Answer to Work Before the Next Outage Hits
There is genuine value in knowing exactly what is broken before you start fixing things. Restarting your modem achieves nothing if the site is simply offline. Waiting for a site to recover does nothing if your actual connection is degraded. Getting to the right answer faster means less wasted time and far less frustration when the problem turns out to be outside your control.
The flow is logical once you follow it through. A speed test confirms whether the connection is healthy. A site status check separates a local network fault from a server-side failure. From there, DNS flushing, traceroutes, and ISP-specific diagnostics close the remaining gaps. Each step rules something out, and ruling things out is exactly how you narrow your way to a fix that actually works.
For Xfinity users, evening congestion is the first suspect when daytime tests look fine. For AT&T Fiber, the ONT and gateway are worth cycling before calling support. For Starlink, the app's obstruction data tells a clearer story than any single speed reading. Knowing your provider's typical failure pattern is half the diagnosis before you even pick up the phone.
The next time a page refuses to load, resist the urge to restart everything at once. Run the test first. Check the site's status. Then follow the evidence wherever it leads. That approach saves time almost every single time.