Performance testing: speed, and holding up under load
A slow page loses customers before they see what you sell. We measure how fast your product is on ordinary phones and connections, and how it behaves when many people use it at once.
Pay as you go: you pay for each finding, at a rate agreed before we start.
What we measure
Page speed
How long the main pages take to show and to respond, on a mid-range phone and a slow connection.
Core Web Vitals
Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, the measures Google uses.
What slows it down
Heavy images, unused scripts, slow server responses and fonts that block the page.
Load
Response times as the number of users rises, and the point where errors begin.
Spikes
A sudden rush, such as a sale or a campaign, and how long recovery takes.
Long runs
Hours of steady use, to catch memory leaks and slow build-up.
How the work runs
We agree the targets
Which pages and actions matter, and what counts as fast enough for your users.
We measure
Speed tests on real devices, then load tests against a test environment.
You get the findings
Each problem with its measured cost and what causes it, in order of impact.
We measure again
After your fixes, the same tests show how much changed.
Questions about this service
How is performance testing priced?
It is pay as you go. You pay for each bug or improvement we find, at a rate set by its severity. We agree the rates with you before any testing starts.
Will a load test take our site down?
Load tests run against a test environment, or at an agreed quiet time with a limit we set together. We raise the load in steps and stop when errors begin.
Do you fix the speed problems too?
We find and explain them. Fixing them is your developers' work, and we re-measure afterwards to confirm the gain.
Tell us what to test
Send a link and what worries you most. We reply with what we would look at first.
Start a project