How Cloudflare Speed Test's Network Quality Score Rates Streaming, Gaming, and Video Calls

The Network Quality Score on speed.cloudflare.com turns your raw measurements — download, upload, latency, jitter, and packet loss — into three separate activity scores: Streaming, Gaming, and Video Calls. Each score answers a different question, because each activity stresses your connection differently. The scores stay marked "pending" until a test run completes, and they are only as current as your last measurement.

What the score actually measures

When you run the test, Cloudflare's page reports five underlying metrics:

The Network Quality Score is derived from these measurements rather than being an independent test. That matters: if a metric is missing or the run is incomplete, the related activity score can't be finalized.

Why there are three scores instead of one

A connection that streams 4K video comfortably can still be poor for competitive gaming, and vice versa. The three scores weight the same metrics differently:

• Streaming leans on sustained download throughput. Buffering is mostly a bandwidth problem, so a stable high download rate matters more than millisecond-level latency.
• Gaming leans on latency, jitter, and packet loss. Real-time input and position updates are small but must arrive quickly and consistently; a brief spike is felt immediately.
• Video Calls sits between the two. Two-way audio and video need adequate upload as well as download, plus low enough latency and jitter that conversation doesn't overlap or drop.

Because the inputs overlap, improving one weak metric — say, reducing jitter — can lift more than one score at once.

Reading the scores in practice

Each activity score is an indicator of suitability, not a guarantee. A few practical points:

• "Pending" is normal before a run. The page shows Streaming, Gaming, and Video Calls scores as pending until the test produces measurements.
• Re-run after changes. Scores reflect the conditions at test time. Moving closer to the router, switching bands, or changing ISPs means you should retest rather than trust an old score.
• Compare like with like. A score taken over Wi-Fi in one room isn't directly comparable to one taken over Ethernet. Keep the setup consistent if you're tracking changes.
• One number isn't the whole story. If Gaming scores low but Streaming is fine, the fix is usually latency/jitter-related (congestion, Wi-Fi interference) rather than raw speed.

A concrete example

Suppose a test returns fast download, fast upload, low latency, but noticeably high jitter and some packet loss. You'd likely see a strong Streaming score, a weaker Gaming score, and a middling Video Calls score. The bandwidth is clearly sufficient; the problem is consistency. In that situation, checking for background downloads, Wi-Fi interference, or an overloaded router is more useful than shopping for a faster plan.

Privacy note worth knowing

Running the test shares your IP address with Cloudflare, which uses it to estimate your country/city and identify your ISP's Autonomous System Number (ASN). Cloudflare truncates the IP address it receives to /24 (IPv4) and /48 (IPv6) and shares anonymized measurement data — not your IP — with measurement partners. A single test can consume up to 200MB of data, so avoid running it repeatedly on a metered connection.