Measure the download speed, upload speed, latency and jitter of the connection you are using right now. The test transfers real data to a server on Cloudflare's network and reports how much it used, so nothing on this page is estimated or simulated.
The whole run takes about twenty seconds. It downloads and uploads real data, so on a metered mobile plan it will use part of your allowance; the exact amount transferred is shown with the result.
An internet speed test measures how fast data moves between your device and a server: download is how quickly data arrives, upload how quickly it leaves, latency the delay before anything happens, and jitter how much that delay wobbles. This page measures all four with real transfers to a server on Cloudflare's network, in megabits per second, the decimal unit providers advertise.
About this tool
What does this tool do?
It runs three separate measurements. First it sends a series of tiny requests and times each round trip, which gives latency and jitter. Then it downloads several megabytes and times the transfer, which gives download speed. Then it uploads several megabytes and times that, which gives upload speed. The size of each transfer adapts to how fast your connection turns out to be, so a slow link is not made to move forty megabytes, and the total amount of data used is reported with the result.
Every number comes from data that actually moved. Nothing is inferred from anything else, and if part of the test cannot run, that part is left blank rather than filled in with a guess.
Why is this useful?
Because the speed on your bill is the speed to your building, not the speed at your desk. Old Wi-Fi hardware, distance from the router, a congested evening, a neighbour on the same cable segment or a VPN can all take a large bite out of it. Measuring from the device you are actually using tells you what the applications on that device have to work with, and comparing a Wi-Fi result against a cabled one usually settles the question of whether the problem is your connection or your network.
Who uses this tool?
• People checking a new connection: confirm you are getting roughly what you are paying for after an installation or an upgrade.
• Anyone whose video calls break up: latency and jitter matter far more than raw speed for calls, and this shows both.
• Remote workers: check upload speed, which is what carries your camera and your file transfers, and which is usually much lower than download.
• People diagnosing Wi-Fi: run the test beside the router and again in the far room to see what the walls cost you.
• Gamers and streamers: a stable, low-jitter connection matters more than a big number.
How to use this tool
1. Close other downloads, streams and backups first, otherwise you are measuring what is left over rather than what you have.
2. Press Start test and leave the tab in the foreground until it finishes.
3. Watch the dial and the status line. The dial fills while a transfer is still running and shows the average of everything measured up to that instant, so on a slow connection you can see the run progressing instead of a line that sits unchanged for a minute. The status line names the stage and the megabytes used.
4. Press Stop at any point to abandon the run. It cancels the transfer in progress rather than just hiding it.
5. Run it two or three times, a minute apart, and use the best result. A single run can be spoiled by a moment of congestion.
Example: the same line measured twice
A home fibre connection sold as "40 Mbit/s" returns 38.6 Mbit/s down and 21.4 Mbit/s up, with a median latency of 34 ms, jitter of 3 ms and a first connection of 210 ms, having moved 22 MB. That is a healthy result: download within a few percent of the advertised figure, and jitter small enough for video calls.
The same line measured from a laptop two rooms away on 2.4 GHz Wi-Fi returns 14.2 Mbit/s down, while latency and jitter barely change. Latency staying put is the clue: the connection to the internet is fine and the Wi-Fi hop is the bottleneck, so no amount of arguing with the provider will improve that number.
What is being measured
The result describes the whole path, not just the line you pay for. That is why a poor Wi-Fi hop caps the number while latency stays normal, and why a wired run is the fairest test of the connection itself.
Understanding your results
Download speed
Bytes arriving divided by the time they took, in megabits per second. Timing starts when the first byte lands, so the delay before the transfer begins is left out of the throughput figure and reported as latency instead.
Upload speed
The same measurement in the other direction, timed from the first byte leaving your device until the server confirms it has received the lot. On most home connections it is far lower than download, which is a deliberate choice by the provider rather than a fault.
Latency
Ten tiny requests are sent and every round trip is timed. All ten count, because the connection to the test server was already open before the first of them left — it was opened while the page was finding a server that answers — so none of the ten carries the setup cost. The figure is the median of the requests that came back, with the fastest of those beside it, and if fewer than ten answered the row says how many did. The median is used rather than the average so one delayed sample cannot distort it. Under roughly 50 ms feels immediate; above 150 ms is noticeable on a call.
Jitter
The average change from one round trip to the next. Low jitter matters more than raw speed for calls and games, because audio and video need packets arriving at a steady rate, not merely arriving quickly. It needs two answered requests before it means anything, so when only one came back the row says it was not measured instead of showing zero.
First connection
The very first request of the run — the one that goes looking for a test server — timed on its own. It carries the DNS lookup and the TCP and TLS handshakes, which is why it is normally much slower than the latency figure and says very little about the speed of the connection itself. When the address that finally answers is not the first one tried on that host, the connection was already open by the time the working path was found, and the row says the setup cost was not isolated rather than passing a warm round trip off as a cold one. On a run started moments after the last one, the browser may still be holding that connection open, so the figure can read much like latency.
Data transferred
How many megabytes the run actually used, download and upload together. Worth reading before you repeat the test on a metered mobile plan.
Test server, Tested from, and Cloudflare location
Test server names the host that actually answered, since more than one is tried. Tested from is your network's name and approximate location, read from the first-party endpoint at ip.myipshow.com, falling back to the test server's own response headers and reading "Not available" if neither can name it. Cloudflare location is the edge site that served the transfer, taken from the response headers when they can be read. None of the three changes the measurement; they record where it was taken.
What this tool cannot tell you
• It is not your line's maximum. Wi-Fi, an older device, browser overhead and anything else using the connection at the time all cap the figure.
• One server, one network. The same connection tested against a server in another country, or on another provider, can return a different number.
• No packet loss. A browser cannot see individual packets, so the old packet loss reading has been removed rather than estimated from something else.
• Upload is measured conservatively. The clock runs until the server confirms it has the data, so one round trip is included and a very fast link can read a little low. It is also why the dial holds still during an upload while the megabyte count keeps climbing: the browser can say how many bytes it has handed to the connection, but that runs ahead of what has crossed the network, and no figure goes on the dial that the result would not stand behind.
• It cannot say where a bottleneck is. The whole path arrives as one number; comparing a Wi-Fi run with a cabled one is how you narrow it down.
Common use cases
Checking a new connection
Run it wired, or as close to the router as you can, and compare the download figure with what you were sold.
Calls that break up
Read latency and jitter before download speed. Unstable delay ruins a call that plenty of bandwidth cannot save.
Working from home
Upload carries your camera and your file transfers, and it is the number most home plans are thinnest on.
Mapping Wi-Fi dead spots
Test in each room. Where speed collapses but latency holds steady, the Wi-Fi is at fault, not the line.
Planning a big transfer
A 2 GB upload over a 20 Mbit/s link takes about thirteen minutes. Knowing the number sets the expectation.
Before calling support
Two or three timestamped results, taken at different times of day, make the conversation much shorter.
Technical details
Speeds are quoted in megabits per second, decimal, so 1 Mbit/s is one million bits. A file size in megabytes is eight times larger than the same figure in megabits, which is why a 25 Mbit/s connection downloads at roughly 3 MB per second. For reference, the United States raised its fixed broadband benchmark to 100 Mbit/s down and 20 Mbit/s up in 2024, and Netflix asks for 15 Mbit/s for a single 4K stream.
| What you are doing | Download needed | Also matters |
|---|---|---|
| Browsing, email, messaging | 1 to 5 Mbit/s | Latency, for pages that feel snappy |
| Standard definition video | 3 Mbit/s | Steady speed rather than a high peak |
| HD video, one stream | 5 Mbit/s | Add for each extra viewer |
| 4K video, one stream | 15 Mbit/s | Sustained speed for the whole film |
| HD video call | 3 to 4 Mbit/s | Upload and jitter, far more than download |
| Online gaming | 3 to 6 Mbit/s | Latency and jitter decide the experience |
| Sending large files or backups | Download is irrelevant | Upload speed, and only upload speed |
When speed is not the problem
A connection can be fast and still feel broken. If pages hesitate before loading, or a call stutters while a download runs happily in the background, the number to look at is delay rather than throughput. The ping tool measures response time against any host you name, which is more useful than a single figure against one server. A VPN is the other common culprit, since it adds a detour and its own encryption overhead to every packet: the VPN checker will tell you whether your traffic is going through one.
About the data
The transfers go to MyIPShow's own test server at speed.myipshow.com, a Cloudflare Worker, so the machine you measure against is normally the Cloudflare location nearest you. If that name cannot be reached the page tries the same Worker's workers.dev address, and then Cloudflare's own public speed test endpoint, so a result is still possible while the Worker is down. The result names whichever host answered. The network name shown with the result comes from the first-party endpoint at ip.myipshow.com, or from the test server's own response headers when that is unavailable. No result is stored on a server: the recent results list lives in your own browser and the Clear button deletes it.
Related tools
Frequently asked questions
Why is my speed lower than what I pay for?+
The figure you pay for is the speed to your building under ideal conditions, and it is usually described as up to that number. Wi-Fi, the age of your device, other people in the house and the busy evening hours all take a share. A result within about ten percent of the advertised speed on a wired connection is normally considered healthy.
Why is upload so much slower than download?+
Because most home connections are designed that way. Cable and DSL technologies divide the available capacity unevenly on the assumption that people consume far more than they send, so an upload speed of a tenth of the download is common. Full fibre connections are the exception and are often symmetric.
What counts as good latency and jitter?+
Under 50 ms of latency feels immediate for browsing and is comfortable for calls and most games. Between 50 and 150 ms is usable but noticeable, and above 150 ms conversations start to overlap. Jitter under about 10 ms is good, and jitter above 30 ms is the usual reason a call breaks up even though the speed test looks fine.
How much data does this test use?+
It depends on how fast your connection turns out to be, because the transfer sizes adapt: a slow link is measured with a few megabytes, a fast one with more. The exact total is reported with the result so you can see what it cost, which is worth checking before repeating the test on a metered mobile plan.
Does a VPN slow the test down?+
Almost always, yes. Your traffic takes a detour to the VPN server before it reaches anything else, and it is encrypted and decrypted on the way, which adds latency and usually costs some throughput. If you want to know your line speed, test with the VPN switched off, then switch it on and compare.
Why do two runs give different numbers?+
Because a network is shared and conditions change from second to second. Another device starting a download, a neighbour on the same cable segment, or ordinary congestion between networks will all move the result. Run the test two or three times a minute apart and treat the best figure as the closest to your real capacity.
Why does this tool not show packet loss?+
Because a web page cannot see packets. Browsers expose requests and responses, not the individual packets underneath them, and the operating system quietly retransmits anything lost before the browser ever finds out. Any packet loss percentage produced in a browser is an invention, so this page reports what it can actually measure instead.
Should I test over Wi-Fi or a cable?+
Use a cable to judge the connection itself, since it removes the most common bottleneck from the measurement. Use Wi-Fi when the question is what a particular room or device actually gets. Running both is the fastest way to find out whether to fix your network or complain to your provider.
Which server does the test measure against?+
A server on Cloudflare's global network, so the machine at the other end is normally the Cloudflare location nearest you rather than one in another country. The page tries MyIPShow's own endpoint first and falls back to Cloudflare's public speed test endpoint if that one cannot be reached, and the result names whichever host answered. If neither responds, the test says so plainly instead of showing a number, which usually means an ad blocker, a privacy extension or a firewall is blocking the requests.