Hand-built websites, engineered to load fast and stay fixed.

We pick the stack to suit the site, not the other way round

A brochure site that changes twice a year and a platform that changes twice a day are different problems, and putting both on the same stack is how projects end up slow or unmaintainable.

For marketing and portfolio sites we usually build with Astro, which ships static HTML with almost no JavaScript. The result loads in well under a second and there is nothing on the server to be exploited. For sites where a non-technical team needs to publish constantly, WordPress is still the right answer, and we build it properly - custom theme, no page-builder bloat, and only the plugins that earn their place.

Where a project genuinely needs an application rather than a website, we build custom. What we will not do is reach for the heaviest option by default and bill you for the complexity.

Core Web Vitals are a build decision, not a plugin

Speed cannot be retrofitted with a caching plugin once the site is already loading four megabytes of unused framework. It comes from decisions made early: how images are served, how fonts are loaded, how much JavaScript ships at all.

Every build gets modern image formats at the right dimensions, deferred and preconnected fonts, hard caching on fingerprinted assets, and compression configured at the server. We test against Core Web Vitals on a throttled mobile connection before launch, not on the office fibre.

Search engines get what they need, from the first deploy

Clean semantic markup, one H1 per page, a real heading hierarchy, canonical tags, an auto-generated sitemap, Open Graph cards and structured data are part of the build rather than an SEO retrofit six months later.

When we replace an existing site we map the old URLs to the new ones and put permanent redirects in place, so the ranking and backlinks you already earned carry across instead of dying with the old site. This is the step most rebuilds skip, and it is the most expensive one to skip.

A handover you can actually use

You own the code and the hosting account at the end of the project. No proprietary builder you can only edit by paying us, no licence that lapses if you leave.

You get a walkthrough of how to update your own content, written documentation for anything non-obvious, and a person to email when something breaks. If you want us to keep looking after it, that is a choice you make afterwards rather than a dependency we engineered in.