Load and performance testing
Load testing that shows what happens when traffic grows
Before a launch, a campaign, or a big new customer, we put your product under the traffic you expect and more, and tell you where response times climb, where errors start, and how much headroom you have. Report and metrics land in your dashboard.
Included in the Scale plan, or EUR 299 per API run as an add-on. Bigger profiles are quoted custom.
You order it, we shape it
Find the breaking point before your customers do.
In your dashboard you order exactly the load test you want: which API or journey, how much traffic, for how long, against which environment. Which metrics we measure is agreed per client; the standard set (p95 response time, error rate, throughput) is always included. If you want, we run your automated tests during the load, so you see how the app behaves for a real user while it is under pressure.
What you get back
- Where response times start to climb, and at what load
- Where errors appear, and what they were
- How much headroom you have, and what to fix first
How we work
From the first call to a clear result.
- 01
You define the test
In the dashboard: which API or journey, how much traffic, for how long, which environment, and what counts as too slow. Metrics are agreed per client, the standard ones are always in.
- 02
We run it in steps
Traffic ramps up in agreed levels against staging or an environment you approve. Optionally your automated tests run at the same time, so we see the app under load the way a user does.
- 03
You read the results
Report and metrics in your dashboard, plus a short review: what held, what broke, what to fix first. Slack, Teams, or email tells you when it is in.
Results, evidence, and QA requests live in your Release Shield dashboard. Bugs go to Jira or Linear, updates to Slack, Teams, or email. See the dashboard
Example load profile
A growing search API
Traffic steps up from 20 to 200 users while we watch p95 response time against the agreed 800 ms. Run the ramp to see where it gives.
Watch the ramp
Press the button: traffic ramps from 20 to 200 users and the response-time line draws itself against the agreed threshold.
What you receive
- A traffic profile, thresholds, and metrics agreed with you
- Report in your dashboard, with the raw metrics to download
- A short review: what held, what broke, what to fix first
What we need to start
- An environment we may load, and a time window
- The journey or endpoints to test, with test data
- Expected traffic and what counts as too slow
Common questions
Will you run load against production?
Only if you explicitly agree the limits and the time window. Staging or a copy of production is the usual choice.
Do I need to set anything up?
An environment we may load and a way to reach it. You order the test in your dashboard; we write the scripts, run them, and upload the report and metrics.
Which metrics do you measure?
That is agreed per client. The standard set is always included: p95 and p99 response time, error rate, throughput, and threshold results. Anything specific to your product is added on request.
Can you run the automated tests during the load test?
Yes. If you want, your end-to-end tests run while the load is on, so you see whether a real user can still complete the key journeys under pressure.
Is load testing in the monthly plans?
Scale includes it. On other plans it is an add-on per API run, and larger profiles are quoted separately.
Can you run stress or spike tests too, and which tool do you use?
Yes. A stepped load test is the default; stress tests and spike tests against an API or a full user journey are ordered the same way, from your dashboard. We write the scripts in current open-source load testing tooling such as k6 and share the raw metrics with the report, so nothing is locked to us.
Book a demo. We agree the first load test on the call.
30 minutes on Google Meet. Pick a time directly in our calendar.