Performance testing for applications and online stores
We check how the system behaves under load before your customers do it during a campaign. We measure speed on the server and in the browser, point out bottlenecks and help remove them.
When to run performance tests
Before a campaign or a sales peak
Black Friday, a product launch, a TV advert. It is better to know in advance how much traffic the store can take.
The site loads slowly
Users leave before they see the offer, and weak Core Web Vitals lower visibility in Google.
Server costs keep rising
Adding capacity masks the problem. Often a single database query accounts for most of the load.
What you get
Numbers in place of hunches: how much traffic the system handles and what to do so it handles more.
Technology
- k6
- Lighthouse
- Grafana
- JMeter
- WebPageTest
Test scenarios
We reproduce real behaviour: browsing the offer, searching, the cart and payment.
Load tests
We gradually raise the number of users up to the expected traffic and beyond.
Stress tests
We check what breaks first and whether the system recovers on its own.
Bottleneck analysis
The database, caching, external services and server configuration.
Browser performance
Core Web Vitals, script and image size, and the order in which resources load.
Report and fix plan
Results with charts and a list of changes ordered by effect and effort.
How we work together
- 01
Goals
We set the expected traffic, the acceptable response time and the most important paths.
- 02
Test preparation
We write scenarios and prepare an environment with data close to production.
- 03
Tests and measurements
We run the tests while watching servers, the database and response times.
- 04
Report and optimisation
We deliver the results and, after fixes, repeat the measurement for comparison.
What the estimate depends on
- number of scenarios and tested paths
- expected scale of traffic
- availability of a test environment
- analysis on the server side, in the browser or both
- implementing fixes and measuring again
We don't publish a price list, because every project has a different scope. After a short conversation you get a free estimate split into stages.
Request an estimateQuestions about this service
If your question isn't here, write to us.
Are tests run on production?
Preferably on a staging environment with the same configuration. If that is not possible, we test production at night, in an agreed window and with controlled load.
How does a load test differ from a stress test?
A load test checks behaviour under expected traffic. A stress test goes beyond that level to find the breaking point and the way the system fails.
Will you fix the problems you find?
Yes. After testing we can optimise queries, caching and the frontend, then repeat the measurement.
What are Core Web Vitals?
Three Google metrics describing how a page feels to the user: loading time of the main content (LCP), responsiveness to interaction (INP) and layout stability (CLS).
Tell us about your project
Tell us what you want to build or verify. We'll come back with questions, a proposed approach and an estimate.
Free estimate · NDA on request
What happens next
- 1A short call
- 2Estimate with a schedule
- 3Work begins