Latency Round-Trip Test

Measure total round-trip network latency from your browser to a remote server and back.

Round-trip time (RTT) in milliseconds measured over multiple requests. Click Start Test; the test sends packets and measures the time until a response arrives.

♢ Runs in your browserNo installationResults can be affected by browser and system conditions
◴

What does this test measure?

Round-trip time (RTT) in milliseconds measured over multiple requests.

☆

Why is this test important?

Measure total round-trip network latency from your browser to a remote server and back.

▻

How do you run the test?

Click Start Test; the test sends packets and measures the time until a response arrives.

▥

How should results be interpreted?

Under 20 ms is excellent for gaming; 20-50 ms is good; above 100 ms causes lag.

☑

Normal and problematic results

Under 20 ms is excellent for gaming; 20-50 ms is good; above 100 ms causes lag.

△

Technical limitations

Results vary by server distance, ISP routing, and current network congestion.

↘

Why can the score decrease?

Unstable measurements, denied permissions, unsupported browser APIs, background load, power saving, or an incomplete test can affect the result. When a score changes, the result screen explains the reason.

⌕

What should you do if a problem is found?

Use a wired connection, close bandwidth-heavy apps, or contact your ISP.

Example Result Explanation

✓ GoodA stable, repeatable result in the expected range. A clear and consistent experience is expected.
△ AttentionSome indicators should be checked again. Reduce background activity and repeat the test under the same conditions.
× ProblemA repeated clear failure or instability means the relevant setting, connection, or device needs closer review.

Frequently Asked Questions

Does this test provide a definitive hardware diagnosis?

No. The test measures signals the browser can safely access and clearly explains its technical limits.

Why can results change between runs?

Background applications, power mode, network conditions, permissions, and operating-system timing can affect results.

How should I repeat the test if I see a problem?

Repeat it on the same device and browser while changing only one condition, so the source of the difference is easier to identify.