Load testingAll features.
Everything a Load test does today: what you can set, each figure it measures, how the rating is decided, and what is in the report.
33 features in 7 groups, checked against the product on 14 November 2026.
Setting up a run
One verified site
You choose the site from a list of your own verified sites.
1 to 6 concurrent users
A slider from 1 to 6; it starts at 3.
15 to 30 seconds
A slider from 15 to 30 seconds in steps of 5; it starts at 15.
The home page, over HTTPS
Every request is a GET of the site's home page, and redirects are followed. There is no setting for another path, method or header.
Sent from Cloudflare's network
The traffic comes from Cloudflare's edge. You do not choose a region.
All users start together
Each user sends one request after another until the time is up. There is no ramp.
15-second limit per request
A request with no answer in 15 seconds is stopped and counted as a timeout and a failure.
A recognisable user agent
Requests are sent as BCDRPulse-LoadTest/1.0.
What it measures
Response time
The average, the fastest and the slowest, and the 50th, 90th, 95th and 99th percentiles, over every request, with the whole answer read.
Time to first byte
The average and the 50th, 90th, 95th and 99th percentiles of the time until the answer's headers arrive. It is timed from the start of the request, so it includes setting up the connection.
Transfer
The average time to download the body, the total bytes and the average bytes per request.
Requests and failures
Total, successful and failed requests, the timeouts, and the error rate. Any answer that is not 2xx counts as a failure.
Requests per second
Every request sent, divided by the length of the run.
Status codes
A count for each HTTP status, and for timeouts and network errors.
Consistency score
From 0 to 100: how steady the response times were. 100 means every request took the same time.
The rating and the summary
A risk rating by fixed rules
Elevated when 5% of requests or more failed or the 99th percentile reached 3 seconds. Moderate when 0.5% failed, any request timed out, the 95th percentile reached 1 second or the 99th reached 1.5 seconds. Otherwise Low. AI does not decide it.
It says when the test was refused
When most failures are HTTP 429 or 403, the report says a rate limit or a firewall rule turned the test's traffic away, and does not call the site slow.
An AI summary
Three short parts: the verdict, what it means and what to check. It is written from the run's own figures and has to agree with the rating. If the AI is not available the report has no summary; the figures are not affected.
The report
A PDF for every finished run
With a report ID, the time of the test and the time the report was made, and page numbers.
Its sections
Executive summary, risk assessment, performance summary, scope and method, latency analysis, status codes, the raw figures, trend, and recommendations in order of priority.
Trend
The error rate and the 95th percentile beside the previous finished run on the same site.
Recommendations by rule
Rated High, Medium or Low, from the failures, any refusal, the slowest requests and the consistency score.
Combined report
On the Reports page up to 50 reports, from this product and the others, can be merged into one PDF with a cover and a contents page.
History
The page shows your 10 most recent runs. The Reports page lists every finished run.
Queue and controls
One run at a time
A second load test cannot be queued while one of yours is queued or running.
Starts within about a minute
Queued runs are picked up once a minute, oldest first. When many tests are running across the platform you are asked to try again in a minute.
A run that hangs is closed
A run with no result after 2 minutes is marked as failed.
Ownership and safety
Verified sites only
A run is accepted only for a site of yours whose DNS record has been confirmed, and the site is checked again when the run starts.
Public addresses only
A host that does not resolve to a public address is refused when you ask for the run and again before it starts.
Plans and limits
Pro
100 load tests a month.
Business
500 load tests a month. The size of a run is the same on both plans.
Resets on the 1st
Allowances count over the calendar month, in UTC, and reset on the 1st.
A run that never started is not counted
For example one refused because the host was not a public address.
What it does not do.
- It does not find the most your site can take. Six users for 30 seconds is a quick read before a release; Cloud load testing sends up to 1,000 users.
- It requests the home page only. Behind a CDN the result can be the CDN's cache and not your server.
- It has no ramp, no chart over time, no pass or fail limits of your own and no schedule, and a running test cannot be cancelled (it ends within 30 seconds).
- It is not a penetration test: nothing is exploited and your application's logic is not tested. We do not offer one.