Load testing

4 min read Updated: 11.11.2026

On this page What does the test measure?
  1. What does the test measure?
  2. How does a test run?
  3. Domain verification
  4. Test version and production
  5. When does a test stop on its own?
  6. How to read the result?
  7. A test without a result
  8. Firewall and exceptions
  9. Monitoring during the test
  10. Plan limits

A load test shows how much traffic your application can handle before it starts slowing down or returning errors. That way you know whether your site will cope with a campaign, a sale or a sudden spike in visits before your customers find out for you.

What does the test measure?

The test sends your site more and more requests and measures the response time and the number of errors every second. The result tells you plainly how many requests per second the site handled without slowing down, and what broke first: response time or server errors.

We test the addresses your users actually visit. If the DockRay plugin is running in the project, we take the most visited pages from recent days and keep their proportions. Without the plugin, we test the home page. The test sends only ordinary read requests - it does not place orders, log in or fill in forms.

How does a test run?

Every test starts with a short measurement at minimal traffic. It shows how quickly the site responds under calm conditions, so any later slowdown has something to be compared against.

There are two types of test to choose from:

  • Ramp up to the limit - traffic grows in steps, and the test ends at the first step where the site stops keeping up. It answers the question "how much can I handle?".
  • Steady traffic - a chosen level of traffic for several minutes. It answers the question "can I handle this much?" and catches problems that only build up over time.

At the end, we watch for a moment whether the site returns to normal operation. A test usually takes a few minutes. You do not need to wait at the screen - when it finishes, you will get a notification in the panel and an email.

Domain verification

Before you run your first test, confirm that the domain belongs to you. This safeguard prevents traffic from being sent to someone else's server. You can do it in one of three ways:

  • DockRay plugin - if it runs on this site and sends data, verification is automatic,
  • DNS record - add a TXT record with the value shown in the panel,
  • file on the server - place a file with the same value at the given address.

Verification applies to a specific address and we check it again before every test. If you change the site address in the project settings, you need to repeat it.

Test version and production

By default, the test goes to the project's test version. Testing production is possible, but it requires deliberate confirmation, because it loads a live service and its real users. If you can, test a copy of the site with the same server configuration.

When does a test stop on its own?

We do not take down a running application. The test stops automatically when:

  • the server starts returning a lot of errors,
  • the response time exceeds the threshold and further steps would show nothing new,
  • the firewall in front of the server starts blocking test traffic.

You can also stop a test manually at any time. The result from the measurements taken so far is saved.

How to read the result?

The most important figure is the traffic the site handled without slowing down. Next to it you will find the response time without load and under load (p95 - the time within which 95% of responses fall), the error rate and a chart of the whole test.

Below the chart you can see the errors your application reported during the test. This lets you connect the slowdown with its cause right away - for example, an exhausted database connection pool.

If most responses came from the CDN cache, the result says more about the CDN than about the application server itself. The panel then shows a warning.

A test without a result

Sometimes a test ends without a result: the firewall did not let the traffic through, our generator was overloaded or the connection was interrupted. The cause then lies on our side or in front of your server, so it says nothing about its performance. Such a test does not count against the monthly limit.

Firewall and exceptions

If your site sits behind a firewall, such as Cloudflare, add the X-DockRay-LoadTest header and our User-Agent shown in the panel to the exceptions. Without this, the firewall may stop the test before it reaches the server.

Monitoring during the test

For the duration of the test and a few minutes after it, we pause availability checks, error spike detection and scheduled scenarios in this project. This way you will not get alerts about an outage caused by a test you ordered yourself. After that, monitoring resumes and checks the current state of the site.

Plan limits

The free plan includes one small test per month. Paid plans give you more tests and a higher maximum traffic. You will find the details in the pricing.

Keep reading

DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.