Connection data from the browser network stack
The page reads online state, effective connection type, downlink estimate, round-trip time, and data saver status when the browser exposes them.
This browser-based network test surfaces the connection information exposed to the page, measures latency to the current site, estimates same-origin download throughput, and runs lightweight reachability probes.
Online status
Unavailable
Effective type
Unavailable
Downlink
Unavailable
RTT
Unavailable
Save-Data
Unavailable
This test pings a same-origin asset several times, then downloads one local image to estimate browser-visible throughput to the current site.
Same-origin latency
Not tested
Download estimate
Not tested
These probes are simple browser reachability checks. They are useful for spotting obvious blocks, captive portal issues, or severe routing failures, but they are not a substitute for a full network lab.
Current site asset
Run the suite to test
Google favicon
Run the suite to test
Cloudflare favicon
Run the suite to test
This page is built for search intent like "network test", "network checker", and "network diagnostics". The tool runs directly in the browser so users can verify the hardware path before moving on to deeper troubleshooting.
The page reads online state, effective connection type, downlink estimate, round-trip time, and data saver status when the browser exposes them.
A same-origin fetch test avoids many cross-origin restrictions and gives a realistic measure of how the current site is responding from your browser session.
Image-based probes help catch severe routing or blocking problems, which is useful when a user says the internet works in some places but not others.
If the page already shows an offline state, fix that first before interpreting the rest of the metrics.
This gives you a quick same-origin response time plus a simple download estimate to the current site.
If some targets fail while others succeed, you may be dealing with filtering, DNS routing issues, a captive portal, or enterprise network policy.
This page validates what a web app can see from inside the browser. It is useful for support triage, but it is not a replacement for packet captures, traceroutes, or ISP-grade speed tests.
Cross-origin network measurement is heavily constrained in browsers, so the most dependable timing signal here is the current origin rather than arbitrary third-party endpoints.
When users report a slow site, intermittent loading, or frequent timeouts, this page helps determine whether the issue is obvious at the browser level before deeper investigation.
No. It provides a browser-visible estimate to the current site, which is useful for troubleshooting, but it is not a controlled ISP bandwidth benchmark.
The Network Information API is not consistently supported across browsers and operating systems. When the browser does not expose a field, the page cannot invent it.
Yes. A target may block requests, rate-limit, or fail to load for reasons unrelated to your local network path. That is why these probes are best treated as hints rather than final proof.
Same-origin checks are more reliable in browsers because they avoid many cross-origin restrictions and match the real path a user is trying to load.
These tools cover related search intents without duplicating the same copy. Each page focuses on a specific device path so users can isolate the problem faster.
Display specs, browser FPS sampling, and a quick PPI calculator for monitor checks.
Speaker tones, left-right stereo checks, and a live microphone level monitor.
Live camera preview, device selection, and stream settings such as resolution and frame rate.
A live mouse pad that tracks clicks, wheel scrolls, and movement in real time.
A browser keyboard tester with a visual layout, pressed-key state, and modifier tracking.
Last updated: April 3, 2026