Interactive diagnostic

Network stability & speed test

Measure the connection between this browser and DeviceTriage using generated data and clearly labeled HTTP-based metrics.

Processed locally in this browser

Controlled connection measurement

Measure response stability and transfer speed

The test exchanges a small amount of generated data with DeviceTriage. It measures this route—not your maximum ISP package speed—and sends no files or personal content.

Only the numeric network summary is kept in this browser for 7 days and added to Device Check and the JSON report. No raw transfer data, URL, IP address, or personal content is saved in the summary.

About 4 MB of generated test dataTransfer amount is the same in both modes

Test guide

What this test proves—and what it cannot

The network test measures HTTPS requests and generated transfers between this browser and the DeviceTriage deployment region. It reports a route-specific sample of response time, variation, failed requests, download, and upload—not the maximum line rate promised by an ISP.

Last reviewed: 2026-09-01

Signals measured

Median HTTPS response time across repeated samples
Jitter as variation between successful response samples
Request loss as failed HTTPS samples
Short generated download and upload throughput

How the test works

Choose 8 response samples for a quick check or 20 for a longer stability view; both modes use the same bounded transfer amount.
Jitter is calculated from variation between returned HTTP samples.
Download uses generated bytes; upload sends generated bytes and stores no personal file.
Payloads and durations are bounded to avoid an unnecessarily heavy test.

Interpreting the results

SignalWhat it meansNext step

Stable samplesResponses returned with limited variation on this route.Compare the affected service if the real problem continues.

High variationTiming changed substantially during the short run.Pause transfers and compare strong Wi-Fi with Ethernet.

Failed requestsSome DeviceTriage HTTPS samples did not return in time.Repeat and confirm with the affected application; this is not raw packet-loss proof.

Measurement limits

Server distance and routing can make this result differ from a game, call, or nearby ISP endpoint.
Browsers do not provide raw ICMP tests, router radio statistics, or modem line diagnostics.
Mobile networks, VPNs, Wi-Fi contention, and background traffic can change every run.

Missing or privacy-reduced detail is not scored as a fault by itself.

Questions about this test

Why is this result different from my ISP speed test?

The target server, route, payload, duration, browser load, and nearby network conditions differ. Use both tests for different questions rather than expecting identical numbers.

Does 0% request loss prove my connection is perfect?

No. It means the short HTTPS sample completed. Intermittent or protocol-specific faults may require longer observation in the affected application.