Skip to content
ARRF
Get Support

The experience grade

The experience grade scores what the phone measured against a usage profile — Video calls by default — and turns it into a 0–100 score, a letter, and a one-line verdict such as “The Wi-Fi is the weak link, not the internet.” It weights the Wi-Fi hop 60% and the internet path 40%, so a slow internet provider isn’t blamed on the Wi-Fi.

It leads the Results screen on an Any Wi-Fi survey, and gets its own Experience card on a RUCKUS survey that also measured experience. The metrics it reads are described on What the phone measures.

Which profiles are there, and what are their targets?

Section titled “Which profiles are there, and what are their targets?”

Pick a profile from the Profile menu on the Experience card. Each profile sets a target per criterion; a criterion the profile doesn’t list isn’t part of its grade.

CriterionWebStreamingVideo calls (default)Gaming
Wi-Fi latency (p95)≤ 50 ms≤ 50 ms≤ 30 ms≤ 20 ms
Jitter——≤ 20 ms≤ 10 ms
Packet loss≤ 2 %≤ 1 %≤ 1 %≤ 0.5 %
Latency under load (Δ)———≤ 30 ms
Internet latency≤ 150 ms≤ 200 ms≤ 100 ms≤ 50 ms
Download≥ 5 Mbps≥ 25 Mbps≥ 3 Mbps≥ 10 Mbps
Upload≥ 1 Mbps—≥ 3 Mbps—

Latency under load (Δ) is how much a cube’s router round trip rose during a speed burst over its own idle round trip — or over the survey’s median idle round trip when the cube has none.

The first four criteria form the Wi-Fi subscore (the hop you can fix); the last three form the Path subscore (they include your internet provider and the test server). With plain labels on — the Home default — they read Router delay, Delay wobble (jitter), Lost packets, Delay when busy, Internet delay, Download speed, and Upload speed.

Does changing the profile change the survey?

Section titled “Does changing the profile change the survey?”

Choosing another profile re-grades the survey on screen — the score, letter, breakdown and verdict all follow. The survey keeps the profile and targets it was captured with, so reopening it later grades it exactly as it did when you stopped. New surveys are captured under Video calls.

Each cube's valueQuality 0-1vs the profile targetCriterion score50% mean + 50% worstdecileWi-Fi subscoreaverage of Wi-Fi criteriaPath subscoreaverage of path criteriaScore = 0.6 Wi-Fi + 0.4PathLetter A-For N/A under 10 cubes
  1. Each cube gets a 0–1 quality per criterion. Full credit at or better than the target, fading linearly to zero at twice the target for lower-is-better criteria (latency, jitter, loss, latency under load), or at half the target for download and upload. There are no band cliffs.
  2. Each criterion scores 0–100 as 50% the mean quality + 50% the quality of the worst-decile value (the 90th-percentile value for lower-is-better criteria, the 10th percentile for speed), so a few bad spots can’t be averaged away.
  3. Criteria average into two subscores, Wi-Fi and Path.
  4. Score = 0.6 × Wi-Fi + 0.4 × Path, clamped to 0–100. If only one family was measured, it is the score on its own.
  5. The score maps to the same letters as the RF grade: A ≥ 90, B ≥ 75, C ≥ 55, D ≥ 35, F below.

The grade needs at least 10 cubes with experience measurements and at least one measured criterion. Otherwise it’s N/A, not F, with the reason: “Experience not measured”, “No video calls criteria measured” (named after the profile), or “Too few readings to grade (N of 10 needed)”.

Each criterion row shows its score, median, worst 10%, target, the share of cubes meeting the target, and the cube count. Worst spots lists up to three cubes with the lowest average quality, naming the criterion that dragged each one down. How experience was measured opens the methodology note.

The letter itself shows only when show letter grade is on; the Home default hides it and lets the verdict lead.

The verdict is a fixed sentence — no AI — chosen from the Wi-Fi and Path subscores and, on a RUCKUS survey, the RF grade. A subscore below 75 (under a B) counts as weak. A part that wasn’t measured is never called good.

SituationHeadline
Wi-Fi and internet both weakBoth the Wi-Fi and the internet connection are holding things back.
Wi-Fi weak, internet fineThe Wi-Fi is the weak link, not the internet.
Wi-Fi weak, internet not testedThe Wi-Fi is the weak link.
Internet weak, Wi-Fi fineThe Wi-Fi is fine; the internet connection is the weak link.
Internet weak, Wi-Fi not testedThe internet connection is the weak link.
Experience fine, RF coverage weakWorks today, but coverage is thin in places.
Everything fineWi-Fi and internet both look good.
Wi-Fi fine, internet not testedThe Wi-Fi looks good.
Internet fine, Wi-Fi not testedThe internet connection looks good.
RF only, coverage weak (score under 55)Coverage is weak across much of the space.
RF only, coverage weak (55–74)Coverage is thin in places.
RF only, coverage fineSignal coverage meets the target.

The supporting sentence says what’s dragging it down — “Mainly Wi-Fi delay.”, “Talk to the internet provider.”, “Fix the Wi-Fi first …, then check with the internet provider.”, or “Only N% of spots reach −67 dBm.” — and names anything untested, such as “The internet connection wasn’t tested.” An RF-only survey always adds “The connection itself wasn’t tested.”

Two clauses can be appended:

  • “Worst in Kitchen.” — the weakest rated room, when the weak link is in the building (the Wi-Fi or coverage), never for an internet problem.
  • “QUIC/UDP blocked — calls and video may suffer.” — whenever the network policy check found QUIC or all UDP blocked.

When nothing could be graded there is no verdict.