All services

Web Development

/overview/

The speed of a static site, with the control of a CMS.

The approach

/intro/

We build headless by default, with an Astro front end: pages are generated ahead of time and served as finished HTML, so a visitor gets the whole page instead of waiting on a database. Almost any CMS can be made headless, and most of ours are, Umbraco, WordPress, Drupal, Shopify and BigCommerce among them, so your team keeps the editing screen it already knows while the site itself stays fast. The result is lightning fast websites with almost perfect Google Performance Scores and a tiny attack surface.

What we deliver

/included/
  • 01

    UX, content and interface design

    Wireframes, page structure and a visual system built around the decisions your visitors have to make. Templates come later, if at all.

  • 02

    Development on the platform that fits

    Shopify, BigCommerce, WordPress, Drupal, Umbraco, Moodle, a headless CMS with a pre-rendered front end, or something custom. Picked for your content, your integrations, and whoever has to maintain it afterwards.

  • 03

    Performance and accessibility passes

    Core Web Vitals, image handling, keyboard navigation and colour contrast, all checked before launch. Clients usually find these things through their own customers otherwise.

  • 04

    Ongoing support and maintenance

    Updates, security releases and content publishing, from a named team that already knows how your site was built.

Why these sites hold up

Five things that come as part of the build, not as extras on the quote.

/in detail/
  • 01

    A headless build, in plain terms

    Content lives in a CMS and reaches the site over an API, so the editing screen and the front end are separate things. Editors get a form with only the fields that matter. The front end is Astro, which builds each page ahead of time and serves it as finished HTML, so nobody waits on a database call for a page that never changes between visits. It is our default because one set of content can then go straight out to the site, an app, a listing, a screen in a branch or a second brand without being rebuilt each time, and because any of the CMSs above can be fronted that way. The one case where we would not: a handful of pages, no reuse, no speed problem, and a budget better spent on the words than on the plumbing. We will say so at the point it matters.

  • 02

    Fewer ways in

    Most sites are not broken into through the page. They are broken into through a login screen, an old plugin, or a database left open to the internet. A pre-rendered front end has none of those: no admin path to find, no plugin directory, no database behind the page, just files served over TLS. Fewer parts means less to patch. Where a CMS still has to be reachable, it goes behind access control, dependencies are kept current, and someone watches it.

  • 03

    Fast on a real phone, not just on ours

    HTML written ahead of time and served from somewhere near the visitor, images cropped and converted for each screen size, third-party scripts deferred or removed. We test on a throttled phone rather than an office fibre line, and we set a budget before launch: usually under two seconds on mobile, Lighthouse in the nineties. People leave when a page stalls, and they rarely come back to check whether it improved.

  • 04

    Google Business Profile, kept in step with the site

    Categories, services, hours, photos, posts, questions and review replies, kept current and matching what the site itself says, because Google compares the two. Calls and direction requests are tracked with tagged links, so local visibility gets measured instead of guessed at. For a business that serves one region, this is often the cheapest work on the list with the clearest effect.

  • 05

    An AI builder, for the jobs it suits

    We built one, and we use it where the brief is narrow: a clear offer, a modest budget, and someone inside the business who would rather edit their own copy than book a meeting. Page count is not the limit it sounds like, and it is not a short-run tool. Nor is speed the reason to choose it, because every site we deliver goes live in a short window, whether it is drawn and coded by hand or assembled this way. What it does not suit is a complex content model, a site with booking or memberships built in, or a brand where the design is the thing that sells. Those still get drawn and coded by hand.

    Worth knowing

    Not sure which is the best approach for your needs? A quick conversation can help determine the right path.

Structure before decoration

A well-built site is most of the way to being found. None of this is a separate project bolted on at the end; it is how the pages get made.

/seo + aeo/
  • 01

    Markup a search engine can follow

    Each page gets one H1 that says what it is, and a heading order that means something. Lists and tables are built as lists and tables rather than styled divs, and link text says where it goes instead of saying "read more". URLs stay short and readable. Sitemaps and canonicals are generated rather than maintained by hand, old addresses redirect straight to the new one with no chain of hops, and internal links are placed where they do work, so authority lands on the pages that need to rank rather than disappearing into the footer.

  • 02

    Structured data for what is actually on the page

    We mark up the things that exist: Organization and LocalBusiness, Service, Product, Article, Breadcrumb, and FAQ where there are real questions with real answers. Only true values go in. No invented review counts, no stars nobody left, no hours we have not confirmed. Each block is validated before launch and checked again whenever the page changes, because broken markup does more harm than none.

  • 03

    AEO: writing an answer engine can quote

    Assistant results and featured answers tend to favour pages that answer early and plainly. Each page leads with the answer in its first sentence or two, then backs it up with detail, a definition, a short FAQ, or a comparison table where a table is honestly the right shape. Your name, address, hours and service names stay identical across the site and every listing, because that repetition is how a model works out you are the same business everywhere it reads. When a page changes, its updated date changes with it.

  • 04

    Audits on a schedule

    Every quarter we crawl the site and check index coverage, broken links, redirect chains, duplicate titles and descriptions, structured data, Core Web Vitals, and whether it still works with a keyboard. You get a short list in plain language, each item with an owner and a date, not a ninety-page export. If something urgent turns up, a page dropping out of the index or a form failing on a phone, you hear about it that day.

How we work

/process/
  1. 01

    Discovery

    We look at the current site, talk to the people who maintain it, and agree on the one thing the new one has to do better.

  2. 02

    Design and build

    A working design in the first two weeks, then build and review in short rounds with your team.

  3. 03

    Launch and care

    Migration, redirects, analytics and a support plan, so launch week is not the week something breaks.

  • 6

    platforms we build on daily

  • 2 wks

    to first working design

  • 24/7

    monitoring on support plans

Proof of the work

/case study/
Scotty Cameron project by MAD Development
Sporting GoodsUmbraco2024

Scotty Cameron

Umbraco implementation and ongoing management for the most collected putters in golf.

We built the site on Umbraco and still look after it: a component library their team publishes with, and a support crew that already knows how it was built.

Need a website built properly?

Tell us what you are working on. We will come back with a straight answer on scope, timeline and budget.

Let's chat

Other services

/5/