Network 8 min read 1,748 words By LaiUse Editorial Team Reviewed 28 October 2026

Speed Test — Complete Guide

Speed Test measures the connection between your browser and this site's backend three ways: round-trip latency, download throughput and upload throughput.

What it does

This tool measures the connection between your browser and this site's backend three ways: round-trip latency, download throughput and upload throughput. It measures three separate characteristics of the connection between the browser and the tool’s backend: download speed, ping, and upload speed. The implementation calls dedicated backend endpoints for each part of the test: /api/speed-test/download?size=${size} for the download measurement, /api/speed-test/ping for the ping measurement, and /api/speed-test/upload for the upload measurement. The returned measurements are then presented in the browser.

The tool is not a fully client-side utility. Although it uses plain browser APIs and no third-party library, it does not process the test entirely in the browser: all three measurements require communication with a backend. Its local-processing capability therefore means that the interface and test orchestration happen in the browser; it does not mean that network traffic stays on the device. The tool has no file input and no drag-and-drop target. It does not upload a user-selected file, and any text it handles is supplied by pasting or typing rather than by opening a file. The output does not update automatically as text is entered: a control must be pressed to run the test.

When to use it

How to use it

  1. Open the speed-test page. Do not expect a file picker or a drag-and-drop area. The tool has no file input; text, if required, is pasted or typed into the page.
  2. Activate the control that starts a test. The published tool does not provide a visible label for this control, so there is no exact button wording to quote. The test is not automatic and does not begin merely because text is entered.
  3. Let the download phase run. The browser requests /api/speed-test/download?size=${size}. The size value is sent as part of the request, and the published size limits are 5 MB and 50 MB. The tool does not explain how those limits map to individual controls, so it does not establish that either value can be selected through a visible format or size menu.
  4. Let the ping phase run. The browser calls /api/speed-test/ping. This phase measures latency rather than transferring data at a sustained rate.
  5. Let the upload phase run. The browser calls /api/speed-test/upload. The tool has no user-selected file to send; the upload test is a request to the backend, not the upload of a document chosen from the device.
  6. Wait for all three phases to finish. Read the reported download speed, ping, and upload speed. The tool does not publish the display units, decimal precision, or exact result labels, so those details cannot be stated more specifically.
  7. Download the file if you need to retain the output. The tool has a file-download capability, but it does not state the generated file’s format, name, or structure. Use another tool if you require a prescribed report format such as a particular spreadsheet or image format.

Worked example

Suppose the goal is to assess an office connection before copying several large files to a remote server. Start a new test by activating the page’s speed-test control. The browser first requests the download endpoint. For a successful run, the request uses a size value within the published 5 MB and 50 MB constraints; for example, the request can carry size=5 when the tool is configured to use the smaller published size. The server responds with the data needed to calculate the download rate, and the page records that rate as the download-speed measurement.

Next, the browser contacts /api/speed-test/ping. The expected result is a ping measurement representing the responsiveness observed for that request. The browser then calls /api/speed-test/upload, and the page records an upload-speed measurement from that phase. A successful completed run therefore produces three distinct results: a download speed, a ping result, and an upload speed. The tool does not state their units, so a reader should use the units displayed by the page rather than assume that a value is expressed in a particular scale.

The expected output is not a list of user-supplied files or a transformation of pasted text. It is a network-test report. If the user needs to keep a record, the file-download capability can save the generated output, but its exact format is not documented in the tool. If the download phase cannot be completed, the corresponding visible error is “Failed to measure download speed” rather than a partial or estimated download figure.

Limitations and edge cases

Troubleshooting

Frequently asked questions

Does the test run entirely in my browser? No. The interface uses browser APIs, but it calls a backend for download, ping, and upload measurements. The network test necessarily depends on communication with that service.

Does the tool upload one of my files? No. It has no file input and no drag-and-drop support. The upload measurement uses the tool’s upload endpoint and is not an upload of a user-selected document.

Can I paste or type text instead of choosing a file? Yes. The tool’s file-upload capability is absent, and text handling is based on pasted or typed content. However, the speed measurement itself comes from the backend requests described above.

Is the result private because local processing is supported? Not in the sense of avoiding backend communication. The tool processes parts of its workflow in the browser, but the measurements require calls to backend endpoints. The tool does not state a retention policy or make a claim that test traffic never leaves the device.

What size limits apply? The only published limits are 5 MB and 50 MB. The tool does not clarify their exact mapping to the interface, so it would be unsafe to claim that a specific button, dropdown, or option selects either value.

Can I copy the measurements to the clipboard? No. Copy-to-clipboard is not a supported capability. Use the available file-download feature if you need to retain the output, or record the visible values manually.

Does the result update automatically while I work? No. The output does not update live as text is entered, and the test is not automatic. A control must be pressed to begin measurement.

Will the tool remember my last result? No. It does not use local storage and does not remember state between visits. A new visit requires a new test.

When is a different tool better? Use another application for testing a specific local file, transferring a file, copying results, maintaining measurement history, using controlled or securely generated test payloads, or exporting a report in a precisely specified file format.

Want to try it? Open the Speed Test — it runs in your browser, so your files stay on your device.

Browse every guide · Read the blog · About LaiUse