Website development & maintenance

A website that loads fast, says something, and keeps working.

Most business sites fail in one of two ways: they are slow and unreadable on a phone, or they look fine and nobody can update them. We build sites that are quick on a mid-range phone over mobile data, that a search engine can read, and that you can change without calling us for every price update.

Start a conversation

You might need this if

  • The site takes several seconds to show anything on a phone.
  • Editing a phone number means emailing a developer.
  • The contact form either does not work, or sends to an inbox nobody monitors.
  • The site was built on a page builder whose licence expired.
  • It scores badly on Core Web Vitals and nobody knows which part is responsible.
  • It is not usable with a keyboard or a screen reader.

What the work covers

Not every engagement includes all of this. The scope is agreed in writing before anything starts.

  • Business websites

    Marketing and service sites built with Next.js or a comparable framework, statically rendered where possible so the first paint does not wait on JavaScript.

  • Landing pages

    Single-purpose pages for a campaign or a service, with the form actually wired to somewhere you will see it, and conversion events you can measure.

  • Performance work

    Measuring first, then fixing what the measurement found: image formats and sizing, font loading, render-blocking resources, oversized bundles and layout shift.

  • Accessibility

    Semantic structure, keyboard operability, visible focus, sufficient contrast and labelled form errors — targeting WCAG 2.2 AA.

  • Migrations and rebuilds

    Moving off an unmaintainable platform while preserving URLs and search rankings, with redirects mapped before the switch rather than after.

  • Ongoing maintenance

    Dependency and security updates, content changes, uptime monitoring and periodic performance checks on an agreed cadence.

How we approach it

  1. 01

    Agree what the site is for

    One primary action per page. A site that tries to do six things on the homepage does none of them.

  2. 02

    Content before layout

    We write or edit the actual copy first. Designing around placeholder text produces layouts that break the moment real content arrives.

  3. 03

    Build mobile-first

    Layouts are built and reviewed from 320px upward, not designed at desktop width and squeezed down afterwards.

  4. 04

    Measure, then optimise

    Lighthouse and field data before and after. We report the numbers we actually measured, including the ones that did not improve.

  5. 05

    Hand over editable

    You get the repository, the deployment configuration and documentation for whatever you will need to change yourself.

What you end up with

  • A responsive site verified from 320px to 1920px with no horizontal overflow
  • Before-and-after Lighthouse scores for performance, accessibility, best practices and SEO
  • Working forms with server-side validation and spam protection
  • Page titles, descriptions, canonical URLs, sitemap, robots rules and structured data
  • A redirect map, where the project replaces an existing site
  • Source repository and deployment documentation handed to you

Technologies involved

Tools and standards this work is carried out with — listed because they are what the job uses, not as a claim of vendor partnership.

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • WordPress
  • Vercel
  • Cloudflare
  • Playwright
  • Lighthouse

On client examples: we do not publish case studies, logos or testimonials without written permission from the client, and we have none cleared for publication yet. If you need evidence of relevant work before engaging, ask — we will share what we can, appropriately redacted, and say plainly where something was a lab build rather than a client engagement.

Questions about this service

Will I be able to edit the site myself?

That depends on what you want to edit, and we agree it before building. Frequently-changing content goes somewhere you can reach without a developer. Layout and structure stay in code, because page builders that let you change anything are also the ones that let you break anything. We tell you which is which before you commit.

Do you guarantee a Lighthouse score of 100?

No. Lighthouse scores vary between runs and depend on the test device, the network and any third-party scripts you need — an analytics tag or a chat widget can cost ten points on its own. We target 90+ on each category in lab conditions and report the measurements we actually took, including the ones we could not improve.

Will a rebuild hurt our search rankings?

It can, if URLs change without redirects. We map every existing URL to its new destination before launch, keep page titles and content intent intact, and submit an updated sitemap afterwards. A short fluctuation while search engines re-crawl is normal; a sustained drop usually means something was missed, and we check for it.

Do you work with WordPress?

Yes, for maintenance, performance work and migrations off it. For new builds we usually recommend a statically rendered framework instead, because the ongoing security and plugin-maintenance burden of WordPress is a real cost that rarely gets priced in.

Need a site built, rebuilt or rescued?

Send the URL if one exists, or a description of what it needs to do. We will come back with what we would change, in what order, and why.

Get in touchHow an engagement works

Related services