Nobody has a number
The site feels slow. Without a measurement every fix is an opinion, and the first person to name a technique wins the argument.
Services
Speed and reliability
Nine seconds is not one problem. It is a large image, a script waiting for another script, a query with no index and a server in the wrong region, added together. Before changing anything we measure the page the way a customer on a phone in Algiers experiences it, and we write down which of those is actually the cost.
Who it is for
- Sites that feel slow on a phone and acceptable on the office desktop.
- Businesses whose contact form is opened more often than it is submitted, on a page nobody has timed.
- Teams that paid for speed work and cannot say what improved.
Problems it solves
The homepage carries everything
A carousel, three tracking scripts and an unoptimised hero image on every page, because the template was assembled once and never weighed.
The database grows and the page follows
A listing page that was fast on a small table slows as the table grows, because the query sorts a column with no index.
Use cases
A measured baseline
Field data from a real phone on a mobile connection: when the main content appears, the total bytes, and the requests that block the first render.
Images that are actually sized
Modern formats, the right dimensions per screen, and lazy loading below the fold — usually the largest single saving on the page.
Fewer scripts, loaded later
Tags that are not needed are removed, the rest are deferred, and every third-party pixel is audited for what it actually returns.
Caching and a server in the right place
Static assets cached at the edge, pages generated rather than rebuilt per request, and the database in the region your users are in.
What is in scope
Fixed scope. Fixed price.
Agreed in writing before anything is built. You approve before we start.
- A performance baseline measured on real devices and connections
- A list of causes ranked by cost, effort and effect on the user
- Image, font and script optimisation
- Query and index review for the pages that are slow
- Caching, compression and a deployment that serves from near the user
- A before-and-after report on the same pages under the same conditions
How it is delivered
- 01
Measure what the customer sees
Whoever reports the slowness shows us the page and the phone. We record the same journey with the network throttled, not on the office fibre.
- 02
Separate the causes
Front end, back end, network and third parties, each with its share of the time. A fix aimed at the wrong layer makes the number worse.
- 03
Fix in order of return
The largest cause first, released and measured again before the next one. No redesign to hide a slow query.
- 04
Keep a performance budget
A page-weight limit and a rendering target checked with every release, so the next feature does not undo the work.
FAQ
Questions about this service.
What owners usually ask before requesting a quote for it.
Can you guarantee a perfect score?
No. A score is a model of a page, not the page itself. We commit to a measured improvement on the pages that matter, on the devices your customers use, and we show the numbers before and after.
Do we need a redesign?
Usually not. Most of the time sits in images, scripts and queries, and those can be fixed under the existing design. A redesign is justified when the structure is the problem, not when the paint is.
How long does the work take?
It is scoped after the measurement, not before, because the cause decides the effort. One slow page is not the same job as a whole site with a database behind it.
What if the slowness is not the website?
Then we say so. A site that loads fast while the counter crawls at five in the afternoon is a database or a network problem; a page waiting on a third-party script you cannot remove is a contract problem. We will not sell optimisation for a cause we cannot move.
Start a project
Want this scoped for your business?
Send the brief. It comes back as a written scope and a fixed quote before anything is built.