Measure download speed, upload speed, ping and jitter from your browser to GearCheck Lab's nearest available edge test node. The test is designed for practical troubleshooting: finding slow Wi‑Fi, unstable gaming latency, poor video-call performance or a connection that does not appear to match expectations.
A useful speed test needs more than one quick file transfer. Short tests can be dominated by connection setup, server start-up, congestion control or a single slow request. GearCheck Lab therefore warms the test path first, then measures the connection over a longer window using adaptive payload sizes and multiple parallel transfers. The goal is to estimate the usable browser-to-edge throughput rather than report a momentary burst.
The test sends several small requests after a warm-up period. It uses a trimmed median for the displayed ping so one unusually slow response does not dominate the result. Jitter is based on the typical change between consecutive latency samples. Lower values normally indicate a more consistent path.
A short probe helps choose an appropriate transfer size and number of parallel streams. The measured stage then runs for several seconds. Download is calculated from bytes received over elapsed time; upload is calculated from temporary generated bytes successfully received by the test endpoint.
Because this is a browser test, the result includes the performance of your device, browser, local network and route to the selected edge location. It is not a laboratory certification of your ISP plan. Read our broader testing methodology for how GearCheck Lab treats browser-visible measurements and limitations.
No single number decides whether a connection is "good." Download and upload describe throughput, while ping and jitter describe responsiveness and consistency. A connection can have high Mbps but still feel poor in games or calls when latency is unstable. The ranges below are practical reference points, not guarantees for every service.
| Metric | Strong result | Usable / typical | When to investigate |
|---|---|---|---|
| Download | 25+ Mbps for one or a few users | 10–25 Mbps for general use | Below about 5–10 Mbps if normal browsing or HD streaming struggles |
| Upload | 8+ Mbps for calls and cloud use | 3–8 Mbps for many everyday tasks | Below about 3 Mbps if calls, uploads or backups are unreliable |
| Ping | Under 40 ms | 40–80 ms | Above 80–100 ms when interactive apps feel delayed |
| Jitter | Under 10 ms | 10–25 ms | Above 25–30 ms when calls or games feel inconsistent |
For household internet, also consider how many devices are active at once. A 25 Mbps line may be comfortable for one person but constrained when several televisions, laptops, phones, game consoles and cloud backups share the same connection.
Web pages, email and documents use relatively little sustained bandwidth. Around 10 Mbps can feel responsive for one user when latency is reasonable, but large software downloads and cloud syncing will take longer.
HD streaming commonly needs several Mbps per stream, while 4K uses considerably more. Video calls depend on upload as well as download. Stable latency and low jitter are often more important than having extremely high headline speed.
Most games do not require huge Mbps once connected. Ping, jitter and packet stability matter more. A fast download result cannot compensate for a long or unstable route to the actual game server.
A 500 Mbps plan on congested Wi‑Fi can feel worse than a slower wired connection for a call or game. When diagnosing an experience problem, match the symptom to the metric: slow file transfer points toward throughput; delayed actions point toward latency; stuttering or uneven response can point toward jitter, interference or congestion.
Run two or three tests rather than trusting one result. A repeated pattern is more useful than an isolated low score caused by temporary congestion or a background task.
Stop large downloads, cloud backup, game updates and high-resolution streaming. These compete for the same bandwidth and can increase latency under load.
If the result improves dramatically near the router, the internet service may be fine and the problem is more likely Wi‑Fi coverage, interference or router placement.
A wired test removes much of the uncertainty introduced by wireless signal strength and congestion. A good Ethernet result with poor Wi‑Fi is strong evidence that the local wireless network needs attention.
If only one laptop or phone is slow, investigate that device, its wireless adapter, browser extensions, power-saving settings or background software before blaming the connection.
If speed drops mainly in the evening, repeated peak-time congestion may be involved. Keep a few results with date and time if you need to discuss a recurring problem with your provider.
Router placement matters. Keep it away from thick walls, metal cabinets and other electronics where possible. Higher-frequency Wi-Fi bands can deliver more speed at short range but generally lose strength faster through walls; 2.4 GHz often reaches farther but may be more congested.
It is normal for two reputable speed tests to disagree. They may be measuring different routes rather than making the same measurement badly. The selected server can be in another city or network, one service may use many parallel connections while another uses fewer, and test duration can affect whether the connection has time to reach full throughput.
Your packets do not travel through the internet in a straight line. Peering arrangements and routing can make one nearby-looking server faster than another. GearCheck Lab reports the browser-to-GearCheck Lab edge path; another test may use a different network entirely.
CPU load, battery-saving modes, browser tabs, security software, VPNs and extensions can affect browser-based tests. Wi-Fi conditions can also change in seconds as other devices transmit.
For comparison, run tests close together under the same conditions and look for the broad pattern rather than expecting identical decimals. Large repeatable differences deserve investigation; small differences are expected.
The upload phase sends temporary generated test bytes, not documents, photos or other personal files from your device. Download test payloads are temporary measurement data. GearCheck Lab does not need access to your local files to run the test.
As with normal web requests, hosting and network infrastructure may process standard request information needed to deliver the service. See the privacy policy for site-level information.
This result does not certify the maximum capacity of your ISP line, diagnose packet loss at every hop, measure the latency to a specific game server, or guarantee performance in another app. Browser scheduling, device performance, Wi-Fi, VPNs, network congestion and the route to the edge node can all influence the result.
A fair test is best run with unnecessary traffic paused, from a device that is not heavily loaded, and repeated more than once. If you are checking whether your ISP delivers an expected service tier, compare a wired result as well as Wi-Fi and follow the provider's own testing requirements.
Different services can use different servers, networks, routes, transfer sizes, durations and parallel connection counts. Your local conditions may also change between runs. Compare repeated tests under similar conditions rather than expecting identical results.
Lower is generally better. Under roughly 40 ms is often comfortable, 40–80 ms can still be playable, and higher values are more likely to feel delayed. The actual game server may have a different ping from this test, and low jitter matters too.
Jitter describes how much latency changes from sample to sample. Consistent 30 ms latency can feel smoother than latency that rapidly swings between 15 ms and 100 ms. Voice, video and real-time games are particularly sensitive to inconsistent timing.
Use both when possible. Ethernet is useful for checking the connection available from the router or modem without normal Wi-Fi interference. Wi-Fi then shows the real experience on the wireless network where you actually use the device.
No. It creates temporary test bytes for the measurement. The browser does not select a personal file from your device.
Yes. VPN traffic travels through the VPN provider and is encrypted. Server distance, congestion and the extra route can reduce throughput or raise latency. Compare with and without the VPN if you are trying to isolate the underlying connection.
Your plan describes the service connection, while Wi-Fi is another link between your device and router. Distance, walls, interference, router capability and the device's own radio can all reduce the speed that reaches one device.
Two or three runs are a sensible minimum for troubleshooting. If the problem is intermittent, repeat tests at different times and keep notes about location, connection type and what else was using the network.
If your connection looks healthy but a particular activity still feels wrong, test the hardware involved in that activity as well.
Last reviewed: 14 September 2026. Measurement methodology and interpretation are updated when the test engine changes.