NetHealthLab

Is your internet actually good?

Run a quick check and get one clear answer.

No signup required · About 15 seconds

What we measure

Every check measures five things between your device and the nearest NetHealthLab server on Cloudflare’s network:

Download
How fast data reaches you, in megabits per second (Mbps). Streaming, downloads and page loads depend on it.
Upload
How fast you can send data. Video calls, cloud backups and sending large files depend on it.
Latency
How long a small request takes to travel there and back while the connection is quiet, in milliseconds (ms). Lower feels snappier.
Jitter
How much that round-trip time changes from one moment to the next. High jitter makes calls and games stutter.
Loaded latency
Latency measured while a download is running. A big jump means the connection slows down when it gets busy.

What your score means

The Internet Health Score combines those five measurements into a number from 0 to 100. Speed counts, but with diminishing returns: beyond roughly 300 Mbps down and 100 Mbps up, more speed doesn’t raise the score. Responsiveness counts just as much, and one seriously weak area holds the whole score down instead of being averaged away.

  • Excellent (85–100): fast and responsive for everyday use.
  • Good (70–84): works well for most households; one area may be a little weak.
  • Fair (50–69): usable, but weaknesses are likely to be noticeable at times.
  • Poor (0–49): a serious weakness that everyday use will probably run into.

See how each measurement and finding is explained

Common reasons a connection feels slow

  • The network is busy. Someone streaming, uploading or updating a game can push latency up for everyone else. It’s a frequent cause of laggy calls on otherwise fast connections.
  • Distance from the router. Wi-Fi gets slower and less stable through walls and floors. Checking again next to the router, or on a cable, shows how much Wi-Fi is costing you.
  • Interference. Neighbouring networks and some appliances share the same radio channels, which can make jitter jump.
  • Your plan or provider. If results stay low even right next to the router, the limit may be the plan itself or congestion on your provider’s network.
  • A VPN or proxy. Routing traffic through another server usually adds latency and can cap speed.
  • Mobile networks. Cellular speeds change from minute to minute with signal strength, location and how many people share the same cell.

What a browser test cannot see

NetHealthLab runs entirely in your web browser. It measures how your device, your home network and your provider perform together on the way to our server. It can’t read your Wi-Fi signal strength, inspect your router’s hardware or see other devices on your network, and every result is a snapshot of one moment. That’s why our findings describe what a result may mean and what to try next, rather than naming a definite cause.

About data usage

To measure speed accurately, a check has to move real data. On a fast connection one check can transfer several hundred megabytes; on slower connections it uses much less. If you’re on a limited or pay-as-you-go mobile plan, keep that in mind before running repeated checks. The result screen shows roughly how much data your check used.

Learn more