Understanding results
Key metrics
Response time
http_req_durationHow long your server takes to respond. Look at the median (p50) for typical performance and p95/p99 for tail latency.
Throughput
http_reqsRequests per second your server handles. In an arrival-rate run the plan fixes the rate sent, so throughput should track the plan.
Error rate
http_req_failedShare of requests that returned an HTTP error or failed to connect. loadtest.dev splits it into 5xx, 4xx, 429, timeout and transport.
Rate limited
429Responses refused by a rate limiter. The service reports 429s separately; investigate the target and any upstream limiter before increasing the rate.
Check pass rate
checksStandalone k6 scripts can validate response bodies, headers and status codes with checks. The loadtest.dev plan does not accept custom checks, and this metric is not part of its run summary.
Data transfer
data_received / data_sentStandalone k6 reports transferred bytes. This can help identify payload changes, but loadtest.dev does not expose this metric in its run summary.
Understanding percentiles
An average can hide slow responses. If p99 is 5 seconds, roughly one percent of measured requests took at least that long. loadtest.dev merges scenario histograms within a run before reading percentiles; it does not average scenario percentiles.