“The internet is slow” describes a feeling, not a diagnosis. The fastest route to a fix is to narrow the scope: one application or everything, one device or every device, Wi-Fi or wired, one time of day or all day.
1. Define the scope in five questions
Is one service affected?
Try another site, stream, download source, or game region. One slow destination may be overloaded or taking a poor route.
Is one device affected?
Test a second device in the same location. A single-device problem points toward its adapter, driver, security software, VPN, or background traffic.
Is only Wi-Fi affected?
Use Ethernet for a control test. A healthy wired result moves the investigation to signal, interference, roaming, or the wireless adapter.
Does time of day matter?
Evening-only slowdowns may indicate local radio congestion, shared ISP capacity, or household demand.
Did anything change?
A new router, driver, VPN, endpoint-security product, mesh node, cable, or Windows update is useful context—even when it is not the cause.
2. Match the symptom to the measurement
| Measurement | Meaning | Common symptom |
|---|---|---|
| Bandwidth | How much data can move per second | Large downloads and high-resolution streams take longer. |
| Latency | Time for a packet to travel and return | Games, remote desktops, and conversations feel delayed. |
| Jitter | Variation in delay | Calls and games feel uneven even when average latency looks acceptable. |
| Packet loss | Traffic that never arrives | Freezes, retransmissions, robotic audio, and disconnects. |
A fast speed test can coexist with bad latency under load. If calls or games degrade only while someone uploads or downloads heavily, investigate queueing and your router’s traffic-management options.
3. Test the path from near to far
Open a terminal and find the default gateway:
ipconfigLook for Default Gateway on the active adapter, then test it:
ping -n 30 192.168.1.1Replace the example with your gateway. On a stable wired LAN, delay should be low and consistent with no loss. Wi-Fi may vary more, but loss or large spikes to the gateway reveal a local problem before the ISP is involved.
Next, test reachability to a public IP and then a hostname:
ping -n 20 1.1.1.1
ping -n 20 example.comIf the public IP works but the hostname does not, name resolution deserves attention. Be aware that some networks and hosts deprioritize or block ping, so one failed ping is not conclusive.
See where delay appears
tracert example.com
pathping example.comtracert shows the discovered route. pathping takes longer but samples loss and delay. A router that does not answer diagnostic packets is not automatically dropping normal traffic; look for problems that continue into later hops and correlate with the real symptom.
4. Check whether DNS is the problem
DNS problems often look like a pause before a page begins loading, “server not found” errors, or some names resolving while direct IP connectivity still works.
nslookup example.com
ipconfig /flushdnsFlushing the cache removes stored answers on the PC; it does not repair an ISP outage or increase bandwidth. If your configured resolver is consistently failing, test a reputable alternative at the router or adapter and record the original settings first.
5. Diagnose Wi-Fi as a radio link
- Test in the same room as the access point.
- Compare 2.4 GHz with 5 GHz or 6 GHz where supported.
- Move the router into the open and away from large metal objects.
- Check whether the client is attached to the expected mesh node.
- Update the Wi-Fi adapter and router firmware from their manufacturers.
- Test with Bluetooth-heavy accessories temporarily disconnected if interference is suspected.
Windows can generate a wireless report with an elevated terminal:
netsh wlan show wlanreportThe report includes recent sessions, disconnect reasons, adapter details, and connection history. Treat it as diagnostic context rather than a score.
6. Contact the ISP with evidence
Prepare the service address, modem or gateway status, times of failure, wired test results, affected devices, and examples of packet loss or speed degradation. State whether restarting the gateway changes the result and for how long.
That evidence helps support distinguish an access-line or capacity problem from Wi-Fi coverage inside the home.