Score latency, jitter, loss, utilisation and availability into one weighted network health grade.
Each measurement is mapped onto a 0–100 sub-score against an engineering threshold, then combined with weights that reflect how strongly each one degrades application experience. Loss carries the most weight because TCP throughput is inversely proportional to its square root. A single grade makes network quality reportable to people who do not read ping output, and the weakest-dimension flag points straight at what to fix first.
Network Performance Health Score
score = 0.30 × loss + 0.25 × latency + 0.15 × jitter + 0.15 × utilisation + 0.15 × availability, each dimension normalised to 0–100.
score = 0.30 × loss + 0.25 × latency + 0.15 × jitter + 0.15 × utilisation + 0.15 × availability, each dimension normalised to 0–100. Each measurement is mapped onto a 0–100 sub-score against an engineering threshold, then combined with weights that reflect how strongly each one degrades application experience. Loss carries the most weight because TCP throughput is inversely proportional to its square root.
A single grade makes network quality reportable to people who do not read ping output, and the weakest-dimension flag points straight at what to fix first.
This calculator takes 5 inputs: Average latency, Average jitter, Packet loss, Peak link utilisation, Measured availability. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Latency degrades experience linearly, but loss degrades TCP throughput as 1÷√p and forces retransmission timeouts. A tenth of a percent of loss can cost more throughput than an extra 50 ms of RTT.