Sample Report
Sample Load Test Report
Preview the kind of launch-readiness report you get after running a small controlled test on a website or API you own.
Start a safe testExample Summary
This sample shows a healthy API endpoint under a short permission-based test. Use it to understand what each metric means before running a small controlled test on your own permitted target.
Status Code Breakdown
How To Read This Report
- Check failed requests first. Errors and timeouts usually matter more than raw speed.
- Use p95 and p99 latency to spot slow responses that averages may hide.
- Compare requests per second against the traffic level your launch or campaign expects.
- Download JSON or CSV reports when you need to share evidence with your team.
Use It As A Before-And-After Baseline
Save a report before a deploy, rerun the same URL with the same traffic settings after the deploy, and compare p95 latency, p99 latency, error rate, timeout count, status codes, and requests per second. That repeatable workflow turns a report into launch evidence.
Read the before and after load testing guide for a practical comparison workflow.
Sample Report FAQ
What does p95 latency mean?
p95 latency means 95% of requests completed at or below that response time. It is useful because averages can hide slow outliers.
What is a good error rate?
For a small launch-readiness check, aim for 0% errors. Any timeout, 5xx response, or unexpected status code deserves investigation.
Can I download the report?
Yes. Completed tests can be downloaded as JSON or CSV so you can share metrics with developers, clients, or teammates.