An internet speed test measures how fast your device reaches a distant server across your ISP link; a LAN speed test measures how fast two devices talk to each other inside your own home. They answer completely different questions, and one can look great while the other looks terrible.

If you have ever run an internet speed test that showed a blazing number, then watched a file crawl from your laptop to your network drive, you have already felt the gap between these two measurements. The confusion is understandable, because both report results in the same units and both use the word "speed." But they test different paths, hit different bottlenecks, and are useful in different situations.

Two different paths through your network

Picture the journey data takes when you load a web page. It leaves your device, crosses your local network to your router, travels out through your modem and ISP, hops across the public internet to a server that might be hundreds of miles away, and then makes the return trip. An internet speed test measures that entire round trip.

Now picture copying a video file from your laptop to a network-attached storage (NAS) box in the closet. That data leaves your laptop, reaches your router or switch, and lands on the NAS. It never touches your modem, never leaves the building, and never sees your ISP. A LAN speed test measures only this local segment.

Because the two paths barely overlap, they are limited by almost entirely different things. Your internet result is capped by whatever plan you pay for and the quality of the path to the remote server. Your LAN result is capped by your own equipment: the Wi-Fi link, the Ethernet cabling, the switch, and the network interface cards (NICs) in your devices.

Why a fast internet plan can still have slow local transfers

Say you subscribe to a gigabit internet plan and consistently measure around 900 Mbps to the internet. It feels reasonable to assume everything on your network moves at that speed. Then a 4K movie takes twenty minutes to copy to your NAS, working out to a fraction of what you expected.

The internet plan is irrelevant to that copy. What matters locally is the weakest link in the device-to-device path:

• Wi-Fi. A laptop on 2.4 GHz Wi-Fi in another room might sustain only 30–80 Mbps of real throughput regardless of a gigabit plan. Distance, walls, interference, and the Wi-Fi generation of your gear all cut into it. See Ethernet vs. Wi-Fi speed and Wi-Fi bands for why.
• Cabling. An old Cat5 run or a damaged cable can quietly negotiate down to 100 Mbps instead of gigabit, throttling everything on that link. Our guide to Ethernet cable categories covers what each rating supports.
• The switch. A cheap or aging switch may only have Fast Ethernet (100 Mbps) ports, becoming an invisible ceiling for anything passing through it.
• The NIC or the storage device. A laptop with a gigabit port still tops out near 112 MB/s, and the NAS's own disks may be the real limit — a topic we dig into in why NAS transfers are slow.

None of these show up in an internet speed test, because that test never travels the local path where they live.

And the reverse: slow internet, fast LAN

The opposite happens too. You might have a modest 100 Mbps internet plan but a fully wired gigabit network at home. Copying files between two wired computers can run near 900+ Mbps even though your connection to the outside world is nine times slower. Local traffic never leaves the house, so it is not constrained by the plan at all. This is exactly why local backups, media servers, and moving large project files between machines can feel instant even on an ordinary internet subscription.

Side-by-side comparison

	Internet speed test	LAN speed test
What it measures	Device to a distant server, across your ISP and the public internet	Device to another device inside your own network
Main limiting factor	Your internet plan and the path to the server	Your Wi-Fi, cabling, switch, and NICs
Typical numbers (as of 2026)	Whatever you pay for: ~50 Mbps to ~2 Gbps down, often less up	Wired gigabit ~900+ Mbps; good Wi-Fi 6 ~300–900 Mbps; weak Wi-Fi under 100 Mbps
Tools	Ookla Speedtest, Fast.com, your ISP's tester	a LAN speed test like PulseLAN, iperf3, a large file copy
Use it when	Checking if you get the plan you pay for, or diagnosing streaming/downloads	Diagnosing slow file copies, NAS backups, or local media streaming

Which test should you run?

Match the test to the symptom. If web pages, downloads, and video streaming feel slow, start with an internet speed test — the problem is likely your plan, your ISP path, or Wi-Fi feeding an internet-bound device. If instead a specific local task drags, such as backing up to a NAS, moving footage between two computers, or streaming from a home media server, run a LAN test. There is no point blaming your ISP for a copy that never reaches them.

When you are genuinely unsure which side is at fault, testing both in sequence is the fastest way to localize the problem. Our guide on telling whether the ISP or your home network is the bottleneck walks through that process, and how to test local network speed covers doing the LAN side properly.

Reading the results honestly

One more source of confusion: units. Speed tests almost always report megabits per second (Mbps), while your file manager shows the copy in megabytes per second (MB/s). Those differ by a factor of eight, so a "gigabit" that looks like 900 Mbps is only about 112 MB/s on the file-copy side. Before you conclude that a transfer is slow, make sure you are comparing like with like — our guide to bits versus bytes untangles it.

Both tests are worth having in your toolkit. The internet test tells you whether the outside world reaches you at full speed; the LAN test tells you whether your own house is holding you back. Knowing which one to reach for turns a vague "the network is slow" into a specific, fixable problem.