A slow site loses enquiries it never tells you about
We measure what is actually costing you, fix it in order of impact, and show you the before and after in numbers rather than adjectives.
What we do
Website performance optimisation that starts with measurement
Slow sites fail quietly
A site that takes six seconds to load does not produce a complaint. It produces a visitor who went back to the search results, and a number in your analytics that looks like ordinary bounce rate.
It also costs you twice. Google uses page speed as a ranking factor, so the slow site ranks lower, and the smaller number of people who do arrive are more likely to leave. The two compound.
Measured, not guessed
Most performance advice is generic — compress your images, install a caching plugin, use a CDN. Sometimes that is the answer. Often the actual problem is one script from a plugin nobody uses, or a font loading in a way that blocks the page, or a server that takes 700 milliseconds to think before it says anything.
We measure against Core Web Vitals — Google’s published standard — then work through the findings in order of impact. You get the numbers before and after, so the result is checkable rather than a claim.
What this looks like in practice
On our own site, the homepage went from 9,368 KiB to 1,677 KiB and server response time from 690 milliseconds to 160. Most of that came from four changes, none of which was the thing anybody would have guessed.
Where the finding is that your site is already fine and the money is better spent elsewhere, we will say so. That happens more often than the industry admits.
Everybody has an opinion about why a site is slow. The waterfall chart has the answer.
DIGIDMN
Measured results
What performance optimisation delivered on our own site
Same site, same content, measured before and after.
Reduction in homepage size — 9,368 KiB down to 1,677
Faster server response — 690 ms down to 160
Accessibility score after the work, up from 94
Typical turnaround for a performance audit
What is included
Every performance optimisation project includes
Baseline measurement
Where the site is now, on real connections and real devices, before anything changes.
Waterfall analysis
What loads, in what order, and what is blocking everything behind it.
Prioritised findings
Every issue ranked by impact against effort, so the cheap wins are obvious.
Implementation
The fixes applied — by us, or handed to your team as a specification they can work from.
Re-measurement
The same tests run again, so the difference is a number rather than an impression.
Before-and-after report
What changed, what it moved, and what is left that was not worth the cost.
Common questions
Performance optimisation questions answered
What people ask before commissioning performance work.
The audit is a fixed price based on the size of the site, and you get the findings whether or not you ask us to implement them.
Implementation is quoted afterwards, because until the audit is done nobody knows whether the problem is one plugin or the entire hosting setup. Quoting the fix before finding the fault would be guessing.
Tell us the address and we will price the audit.
Start here
Start with a performance audit
Send us the address. We will measure it, tell you what is slowing it down and what fixing each thing is worth — and you get the findings whether or not we do the work.