Measure download, upload, latency and jitter between your browser and our server in India
Times random test data to and from our server in India. Nothing you type is sent, and nothing is stored. Checked against sources on 21 Nov 2026.Checked against the tool’s code on 18 November 2026. Figures read from their sources on 21 November 2026. What we collect
An internet speed test times how fast data moves between your device and a server. This page downloads random test data from our server in India, uploads test data back, and times 10 tiny round trips, then shows download and upload in Mbps and latency and jitter in milliseconds. It measures that path, not the speed your provider advertises.
| Use | Download | Upload |
|---|---|---|
| HD video (720p) | 3 Mbps | - |
| Full HD video (1080p) | 5 Mbps | - |
| 4K video | 15 Mbps | - |
| Group HD video calls (720p) | 1.8 Mbps | 2.6 Mbps |
This tool sends random test data to our server in India and downloads random test data from it, to time your connection; nothing you type is sent, and nothing is stored. Which tools call a server
Close other downloads and video on the same connection, then press Start test.
Wait about 17 seconds while it measures latency, then download, then upload.
Read download and upload in Mbps and latency and jitter in milliseconds.
Press Copy result to paste the figures into a support ticket, or Run again on another device or Wi-Fi band.
Press Start test and the page does three things in turn. It times ten tiny round trips to our server and reports the lowest, the median and the jitter, dropping the first because it includes opening the connection. It then downloads random bytes for about eight seconds over three requests at once, growing each request so it takes about a second and a half. Finally it uploads random bytes for about six seconds in pieces of at most a million bytes, which our server counts and throws away.
The first second of each phase is not counted: a new connection starts slowly (TCP slow start), and counting it would make every line read low. This follows RFC 6349, the method framework for TCP throughput testing, and the notes of M-Lab's NDT test.
The result is the speed between your browser and one server, ours, in India. A faraway server, a busy Wi-Fi channel, other devices downloading, a VPN or an old router all lower it, so it can be well below the plan your provider sells, which is the speed to their own network. Run it twice, close to the router and further away, to see where the slowdown sits.
Only test data made up by the page goes up; nothing you type, no file. Nothing is stored except the anonymous count that a test was run, and every reply is marked so no cache keeps it.
Press Start test on this page. It measures latency first, then download for about eight seconds and upload for about six, and shows the figures in Mbps and milliseconds. Close other downloads and video on the same connection first, or they share the line and the result reads low.
A provider sells the speed to its own network. This test measures the whole path from your browser to our server in India, including your Wi-Fi, your router, other devices on the line and the route between networks. Wi-Fi far from the router, a VPN or a busy evening hour often account for most of the gap.
A good speed depends on use. Netflix recommends 3 Mbps per stream for HD, 5 Mbps for Full HD and 15 Mbps for 4K. Zoom lists 1.8 Mbps down and 2.6 Mbps up for 720p group video calls. A household adds those up for everything used at the same time.
Ping, or latency, is how long a tiny message takes to reach a server and come back, in milliseconds. Jitter is how much that time changes from one message to the next. Both matter more than raw speed for games and video calls; low and steady is what you want.
No. The upload sends random test data made up by the page, in pieces of at most a million bytes, and our server counts and discards each piece. Nothing you type or own is sent, and nothing is stored except the anonymous count that a test was run.
Other traffic on your network and on the route changes from second to second, and Wi-Fi signal varies as you move. Run the test two or three times and read the typical figure. Testing over a cable next to the router shows what the line itself delivers.
Rates and rules change; check the source before you rely on a figure.
Still stuck? Ask about Internet Speed Test and anybody who knows can answer. No account needed.
Same job, other tools: Link Preview Checker – Find the missing tag behind a WhatsApp or Slack link with no picture · Readability Checker – Flesch reading ease and grade level, with what to change · User-Agent String Checker – Check what a user-agent string can and cannot tell you before you rely on it.
On the related tools: JSONPath Evaluator – Evaluate a JSONPath expression and get the matching values and their paths.
On the same topic: What Is My IP Address – See the public IP address websites see for your connection, IPv4 or IPv6, and copy it · Ping Test – Ping a host or IP from our server: 4 replies with min, average and max time · WebRTC Leak Test – See which IP addresses WebRTC hands to websites, and whether your VPN is being bypassed.