How to Run a Repeatable Internet Speed Test
A speed-test result describes one device’s connection to one test service at a particular time. A repeatable setup helps you compare results, but a browser test cannot isolate every cause of slow service or replace your provider’s full network measurements.
What the three main results mean
Download speed is how quickly data reaches your device; upload speed is how quickly it leaves your device. Both are shown in megabits per second (Mbps). A megabyte contains eight megabits, so a file’s transfer rate in MB/s is not numerically the same as a speed-test result in Mbps.
Ping is a round-trip time measurement in milliseconds (ms): lower values generally mean a faster response for interactive tasks, but one ping number does not describe all network behavior. This tool reports a sample of ping, download, and upload performance. It does not measure every factor a detailed broadband study might examine, such as packet loss or performance under load.
Set up a fair comparison
- Choose a stable location: For a wired test, connect the device to the router with Ethernet. For Wi-Fi, test near the router and note that walls, distance, interference, and the device’s radio can affect the result.
- Reduce competing traffic: Pause large downloads, cloud backups, video streams, and other speed tests on the same connection. Keep other household activity similar when comparing two results.
- Run several tests: Repeat the test two or three times, leave a short gap, and record the time, connection type, and result. If the question is about evening slowdowns, test at the time they normally occur as well as at a quieter time.
- Compare like with like: Use the same device, room, connection type, and test service. If you change from Wi-Fi to Ethernet or move to another room, treat that as a separate comparison.
Interpret the result without overclaiming
The browser exchanges sample requests with TheCodePlaza’s speed-test service. The result therefore includes the device, local network, internet route, and test service involved at that moment. A low result can come from any point in that path; it does not identify the provider as the cause by itself. A high result also does not guarantee that every app, game, or website will feel fast.
Compare results with the service details your provider advertises, but remember that plans and test methods differ. The FCC’s consumer guide defines download and upload in the same basic directions and explains why upload and latency can matter in addition to download speed. The FCC’s published broadband-measurement methodology describes a broader set of tests than this short browser test.
Common reasons two tests disagree
- One test used Wi-Fi and another used Ethernet, or the device was in a different room.
- Other devices started streaming, backing up files, or downloading during one run.
- The time of day or the route to the test service changed.
- Different speed-test services use different servers, methods, and sample sizes.
Common questions
Why is my speed-test result lower than the number on my plan?
The test measures one device and connection path at a moment in time. Wi-Fi, household traffic, device limits, service conditions, and the test service can all affect it; repeat under consistent conditions before drawing a conclusion.
Does a speed test measure packet loss or Wi-Fi coverage?
This tool reports ping, download, and upload samples. It is not a full wireless survey and does not report every metric used in more comprehensive broadband measurements.
Sources and further reading
- FCC: Broadband Service for the Home — A Consumer’s Guide — Defines download and upload speed and discusses latency as another service consideration.
- FCC: Measuring Broadband America Open Methodology — Historical FCC methodology describing web browsing, packet loss, latency, and other metrics; it is not the same as this browser test.