Internet Speed Test

Measures real internet download and upload speed, latency (ping), and jitter against a remote server using the Measurement Lab (M-Lab) ndt7 protocol.

iPhoneiPadMacApple Vision ProApple TVApple Watch

Overview

Internet Speed Test runs a genuine network measurement against a public Measurement Lab (M-Lab) server — it is not an estimate from local transfer counters like Connection Rate. M-Lab is an open, third-party research platform; Lirum uses its ndt7 test, which performs a multi-stage measurement: locate the nearest server, probe latency, then run a real download and upload over the connection.

The first time you run a test, Lirum shows a short consent screen because the measurement sends some data to M-Lab (see Privacy & Consent below).

Table Of Contents

• Overview
• Running A Test
• Phases
• Results Screen
• Latency Profile
• Connection Suitability
• Connection Details
• History
• Privacy & Consent
• Notes And Limitations

Running A Test

Tap GO on the idle screen. The tool then:

1. Locates the nearest M-Lab server.
2. Probes latency (ping/jitter).
3. Runs the download measurement.
4. Runs the upload measurement.
5. Shows the results screen.

You can cancel a running test by leaving the screen; the in-flight task is cancelled.

Phases

While the test runs, the screen shows the current phase and a live speed dial:

• READY — idle, before the test starts.
• LATENCY — probing the server and measuring round-trip time.
• DOWNLOAD — pulling data from the server; the dial reflects live download throughput.
• UPLOAD — pushing data to the server; the dial reflects live upload throughput.
• COMPLETED — finished, showing the results screen.

During download/upload, the running screen shows the live speed on the dial, a throughput bar history, an area chart of speed over time, and a compact stat strip (Download / Upload / Ping / Jitter) that fills in as each phase completes.

Results Screen

After the test completes, the results screen shows:

• A hero card with a letter grade and rating based on the download speed.
• Primary metrics: Download and Upload in Mbps (with an MB/s conversion underneath).
• A latency profile card.
• A connection suitability card.
• A connection details card.
• Run Again and Share actions.

Latency Profile

The latency card reports:

• Ping — round-trip time in milliseconds (ms).
• Jitter — variation in latency, in ms.
• Loss — not reported by ndt7; shown as 0 / not available.

A latency distribution readout summarizes the sampled ping values.

Connection Suitability

The suitability card checks your measured speeds against common use cases (for example streaming, video calls, large uploads) and marks each as PASS or FAIL. Tap the card to open a detail view that explains what your connection supports — and where it hits its limits.

Connection Details

The connection card shows metadata captured during the test:

• ISP and IP (as reported by the M-Lab server).
• Server — the M-Lab server location and host.
• Link — the active network interface (for example Wi-Fi or Cellular).
• Protocol — the transport used (for example wss · TCP BBR).

History

Each completed run is saved to a local history list. Tap the history button (top-right) to review past runs, each with its download/upload/ping/jitter values, timestamp, and server. History is stored on-device.

Privacy & Consent

Because the test exchanges data with M-Lab's public servers, the first run shows a consent screen. M-Lab publishes measured results (including your public IP address, the timestamp, and the speed/latency results) under a CC0 public-domain dedication so researchers can study internet health. No personal information (name, email, or precise location) is collected or transmitted by the test itself.

Your consent choice is remembered for future runs.

Notes And Limitations

• The test measures your real internet path to an M-Lab server, so results depend on your ISP, Wi-Fi/cellular conditions, distance to the server, and network load at the time.
• This is distinct from Connection Rate (which reports live device-level transfer counters) and from Throughput (which measures peer-to-peer speed between two devices on the same network).
• ndt7 does not report packet loss directly; the loss figure is best-effort.
• The test requires an active internet connection and, on first run, consent to share measurement data with M-Lab.
• Running the test consumes real data — avoid it on a metered connection if you are sensitive to data usage.