Web Design
Sites that look the part, load in half a second and are built to convert.
A rebuild that looks better can still earn less. The design gets signed off, the build goes to whoever’s free, and the search work starts after launch, by which point the URL structure, the heading order and the page weight are already locked in. Fixing those afterwards costs more than getting them right in week one.
So we don’t split the job up. The same person makes the design call, the performance call and the SEO call, usually on the same day.
The design still has to be good
If the design is the part you care about most, you’re not wrong. A site that looks cheap loses the enquiry before anyone reads a word, and no amount of technical work rescues that. Every build gets a real design pass: a considered type scale, deliberate spacing, and artwork made for your business instead of the stock photo your competitor already bought.
Then we make it earn its keep. Each page is built around one action we want the visitor to take, and anything that doesn’t help that action comes off. That’s the difference between a site people compliment and a site that fills your inbox.
What’s included
One job per page
We start with what each page is for and the single thing a visitor should do on it. Layout follows from that. A page trying to do five things is a page where visitors do none of them.
Fast, and you can check it yourself right now
Google’s own Lighthouse tool scores this page 100 out of 100 on all four categories: performance, accessibility, best practices and SEO. Largest Contentful Paint 0.5 seconds, total blocking time 10 milliseconds, cumulative layout shift 0.001.
Go and check. Open Chrome, press F12, click the Lighthouse tab and run it on this page. We’d sooner show you than describe it.
Those numbers come from self-hosted fonts, no render-blocking requests, images served in modern formats at the size they’re displayed, and no third-party scripts loaded for the sake of it.
Designed on the phone first
Most of your visitors are on a phone, often on patchy mobile data, often one-handed. We design for that screen first and let the desktop layout grow out of it. A surprising number of sites are still built the other way round, and you can feel it the moment you pick one up.
SEO foundations built in
Clean semantic markup, a sensible URL structure, correct heading hierarchy, structured data, and an information architecture that gives your content somewhere logical to live as the site grows. None of this is visible to a visitor. All of it decides whether your SEO work compounds or fights the platform.
Accessibility done properly
Real colour contrast, keyboard navigation that works, focus states you can see, alt text that means something, and forms a screen reader can complete. It’s the right thing to do, and search engines reward a lot of the same signals.
Your rankings survive the move
If we’re replacing an existing site, every old URL gets mapped and redirected, your analytics history stays intact, and we watch Search Console closely for weeks afterwards. Rebuilds cost people their rankings when that step gets skipped. We treat it as part of the build.
The stack, and why it matters to you
Most of our recent builds are static sites deployed to a global edge network. In practical terms: your pages are pre-built and served from a location near your visitor, instead of being assembled on demand by a server in another state.
What that buys you is the load time above, hosting that costs a fraction of a traditional plan, and an attack surface close to zero, because there’s no database or admin login sitting on the public internet waiting to be probed.
It isn’t the right fit for everything. Complex logged-in functionality, live inventory and large ecommerce catalogues have different requirements, and we’ll tell you when your project is one of those instead of forcing it into the tooling we prefer.
Who this is for
Businesses replacing a site that has quietly stopped earning its keep, or launching a new one and wanting the design and the search performance decided together from the beginning. Particularly if the last rebuild cost you rankings and you’d rather that didn’t happen twice.
Common questions
Will I be able to update the site myself?
If you want to, yes. Tell us that up front and we'll build it with a content management system fitted to how you actually work, plus a walkthrough of the parts you'll touch. Most of our clients don't want that though. They'd rather email or call us and have the change made, which is included, so nobody has to remember how a CMS works twice a year.
Do you build on WordPress?
We can, and for a first site it's a reasonable place to start. It's cheap to get going and there's a plugin for everything. The trouble is what it costs you later: every plugin is code from a stranger with access to your whole site, updates break things, and performance degrades as the stack grows. Newer technologies have moved well past it. A modern static build has no database to attack, no plugins to patch, loads faster and needs a fraction of the maintenance. We pick based on what the site needs to do, not on what we feel like building, but we'll usually recommend the newer approach and tell you why.
What happens to my rankings when the site changes?
Nothing, if the migration is done properly: a complete URL map, 301 redirects for every legacy address, and monitoring for the weeks afterwards. Rankings get lost in rebuilds because that work gets skipped, not because rebuilding is inherently risky.
How long does a build take?
A focused brochure site is usually four to six weeks. Anything with custom functionality depends on the functionality. We'll give you a real timeline before you commit, not an optimistic one.
Go deeper
Worth reading on this
How to build a solid site structure for SEO
Site architecture is decided early and expensive to change later. How to plan hierarchy, URLs, internal linking and topic clusters so your content has somewhere sensible to live.
Website speed is an SEO problem, not just a UX one
Site speed affects rankings directly, and affects them again indirectly through visitor behaviour. Here's how the two connect.
Technical SEO: making sure search engines can actually read your site
The technical layer beneath your content: crawling, indexation, robots directives, sitemaps, canonicals and Core Web Vitals, and how to tell which is broken.
Other services
Ready to stop guessing and start getting enquiries?
Tell us about your site and we'll show you, in plain terms, where you're losing visibility. No obligation, no jargon.
Get your free visibility audit