Low-data responsiveness check
Measure responsiveness, not just raw speed.
Thirty sequential samples reveal the median delay, jitter and spikes that matter to calls, remote desktops and games.
Live measurement
Latency & Jitter Test
This test uses only small requests, but background tabs, extensions and battery saving can still affect timing.
Results will update live on this page.
This run
Network quality summary
Translate it into real tasks
These are transparent threshold-based guides, not service guarantees.
VPN deltas versus direct baseline
Method
Thirty samples, one stable summary
The browser sends 30 zero-byte latency requests to Cloudflare Speed. Median latency resists one-off spikes; jitter is the average absolute change between consecutive samples. The chart keeps every measured point visible.
A concrete example
Why jitter changes the experience
A 35 ms median with 4 ms jitter is usually steadier than a 25 ms median with repeated 100 ms spikes. The second connection looks faster in one number but may feel worse in live audio.
Limits and uncertainty
What these numbers can—and cannot—tell you.
- 01
HTTP application latency includes browser scheduling, TLS/connection reuse and the path to Cloudflare; it is not an ICMP ping to a game server.
- 02
This test does not load the connection, so it cannot reveal bufferbloat. Use the full speed test for loaded latency.
- 03
No packet-loss claim is made; a failed HTTP request is reported only as a measurement failure.
Anonymous feedback
Did this tool solve the job?
Found a problem or an idea to make this tool better? Tell us. We review every report and start working on actionable improvements within 2 days, continuously improving reliability and usability.