Reading your performance report
Per-transaction response times, percentiles, errors, and what good looks like.
# Reading your performance report
The performance report is per-transaction, not just an overall average.
## Response times
For each step you get min / avg / median / **p90 / p95 / p99** / max and standard
deviation. Watch the **p95** — it's what most of your users actually experience,
far more honest than the average.
## Throughput and errors
Requests per second (TPS) and errors grouped by status code, with root-cause
grouping so you can see *why* requests failed, not just that they did.
## Pass / fail against NFRs
If you set NFRs (e.g. p95 < 800ms, error rate < 1%), each is evaluated and marked
pass / warn / fail.
We only show numbers from a load test that actually ran — never synthetic
figures.
Tags: performance report, results, response time, p95, percentile, errors, reading results, throughput, tps