Skip to content
Calcrivo

Network Performance Health Score Calculator

Score latency, jitter, loss, utilisation and availability into one weighted network health grade.

Inputs

ms
ms
%
%
%

Network Health Score

85.2/100

Grade

B — Good

Weakest Dimension

Jitter

Latency Sub-Score

77.5

Packet Loss Sub-Score

88.0

Capacity Headroom

45.0%

Step by step

  1. Values used

    Average latency = 35 ms; Average jitter = 5 ms; Packet loss = 0.2000 %; Peak link utilisation = 55 %; Measured availability = 99.95 %

  2. 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.

  3. Network Health Score

    = 85.2 /100

  4. Grade

    = B — Good

  5. Weakest Dimension

    = Jitter

  6. Latency Sub-Score

    = 77.5

  7. Packet Loss Sub-Score

    = 88.0

  8. Capacity Headroom

    = 45.0

How it works

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.

Formula

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.

loss
Sub-score falling 60 points per 1% of packet loss
latency
Sub-score falling 1.5 points per ms above 20 ms
utilisation
Sub-score falling 3 points per % above 70%

Frequently Asked Questions

How is Network Performance Health Score calculated?

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.

Why does Network Performance Health Score matter?

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.

What values do I need to enter?

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.

Why is loss weighted more heavily than latency?

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.

You might also need