A large download took much longer than expected, so I ran a browser-based speed test and got 73 Mbps over Wi-Fi. I pay for a higher advertised speed, but I am not sure whether the test result reflects my connection or just wireless conditions.
What is the correct way to check whether I am actually getting the speed I pay for? Should I test over Ethernet with other devices disconnected, and which result should I compare against my plan?
Don’t use a Wi-Fi result as proof that the ISP is underdelivering. Wi-Fi adds variables such as distance, interference, router capability, device capability, and the band you are connected to. A 73 Mbps wireless test may say more about the local Wi-Fi link than the internet service.
Connect a computer directly to the router or modem with Ethernet, preferably using a gigabit-capable port and cable. Pause downloads, cloud backups, streaming, VPNs, and game updates, then disconnect or idle the other devices. Run the internet speed test several times, trying a nearby server and testing at different times of day. Make sure the computer itself is not limited by a 100 Mbps Ethernet adapter, since that usually tops out somewhere below 100 Mbps in an actual test.
Compare the wired result with the speed tier on your bill, not necessarily the biggest number in the provider’s advertising. Read whether the plan says “up to,” lists a typical speed, or has separate download and upload rates. Some connection overhead is normal, so a result a little below the plan rate is not automatically a problem. A wired result that repeatedly falls far short is worth reporting to the ISP.
For the large download, remember that download programs often show megabytes per second, while plans and speed tests use megabits per second. Divide Mbps by eight for a rough conversion. A 100 Mbps connection has a theoretical ceiling of about 12.5 MB/s, and the actual file server may be slower than your connection anyway.
A hidden speed cap in the router can make every test look like an ISP problem. QoS, bandwidth control, parental controls, traffic monitoring, or an old 100 Mbps WAN port may limit throughput even when the incoming line is fine. Temporarily disable those features and check the router’s WAN link speed in its status page.
If your provider has an app or modem diagnostics page, compare its “speed to gateway” result with the speed reaching your device. A good gateway result paired with a poor device result points to your equipment or home network. If the gateway itself repeatedly tests low, contact the ISP and ask them to confirm the modem’s provisioning and signal levels. That gives support something more useful than a single browser test over Wi-Fi.
Don’t compare the download’s MB/s figure directly with a speed test’s Mbps result. They use different units. A 73 Mbps connection tops out around 9 MB/s before protocol overhead, so a download showing roughly 7 to 8 MB/s may actually match that test pretty closely. The download server itself can be slower too.
For a fair check, connect one computer to the router with Ethernet, pause other streaming or downloads, and run Speedtest by Ookla against a nearby server a few times. If Ethernet reaches your plan speed but Wi-Fi stays near 73 Mbps, the ISP connection is probably fine and the wireless link is the limit. Make sure the device is using 5 GHz or 6 GHz rather than 2.4 GHz, and test close to the router before changing equipment or calling support.
The missing detail is whether that “large download” was transferring data the whole time or spending part of the time installing, unpacking, verifying, or writing files to disk. Game launchers are especially bad for this. They may download a chunk, pause network traffic while patching files, then continue. A slow drive, nearly full storage, or antivirus scanning can make the total job take much longer even when the internet connection is behaving normally.
@micro_rusty_admin is right about checking the units, but there is another mismatch here too. Speed tests usually open several connections at once to fill your available bandwidth. A file download may use fewer connections and depend on whatever limit the sender has set. That means a speed test can look fine while one particular download crawls. Trying a second large download from a different well-known service can tell you whether the first server was simply the bottleneck.
I would watch the live network usage in Task Manager or your system’s equivalent during the download. If it sits around the same rate most of the time, then you can compare that rate with the test after converting MB/s to Mbps. If network use repeatedly drops near zero while disk or CPU use jumps, your connection is probably waiting on the computer rather than the ISP.
The 73 Mbps Wi-Fi result still deserves a wired check, as the others said, but I would not assume it proves anything by itself. If your paid tier is 100 Mbps, that wireless result is not shocking. If you are paying for 500 Mbps or 1 Gbps and every capable wired device stays near 73 Mbps, then something is clearly limiting the connection. At that point, check whether the result plateaus at roughly the same number every time. A consistent ceiling often points to equipment, configuration, or provisioning. Results that swing widely are more likely to involve Wi-Fi conditions or congestion.
Before buying a new router or changing plans, separate the three questions: how fast the ISP delivers to the home, how fast your router delivers to the device, and how fast that particular download source sends the file. They can produce three very different numbers, and only the first one tells you whether the provider is actually underdelivering.
The download taking “too long” is not evidence by itself unless the expected time was realistic. File sizes are usually shown in GB, while connection speeds are sold in Mbps. The conversion is less flattering than the advertising.
For example, a 50 GB download at a steady 73 Mbps has a theoretical minimum of about 91 minutes. Real transfers take longer due to overhead, server limits, and the pauses @thread.vim described. If you expected it in 20 minutes, the expectation may be the problem.
Work backward from the actual file size and total time. Multiply the file size in GB by 8,000, then divide by the number of seconds. That gives a rough average in Mbps. It is more useful than judging the download by feel.
You still need a quiet, wired test to make a claim against the ISP. If that repeatedly lands near 73 Mbps on a much higher tier, save the results and call them. If only that download was slow, blame has not yet been assigned.
Browser tabs can lowball you all on their own since the browser itself becomes the bottleneck on faster lines. For the wired retest everyone’s suggesting, use the Speedtest desktop app instead of the website version and you’ll get a cleaner read. If both still sit at 73 on a higher tier, then start the ISP conversation.
If your device is connected through a Wi-Fi extender or a mesh satellite, 73 Mbps may be the speed of that wireless backhaul rather than your internet line. This is especially common with basic repeaters, which receive and retransmit traffic on the same radio. Even plugging an Ethernet cable into the extender does not create a true wired test because the extender still reaches the main router over Wi-Fi.
For a useful comparison, connect Ethernet to the main router itself. Then test Wi-Fi in the same room while temporarily unplugging any extenders or satellites so the device cannot remain attached to a distant access point. Phones and laptops sometimes cling to a weaker node longer than expected, so simply walking closer to the router may not switch the connection.
If the direct wired result is close to your paid tier but the mesh or extender path stays around 73 Mbps, the ISP is not the bottleneck. At that point, moving the satellite, using wired Ethernet for its backhaul, or replacing a single-band repeater would make more sense than upgrading the internet plan.
A wired test that reads 73 on a gigabit plan and a wired test that swings between 400 and 900 tell you completely different stories, and that’s the split I’d nail down first. A rock-steady number means something is capping you, exactly like @thread.vim said about the plateau, while numbers that bounce around usually just mean congestion or Wi-Fi noise.
Whether 73 Mbps is a per-device ceiling or the home’s total ceiling changes the diagnosis. Run tests on two capable devices at the same time and compare the combined result. If both manage roughly 70 Mbps, your service is delivering more than the original test showed and that device or Wi-Fi link is the limit. If they split roughly 73 Mbps between them, the bottleneck is probably at the router, modem, or ISP provisioning.