> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/load-testing/run-a-load-test-and-read-results.md).

# Run a Load Test and Read Results

Select **Run** on a load test to dispatch it. The run appears on the **Results** tab immediately and its charts update live while virtual users execute.

![Load test results](/files/I6CTZlRfyKIL6DKiS8Qk)

## Reading A Result

| Element                       | What it tells you                                                                                                                      |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Runs strip                    | Each past run with status and age — select one to inspect it.                                                                          |
| What this run did             | The mode (Simple — browser users replaying features, or Advanced — protocol k6), target URL, load profile, and the features exercised. |
| KPI tiles                     | Total requests (with peak rate), latency p95, error rate, peak concurrent users, and (Advanced) threshold gates.                       |
| Latency percentiles           | p50/p90/p95/p99 over time — a rising p95 under steady load is your earliest saturation signal.                                         |
| Throughput, users, error rate | Confirm load actually ramped as configured and correlate error spikes with load level.                                                 |
| By step — latency under load  | Simple runs: per-step p50/p95/p99 and error rate, so you can see which step of the journey degrades first.                             |

An **Advanced** run passes when every threshold gate holds for the whole run — a failed gate marks the run failed even if all requests technically succeeded. A **Simple** run reports per-step timings without gates and fails when the replayed features fail under load.

## Act On The Result

* **Ask AI** seeds the Assistant with a data-rich summary of the selected run — useful for sharing a quick verdict.
* **Export** downloads the full results as JSON, the per-step/per-endpoint table as CSV, or the raw metric samples as CSV.
* **Cancel** stops an in-flight run; **Delete** removes a terminal one.

## When Results Look Wrong

* A 100% error rate usually means the target URL was unreachable from the fleet — check the Target section and any access controls.
* Flat-zero throughput with running virtual users means journeys are failing before their first request; re-run the journey as a functional test first.

## Related Help

* [Create a load test](/load-testing/create-a-load-test.md)
* [Understand live run status](/run-tests/understand-live-run-status.md)
* [Share or export results](/results/share-or-export-results.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/load-testing/run-a-load-test-and-read-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.