Skip to content
Mayrian

Website development

Fast, accessible, search-friendly websites on a CMS your team can update without a developer.

LighthouseElementsNetwork
https://northside-clinic.example/
96Performance
100Accessibility
100Best practices
100SEO

What we build

Websites we build

We build fast, accessible websites on a CMS your team can update without a developer, from marketing sites and content hubs to full replatforming projects.

  • Corporate and marketing sites

    Brand, services and content hubs your marketing team can update and extend.

  • Content-heavy sites

    News, resources and knowledge bases with search, filtering and structured content.

  • Web apps

    Logged-in areas, calculators and booking flows inside the public site.

  • Redesigns and replatforming

    Moving from an old CMS without losing content, search rankings or analytics history.

  • Multi-site and multilingual

    Several brands, regions or languages from one CMS and component library.

  • Landing pages and campaigns

    Campaign pages your marketing team builds from reusable blocks.

mayrian.com/team
A laptop showing a website on a wooden desk

How to get started

Three steps to a plan for website development

  1. 1Tell us what you needUse the project form or book a call. A few sentences about the goal is enough to start.
  2. 2Free technical consultationWe go through your goals, users, existing systems and constraints with you.
  3. 3Your planA detailed plan covering the right tech stack, architecture, timeline and budget. Then you decide.

How it works

Built for Core Web Vitals

We build and check every site against Core Web Vitals, measured from real visits. Set each metric to see its rating and what we'd fix.

3.4s

How quickly the main content appears. Good up to 2.5s; poor above 4s.

180ms

How quickly the page responds to taps, clicks and typing. Good up to 200ms; poor above 500ms.

0.18

How much the page jumps around while loading. Good up to 0.1; poor above 0.25.

Core Web Vitals assessment

Not passed

Google assesses the 75th percentile of real visits to your site. All three must be good to pass.

  • LCP: needs improvement. Optimize and preload the hero image, serve from a CDN, reduce server response time and render-blocking CSS.
  • INP: good. No action needed.
  • CLS: needs improvement. Set sizes on images and embeds, reserve space for ads and banners, and avoid inserting content above what's loaded.

Rendering, chosen page by page

We choose the rendering for each page. Switch between static, incremental, server and client rendering to see when content appears.

  • BuildHTML built once, at deploy
  • CDNCached HTML from the nearest edge
  • BrowserContent visible

Pages are built at deploy time and served from a CDN. Fastest and cheapest; content changes need a rebuild or revalidation.

Services

Website development services

Take one on its own, or combine them in one engagement with one team.

  • Website design and build

    Content structure, responsive design and a component library, built on Next.js, Astro or your CMS's own theme.

  • CMS implementation

    WordPress, Contentful, Sanity, Storyblok or Drupal, set up with roles, workflows and previews.

  • Migration and replatforming

    Content migrated, URLs mapped and 301 redirects in place, so search rankings carry over.

  • Performance, SEO and accessibility

    Core Web Vitals, structured data and WCAG 2.2 AA checks before and after launch.

Our approach

How the work runs

Each stage hands its output to the next, like the stages of a delivery pipeline.

  1. Stage 1

    Content and structure

    Content audit, sitemap and page templates based on what visitors need.

  2. Stage 2

    Design

    Responsive designs and a component library, checked for accessibility.

  3. Stage 3

    Build

    Components wired to the CMS, with rendering chosen per page for speed.

  4. Stage 4

    Migrate

    Content migrated, URLs mapped and 301 redirects set up.

  5. Stage 5

    Launch and measure

    Performance, accessibility and SEO checks, analytics and monitoring.

What we'll need from you

Having these ready keeps the work moving.

  • Content owner

    Someone who gathers, writes or approves content.

  • Brand assets

    Guidelines, logos, fonts and imagery.

  • Current site access

    CMS, analytics and Search Console access for the audit and redirects.

  • Editors for training

    The people who'll update the site, for training before launch.

Who's on the project

Our team, working with content owner from yours.

Deliverables

What you receive

Everything is handed over in your name: code, accounts and documentation.

CHANGELOG.md
  1. - Training and documentation for editors

What the documentation looks like

Every project ends with documents your team can run with. Here is an excerpt of one of them.

redirects.csvPreview

Old URLs to new, before launch

1,240 URLs mapped · top 5 by organic traffic shown

Old URLNew URLStatusVisits a month
/services.php?id=12/services/data-migration3013,410
/about-us.html/about3012,980
/blog/2021/05/guide/insights/migration-guide3012,150
/contact-us.html/contact3011,870
/careers/jobs.php/careers3011,120

Measuring success

How success is measured

What we report on in website development projects. Which measures apply, and their targets, are agreed with you at the start.

Core Web Vitals

Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, from real visits.

The launch preflight

Before launch, every check runs from the command line. Run it, fix what fails and run it again.

terminal

Press Run preflight to check the site before launch.

Readiness check

Are you ready for
website development?

Five questions, about a minute. You'll see what to settle first and a sensible starting point.

npx mayrian readiness --for "Website development"

? Do you know the site's main goals and audiences? (y / n / ?)

How to start

From first call to production

Start where you are. Each step ends with a decision, so you commit to the next one only when it makes sense.

git log --oneline --decorate

git show v0.1

Free technical consultation

Talk through the goal, the users, the systems involved and any deadlines.

  • + A clear view of scope and priorities
  • + A recommended next step
  • + A plan covering stack, architecture, timeline and budget
Book the consultation

Estimate the value

What it could be worth to you

Enter your own figures. The formula is shown, and the estimate can go with your enquiry.

estimate.yaml

# Revenue from a faster, clearer site

# formula: Visits × enquiry rate × improvement × value of an enquiry

$ mayrian estimate

Added enquiry value

$36,000

a month

1# => $36,000 a month
Add to my enquiry

Build or buy

When you don't need
a custom build

Part of the free technical consultation: when an existing product covers the need, we recommend it instead of a custom build. These are the options we weigh, alongside the tools you already have.

A custom build fits when

  • Brand and experience need a bespoke design system
  • Content is reused across web, apps and other channels
  • The site integrates with CRM, booking or product data
  • Speed and accessibility targets are strict

Technologies and standards

Chosen for your project

Content management systems differ in model and editing experience. Choose one to see when it fits.

WordPress

Open source, PHP; traditional or headless

Content-heavy sites with editors who know it; WordPress VIP for enterprise hosting.

Hosted on Vercel, Netlify or Cloudflare, or on your own cloud.

Our technology radar for website development

Adopt Trial Assess Caution
AdoptTrialAssessCautionTechniquesPlatformsToolsLanguages & frameworks

techniques / adopt

Feature flags

Separate deploying code from releasing it, so unfinished work can ship dark and be switched on gradually.

Our default. We use it on client projects unless there's a reason not to.

Our recommendations. Updated September 2026.

Frameworks

  • Next.js
  • Astro
  • Nuxt

CMS

  • WordPress
  • Contentful
  • Sanity
  • Storyblok
  • Drupal

Hosting

  • Vercel
  • Netlify
  • Cloudflare
  • AWS

Built to

  • Core Web Vitals
  • WCAG 2.2 AA
  • Schema.org structured data

Questions

Common questions
about website development

Do you build on WordPress or a headless CMS?

Both. We use WordPress for content-led sites with standard layouts, and a headless CMS such as Contentful or Sanity for structured content used across web, apps and other channels.

Will we lose our search rankings?

No. We map and redirect every URL, carry metadata over and make the new site faster, then monitor Search Console closely for the weeks after launch.

Can our team update it without developers?

Yes. Editors get page templates, reusable blocks and previews, with roles and approval workflows where needed.

How is a project priced?

Well-defined scopes are delivered as fixed-price engagements; when requirements are still evolving, we provide a dedicated team instead. Either way, the free technical consultation ends with a plan covering tech stack, architecture, timeline and budget, so you know the cost before work starts.