Internet Speed Test
Measure the real download throughput of a static file from this site. The bytes and the elapsed time are shown.
What this speed test measures
It downloads one real static file that this site serves — the browser converter catalogue, a little over a megabyte — with the browser cache bypassed, times the transfer with the page's own high-resolution clock, and reports the bytes read divided by the elapsed time. That is a measured throughput for this path at that moment, not an estimate, not a score from a third-party network, and not a claim about the capacity of your connection.
How to use it
Press Run the speed test and wait for the card on the right, which reports Mbit/s, MB/s, the byte count, the total elapsed time and how long the server took to start answering.
Worked example
One run read 1,129,431 bytes in 612 ms, which is 1.13 MB in 0.612 s: the page reported 1.84 MB/s, or 14.76 Mbit/s, and a server response time of 41 ms.
Why it runs in your browser
The request is made by this page and the arithmetic happens in this tab, so the measurement describes your path from this site rather than a number a remote service computed for you. Nothing is uploaded and the page keeps working after it loads, though a measurement needs the connection by definition.
Press the button and this page downloads one real static file this site serves, bypassing the browser cache, then divides the decoded bytes by the elapsed time to report a speed in megabits and megabytes per second.
It also shows the byte count, the elapsed time and the time to first byte, which separates a slow server response from a slow transfer. A failed download shows the failure and no speed rather than a zero.
This is one path at one moment, not a capacity test of your connection and not a comparison with a third-party speed-test service. A busy server, a throttled tab or a proxy can all move the number.
What is measured
The file is the browser converter catalogue, fetched with the cache disabled and a timestamp in the query so no stored copy can answer. The clock starts before the request and stops after the body has been read.
The reported bytes are the decoded response body. The server may send it compressed, so the figure describes what arrived ready to use rather than the exact bytes on the wire.
- One download of a static asset this site serves
- Speed in Mbit/s and MB/s, from bytes divided by elapsed seconds
- Bytes, elapsed time and time to first byte, shown separately
What the figure cannot tell you
A single small download is dominated by connection setup and server response time, so the speed it reports is often lower than a sustained transfer would achieve. Repeating the test and watching the spread is more informative than one number.
It says nothing about upload speed, latency under load, packet loss or your connection's capacity as measured by a provider. Those need a different test with a different server.
How to use the run button
Press Run the speed test in the Run the measurement panel. The test downloads one real static file this site serves, the browser converter catalogue, with the cache bypassed and a timestamp in the query, then divides the decoded bytes by the elapsed time and reports megabits and megabytes per second in the Measured panel.
Read the supporting figures with the headline: Bytes read, Elapsed, Server response as time to first byte, and the asset name. A single small download is dominated by setup and response time, so the figure often reads lower than a sustained transfer; it says nothing about upload, latency under load, or provider capacity.
What to Expect
Best for
- Checking that a connection can reach this site and transfer a real file
- Separating a slow first byte from a slow body transfer
- Comparing two networks on the same file at the same time
Not ideal for
- A verdict on the speed you pay your provider for
- Upload measurements, which the page does not perform
- Comparing against a third-party speed test, which uses different servers
What this tool keeps
- A real measurement, with no number shown when the download fails
- The cache bypassed, so a repeat run measures a fresh transfer
- Bytes, elapsed time and first-byte time reported beside the speed
What may need cleanup
- A figure skewed by a proxy or a busy server
- The megabyte figure, which counts decoded bytes rather than wire bytes
- One run's result, which is a sample rather than an average
Common errors
- Reading the result as your connection's maximum capacity
- Comparing it with a provider's headline figure
- Expecting an upload result from a download-only test
Example use cases
- Confirming a network can fetch this site's assets
- Showing the difference between TTFB and transfer time
- A quick check before reporting a slow page
Sample input
Press Run the speed test once on a home connection and read the four measured rows.
Sample output
About 2.1 MB read in 0.34 seconds, reported as roughly 49 Mbit/s and 6.2 MB/s with a first-byte time of 41 ms.
Who this is for
- Users diagnosing a slow page load
- Support staff checking connectivity to this site
- Teachers demonstrating the difference between latency and throughput
Frequently asked questions
What does the speed test measure?
One real static file this site serves, downloaded with the browser cache bypassed, then decoded bytes divided by elapsed time in megabits and megabytes per second.
Does it measure upload speed?
No. It performs a download measurement only.
Is one run a verdict on my connection?
No. A proxy, a busy server or a single sample can skew the figure, so treat one run as a sample rather than an average.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.