Websites

What you get

A website built the way an application is built: typed, tested, deployed by a pipeline and monitored after launch.

How it works

Edge and CDN in front, Next.js rendering with ISR behind it, a cached API or headless CMS for content, and PostgreSQL underneath. Images are converted, sized and served per device; fonts are self-hosted and subset.

What we measure

Core Web Vitals at p75 on mobile field data, accessibility against WCAG 2.2 AA, and the conversion events you care about.

What actually makes a site fast

Speed is decided by a handful of things, and most of them are settled before any code is written.

The largest element on the first screen should be text, not a hero image or a video. Text is in the HTML, so it paints as soon as the document arrives; anything that has to be fetched, decoded and laid out first pushes the number that Google measures. On this site the largest element is the headline, and that was a decision, not a happy accident.

JavaScript is the second lever. A page that ships a framework, an animation library, a carousel and three analytics tags spends its first second parsing instead of painting. We keep the initial bundle under a budget the build fails on, so a dependency added in a hurry cannot quietly cost a second.

The third is images. Converted to modern formats, sized for the device that asked, and given explicit dimensions so nothing jumps while they load.

What does not make a site fast: a faster host, a caching plugin, or removing a stylesheet. Those are the fixes people reach for because they are easy, and they move the number by a few percent.

What we need from you

Content is the long pole on almost every website, so it helps to know that early. Final copy and real images for the pages that matter — not all of them, but the homepage and the top two or three — let us build against the real thing instead of placeholder text that hides layout problems until launch week.

If you have a brand, we work inside it. If you do not, we will set type, colour and spacing as part of the build rather than treat it as a separate project.

Where a website stops being a website

If a page needs a user to sign in, if it stores something a person comes back to, or if it has to talk to a system you already run, it is an application wearing a website's clothes. That is a web application build with different foundations, and recognising it early is cheaper than discovering it in month three.