Start a build

What we build

How we run it

Why us

Start a build

Typical first reply · under 4 hours

Case study

4.1 seconds
to under one.

A storefront that was losing mobile visitors before it finished painting. The fix was architectural, not a plugin.

4.1s under 1s

Largest Contentful Paint on mobile

The problem

The site was slow in the specific way that costs money: fine on a desk, unusable on a phone on a train. Years of plugins had each solved a real problem and collectively made the storefront impossible to render quickly.

The usual advice — compress the images, add a caching layer — had already been taken, twice.

What we did

We went headless and moved rendering to the edge, which meant rebuilding the storefront rather than optimising it. Product data stayed where the client’s team already managed it, so nobody had to learn a new admin.

Checkout, tax and fulfilment were treated as the real project. That is where commerce builds actually get expensive, and where a fast homepage in front of a broken checkout would have proved nothing.

What changed

Largest Contentful Paint on mobile went from 4.1 seconds to under one. The client’s team edits the same fields they always did.

We run the infrastructure, including the release process, so a busy season is a capacity decision rather than a crisis.

All case studies

Tell us what you are trying to ship.

A real technical opinion back within two business days — not a sales call.

Start a build