Built, not assembled.
Most small business websites are a bought template with twenty plugins holding it together. They load slowly, they fail accessibility, and they convert badly. All three are consequences of how the thing was made.
- Custom build, no page builder
- LCP under 2.5s, WCAG 2.2 AA
- Everything, documented
Speed is not a plugin you install at the end.
A page builder gives you drag and drop at the cost of markup. Every element wraps in several nested containers, every feature loads its own stylesheet and script, and the page arrives at the visitor carrying hundreds of kilobytes it never needed.
You can then buy a caching plugin and an optimisation plugin to compress the mess, which helps, and you are still shipping a page several times heavier than it needed to be.
Accessibility goes the same way. Contrast, focus states, heading order, touch targets and keyboard navigation are either designed in or retrofitted badly. Retrofitting is always more expensive.
This site is the example. One stylesheet, self-hosted fonts, no page builder, animation that degrades to a perfectly usable page.
We build client sites the same way, and we will show you the numbers rather than claim them.
Design for the decision, build for the metric.
Structure first. What the visitor needs to know, in what order, to decide. Most pages fail because they lead with what the business wants to say rather than what the buyer needs to resolve.
Then the build. Semantic HTML, a real design system rather than one-off styles, responsive images that serve a phone a phone-sized file, fonts hosted on your own domain, and JavaScript that enhances rather than gates the content.
Then measurement. Form submissions, calls, WhatsApp clicks and enquiry events tracked properly, so you can tell which pages actually produce business rather than guessing from traffic.
We will tell you when you do not need a new site. Sometimes the existing one needs three fixes rather than a rebuild.
That is a cheaper answer and often the right one.
Deliverables.
Discovery and structure
What each page has to do commercially, and the order the content needs to be in to do it. Agreed before any design work starts.
Design system
Type scale, colour tokens, spacing and components defined once and reused, so the site stays consistent as it grows.
Custom build
Semantic markup, responsive images with proper srcset, self-hosted fonts, and a theme written for your site rather than configured from a template.
Accessibility
WCAG 2.2 AA practices applied during the build: heading order, focus indicators, contrast, keyboard navigation, reduced motion support.
Performance
Core Web Vitals treated as a budget set before development, not a score chased afterwards.
Handover
You can edit every headline, image and block without touching code, and the build is documented so another developer could pick it up.
How a build runs.
Diagnose
Current performance, current conversion rate, current accessibility faults, and what the existing site is actually failing at. Recorded as the baseline.
Structure
Sitemap and page-by-page content order, signed off before anything is designed.
Design
Applied to real content, not placeholder text, so the layout survives contact with reality.
Build
In the open, on a staging URL you can watch, with nothing going live until you have seen it.
Measure
Post-launch verification of speed, accessibility, forms, tracking and the conversion rate against the recorded baseline.
Building for a Manchester audience.
Two things decide whether a regional service website works, and neither is the design. The first is how fast it loads on a mid range phone on mobile data, because a large share of the traffic arrives from a map result on a handset, often from a van or a building site.
The second is local credibility above the fold. A visitor who found you by searching for a supplier near them is checking one thing first: are these people actually here, and have they done this before for someone like me. An address, a phone number with the right dialling code, areas served and recognisable local work answer that in two seconds.
Everything after those two is ordinary good building. Accessible, fast, easy for your team to edit, and owned by you rather than rented from whoever built it.
Fast on a phone, on mobile data, in a van.
Local credibility above the fold, not in the footer.
Straight answers.
Do you use WordPress?
Usually yes, because you need to be able to edit it. But we build a theme for your site rather than buying a multipurpose one and configuring it, and we avoid page builders. You keep the editing convenience without the weight.
How long does a site take?
A focused brochure site is usually weeks rather than months. The variable is almost never the build, it is how long content and sign off take. We will give you a date and tell you what we need from you to hold it.
Can I edit it myself afterwards?
Yes, and that is a requirement we design for rather than an afterthought. Headlines, body copy, images, services, case studies and posts are all editable without code.
What about my existing rankings?
Preserved deliberately. We inventory every indexed URL before the build, decide keep, improve, merge or redirect for each, and put a redirect map in place before launch. Rebuilds lose rankings when nobody does this.
Do I need to rebuild at all?
Possibly not. We will audit what you have first and tell you honestly whether the problem is the site or something else, such as where your traffic comes from or what happens after an enquiry arrives.
Where this connects.
Tell us what’s next.
Send over the problem and the numbers you have. We will tell you honestly whether we are the right people for it.