"The internet is slow" almost always means one of two very different things: the connection coming into your house is slow, or something inside your house is slowing it down. Those have completely different fixes, and guessing wastes hours. This decision guide gives you a step-by-step method to isolate exactly where the slowness lives before you change anything.

Why the distinction matters

If the bottleneck is your ISP, no amount of rearranging cables and routers will help — you need a plan change, a line repair, or a support ticket. If the bottleneck is inside your home, calling the ISP is a dead end, because their equipment is delivering full speed to your front door while an old switch, a bad cable, or weak Wi-Fi throttles it from there. Telling the two apart is the single most valuable diagnostic skill in home networking, and it hinges on one idea: separate the internet path from the local path, and test each on its own. That split is the whole subject of LAN vs internet speed testing.

The step-by-step method

Step 1: Test wired, straight off the router

Plug a capable computer directly into the router (or the modem/gateway) with a good Ethernet cable and run an internet speed test. This removes Wi-Fi from the equation entirely and shows you the best your connection can do.

• If this matches your plan, your incoming connection is fine — the bottleneck is elsewhere in the house. Skip to Step 3.
• If this is well below your plan even wired, the problem is your ISP connection, the modem, or the plan itself. Go to Step 5.

Step 2: Compare wired to Wi-Fi

Now run the same internet test over Wi-Fi from where you normally sit. If wired hits your plan but Wi-Fi is much slower, you have found it: the bottleneck is wireless, not the internet. The causes and fixes — bands, placement, generations — are covered in Ethernet vs Wi-Fi speed. If Wi-Fi and wired are both slow together, the issue is upstream of your Wi-Fi.

Step 3: Run a LAN test between two local devices

This is the step most people skip, and it is the most revealing. Run a speed test between two devices on your own network — no internet involved — for example a laptop and a NAS, or two computers. This measures your internal wiring and hardware directly. A tool such as a LAN speed test like PulseLAN makes this straightforward, and the mechanics are laid out in how to test local network speed.

• On a gigabit LAN, two wired devices should move data at roughly 900+ Mbps. If they do, your internal wiring is healthy.
• If two wired devices only reach a couple hundred Mbps, something local is capping you — a 10/100 switch, a bad cable, or an old NIC — regardless of how fast your internet is.

Step 4: Hunt the slow local component

If the LAN test came back slow, find the weak link by substitution. Check every switch and adapter in the path for a 10/100 (fast Ethernet) limit, swap suspect cables for known-good ones, and confirm each device negotiated the speed you expect. Older or cheap gear and marginal cabling are the usual culprits, and the cable rating itself can be the cap — Ethernet cable categories explains which rating you need for which speed.

Step 5: Compare to your plan and test the modem directly

If even a wired test off the router is slow, verify what you are actually paying for, then test as close to the source as possible — ideally straight off the modem with nothing else connected. If the modem itself delivers full speed but the router does not, the router is the bottleneck. If the modem is slow too, the problem is the line or the ISP.

Step 6: Single device vs whole network

Finally, ask whether everything is slow or just one device. If only one device is slow while others are fine, the fault is that device — its adapter, its cable, its Wi-Fi, or its own load. If every device is slow at once, the fault is shared: the router, the modem, or the ISP.

Diagnostic decision table

Use this to jump straight to the likely culprit based on what you observe.

Observation	What it points to	Next step
Wired off router matches plan; Wi-Fi is slow	Wi-Fi bottleneck	Fix placement, band, or channel
Wired off router is well below plan	ISP, modem, or plan	Test off the modem; call ISP with results
Internet is fine but local transfers are slow	Internal LAN (switch/cable/NIC)	Run a LAN test; substitute components
Two wired devices cap near 100 Mbps	A 10/100 switch or port in the path	Replace with a gigabit switch
Only one device is slow	That device's adapter/cable/Wi-Fi	Test another device on the same port/spot
All devices slow at the same time	Router, modem, or ISP	Reboot, then test off the modem
Fast plan, but LAN tests below plan	Internal wiring is the ceiling	Upgrade switch/cabling to match the plan

A quick worked example

Say you pay for 1 Gbps but streaming buffers. You plug into the router: the wired test reads about 940 Mbps. Good — the internet is fine, so the ISP is off the hook. Over Wi-Fi in the living room you get 120 Mbps; in the same room as the router you get 550 Mbps. That pattern is textbook Wi-Fi distance and interference, not an internet problem. Now you run a LAN test between your desktop and your NAS and get 940 Mbps wired — the internal wiring is healthy too. Conclusion: spend your effort on Wi-Fi coverage, not on the ISP or the switches. Ten minutes of testing pointed you at the one thing worth fixing.

Putting it together

The whole method reduces to a few questions asked in order: Is it fast wired off the router? Is it only slow on Wi-Fi? Is it slow between local devices with no internet involved? Is it one device or all of them? Each answer eliminates a whole category. Test the internet path and the local path separately, compare against what you actually pay for, and change only the thing your tests have proven is slow.

Slowness feels like one problem, but it is really two questions wearing the same coat. Answer "ISP or home network?" first, and every fix that follows is aimed at the right target instead of the loudest guess.