Core Web Vitals in the contractWebsite Development

A website is judged by Google, by people, and now by machines.

Q: How much does a website cost?

Scope drives the number, so we quote after the audit rather than publishing a figure that fits nobody. A focused marketing site on a headless CMS with ten to fifteen templates sits at the low end of a fixed-scope engagement. A multi-language, multi-region site with a design system, editorial workflow, and thousands of migrated URLs sits at the high end. Either way you get a fixed scope and a fixed price before any code is written.

Q: Astro, React, WordPress, or headless. How do you choose?

The brief chooses. Astro when content is the product and every millisecond of load counts. React when the site carries configurators, calculators, or heavy interaction. WordPress when your team already lives in it and editorial velocity matters more than novelty. Headless, usually Sanity, when the same content has to feed a site, an app, and a partner channel at once. We write the recommendation down with the trade-offs, and we will tell you when the boring choice is the right one.

Q: Will we lose search rankings when we replatform?

Not if the migration is done properly. We crawl the existing site, map every indexed URL to its destination with 301s, preserve titles, metadata, and structured data, and keep the redirect map under monitoring for ninety days. Search Console impressions are compared week over week against a pre-launch baseline, so a dip is caught in days rather than discovered in a quarterly report.

Q: What is AEO and GEO, and why are they on this page?

AEO is answer engine optimisation: structuring content so featured snippets, voice assistants, and AI answer panels can lift an accurate answer. GEO is generative engine optimisation: making your pages citable by ChatGPT, Perplexity, Google AI Mode, and Copilot. Both depend on the same engineering as good SEO, clean semantic HTML, complete structured data, stable canonical URLs, and machine-readable summaries, which is why we build for them rather than bolt them on afterwards.

Q: How do you prove the site meets Google's standards?

Field data, not screenshots of a lab score. We set LCP, INP, and CLS budgets at architecture stage, enforce them in CI so a regression fails the build, and report the 75th percentile mobile numbers from real users after launch. Accessibility is verified against WCAG 2.2 AA with assistive technology, not only automated checks, and structured data is validated on every template.

Q: Do you design the site as well as build it?

Yes, and the same team does both. Research and content inventory, information architecture, wireframes, then a design system in Figma, built by the engineers who sat in the design reviews. Design that cannot hold its performance budget is not finished, so both disciplines work from one backlog rather than throwing files over a wall.

Q: Can our marketing team edit pages without a developer?

That is the point of the CMS work. We model content as reusable blocks with guardrails, so marketers compose new pages from approved components without breaking layout, performance, or accessibility. Editors get preview, scheduled publishing, and role-based approvals, and we train the team on the model rather than handing over a manual.

Q: How long does a website project take?

A focused marketing site typically runs eight to twelve weeks from kickoff to launch. Larger programmes with a design system, multi-locale content, and a substantial migration run four to six months. The audit is the first two weeks either way, and we do not start production build until the URL map, content model, and design system are signed off.

Q: What happens after launch?

Field vitals, rankings, and AI citation checks are monitored, and the iteration backlog is driven by what that data says. Retainer clients get template work, campaign pages, CRO experiments, security patching, and monthly reporting on traffic and conversion from the same pod that built the site, so context does not reset every quarter.

We design and build marketing and corporate websites on Astro, React, WordPress, and headless CMSs. Fast by architecture, accessible by default, and structured so search engines and AI answer engines can read, rank, and quote you.

Get a Free Audit See the work

15+ yrsBuilding websites for brands and enterprises

4Stacks in production: Astro, React, WordPress, headless

450+Engineers and designers in house

100+Sites shipped across marketing, ecommerce, web apps

What we do

Website design, development, and migration.

We take websites end to end: research and information architecture, design systems in Figma, then the build on the stack your brief actually calls for. Astro when content and speed are the product. React when the site carries real interaction. WordPress when editorial velocity matters. Headless with Sanity when the same content has to serve a site, an app, and a partner channel. Every build ships against measured Core Web Vitals, WCAG 2.2 AA, and structured data complete enough for search engines and AI answer engines to quote.

Where this fits

Websites, web applications, and storefronts are different jobs.

If you are not sure which one you need, that is a five-minute conversation, not a proposal.

You are here

Website Development

Marketing, corporate, and content sites. Anonymous visitors, editorial workflow, search and AI discoverability, conversion.

Astro · React · WordPress · headless CMS

Different page

Web Application Development

Logged-in products: dashboards, portals, workflow tools. Authentication, roles, state, and platform load.

Go to web applications →Different page

Ecommerce

Selling online at volume: catalogue, checkout, payments, fulfilment integrations on Shopify and Shopify Plus.

Go to ecommerce →

Key Challenges

What quietly costs you traffic and trust.

Slow pagesSpeed you only notice in the analyticsHeavy themes, unoptimised media, and third-party scripts push you outside Google's Core Web Vitals thresholds. Failing field vitals costs ranking and conversion at the same time.

Invisible to AIAI answers about you, without youAnswer engines summarise your market from pages they can parse. Thin markup and missing schema leave you out of the citation. The referral you never see is the one you cannot optimise.

CMS frictionEvery page change needs a developerRigid templates and unmodelled content turn a copy tweak into a ticket, so campaigns wait on release cycles. Marketing velocity drops to the speed of your deploy queue.

Compliance riskAccessibility found in a legal letterContrast failures, keyboard traps, and unlabelled controls are cheap to prevent and expensive to discover late. Remediation after launch costs multiples of doing it in design.

Why Devsinc

Built to a standard you can measure, not a template you have to defend.

Performance budgets, not promises

LCP, INP, and CLS targets are set at architecture stage, enforced in CI, and monitored on field data after launch. A regression fails the build, not the quarterly review.

Accessibility inside design

Contrast, focus order, and semantics are reviewed in Figma before build. WCAG 2.2 AA is a design constraint here, not a retrofit.

The stack matches the brief

Astro, React, WordPress, or headless. We write the recommendation with trade-offs and tell you when the boring choice wins.

Migrations that keep your rankings

Full crawl, URL map, 301s, preserved metadata and schema, then ninety days of redirect and Search Console monitoring against a pre-launch baseline.

Editors get real autonomy

Content modelled as guarded blocks with preview, scheduling, and approvals, so marketing composes pages without breaking layout or vitals.

One team, design through support

The engineers who ship sat in the design reviews, and the same pod stays on for iteration after launch.

What we build

Eight things we are asked for most.

Website design

Research, information architecture, wireframes, and a design system your brand can extend without us.

Website development

Production builds on Astro, React, WordPress, or headless, to a performance and accessibility budget.

Headless CMS builds

Sanity and comparable CMSs modelled as reusable blocks, with preview, scheduling, and role-based approvals.

Replatform & migration

Move off a legacy stack with URL mapping, content migration, and a rehearsed cutover that protects rankings.

Technical SEO engineering

Crawlability, canonicals, sitemaps, internal linking, and complete structured data, built into the templates.

AEO & GEO readiness

Machine-readable summaries, entity clarity, and citable page structure so answer engines and AI models quote you correctly.

Core Web Vitals remediation

Diagnose and fix field vitals on the site you already have, without a full rebuild where one is not warranted.

Accessibility audit & fixes

WCAG 2.2 AA review with an annotated report, prioritised fixes, and regression checks in the pipeline.

Platforms & frameworks

Four stacks, and the honest case for each.

We do not have a house framework to sell you. The recommendation is written down with trade-offs before you commit, and we will tell you when the boring choice is the right one.

Astro

Content-first sites that ship almost no JavaScript by default. Islands hydrate only the components that genuinely need interaction.

Choose it whenContent is the product and every millisecond of load counts: marketing sites, documentation, editorial, campaign hubs.Trade-offHeavily interactive, app-like sections need deliberate island design rather than a blanket framework.

Islands architectureContent collectionsMDXEdge or static

React

Component-driven builds, usually with Next.js, when the site carries configurators, calculators, or heavy state.

Choose it whenThe marketing site has product-like surfaces: pricing configurators, interactive tools, gated content, personalisation.Trade-offMore JavaScript to budget for. Vitals work becomes a deliberate part of the build, not a side effect.

Next.jsApp RouterISRDesign system in code

WordPress

A first-class option, engineered properly: custom blocks, no page-builder bloat, and a hardened, patched deployment.

Choose it whenYour team already lives in WordPress, editorial velocity matters, and plugin ecosystem coverage is a genuine advantage.Trade-offPerformance and security depend on discipline. We keep the plugin surface small and the block library custom.

Custom blocksACFHeadless WP optionManaged hosting

Headless CMS

Sanity most often, plus Contentful, Storyblok, and Payload. Content modelled once, delivered to any channel through an API.

Choose it whenThe same content has to feed a website, an app, and a partner channel, or several brands and locales share one library.Trade-offContent modelling is real up-front work. Done well it pays back on every launch after the first.

SanityContentfulStoryblokPayload

Already on one of these and unhappy with it? Migration is a scoped project with a rehearsed cutover, not a rebuild you fund twice.

Scope a migration

UI/UX process

Design and engineering share one backlog.

Research & content inventory

Analytics, Search Console, and a full crawl of what you have, plus interviews with the people who publish and the people who buy.

Output: audit, page-level keep/merge/kill list

Information architecture

Navigation, URL structure, and templates mapped to search intent and the journeys that actually convert.

Output: sitemap, URL map, template inventory

Wireframes & content design

Layout and copy structure resolved together at low fidelity, so hierarchy is argued about before anything looks finished.

Output: annotated wireframes, content model draft

Design system

Type scale, colour with contrast checked, spacing, components, and states in Figma. Accessibility reviewed here, not later.

Output: Figma library, tokens, component specs

Build & CMS modelling

Components built to the spec, content modelled as guarded blocks, performance budgets enforced on every pull request.

Output: production build, editor guardrails, CI checks

QA, launch & iterate

Cross-browser and assistive-tech testing, redirect verification, then a post-launch backlog driven by field data.

Output: launch checklist, field monitoring, iteration plan

Standards & discoverability

Compliant with Google. Readable by machines.

Search is no longer the only reader. The same engineering that satisfies Google's page experience signals is what lets answer engines and AI models quote you accurately, so we treat it as one workstream with four outputs.

GOOGLE

Page experience compliance

The signals Google actually measures, treated as build criteria rather than a post-launch report.

Core Web Vitals on field data, not lab scores
Mobile-first rendering and responsive parity
HTTPS, crawl budget, and clean canonicals
No intrusive interstitials or layout traps

SEO

Technical search engineering

The parts of SEO that live in the code, built into templates so content teams inherit them for free.

Semantic headings, one H1, descriptive links
XML sitemaps, robots, hreflang for locales
Schema.org for Organization, Service, Article, FAQ
Internal linking and pagination that crawlers follow

AEO

Answer engine optimisation

Structuring content so snippets, voice assistants, and AI answer panels can lift an accurate answer.

Question-led headings with direct answers
FAQPage and HowTo markup where it is truthful
Concise definitions near the top of the page
Tables and lists machines can parse

GEO

Generative engine optimisation

Making your pages citable by ChatGPT, Perplexity, Google AI Mode, and Copilot rather than paraphrased away.

llms.txt and machine-readable page summaries
Entity clarity and consistent naming across the site
Stable URLs and dated, attributable content
Original data and quotes worth citing

< 2.5sLCP target, 75th percentile mobile

< 200msINP target, 75th percentile mobile

< 0.1CLS target, 75th percentile mobile

WCAG 2.2 AAAccessibility conformance standard

90 daysRedirect and ranking monitoring after launch

Process

From audit to launch, then after.

01AuditTwo weeks on your site, analytics, and content. We benchmark field vitals, accessibility, structured data, and AEO and GEO readiness, then rank fixes by traffic and revenue impact.

02Architecture & designInformation architecture, URL map, content model, and the platform decision, alongside the design system. Signed off before anyone writes production code.

03Build & migrateComponents built to budget in sprints, content migrated with reconciliation, then a rehearsed cutover with 301s verified and rollback points agreed.

04Monitor & iterateField vitals, Search Console, and AI citation checks after launch, with an iteration backlog and monthly reporting on traffic, rankings, and conversion.

Engagement models

Three ways to start.

Get a Free Audit

Fixed scopeAudit & roadmapA short engagement that benchmarks the site you have and returns a costed, sequenced plan across performance, SEO, AEO, GEO, and accessibility.Best when you need evidence before you fund a rebuild.

Project basedDesign & buildEnd-to-end ownership from research and design system through build, migration, launch, and handover on the platform your brief calls for.Best for a new site, a rebrand, or a replatform.

OngoingGrowth retainerA standing pod for template work, campaign pages, CRO experiments, vitals monitoring, security patching, and content operations.Best when the site is a channel you keep investing in.

Tech stack

The tools behind the builds

Build & front end

AstroReactNext.jsTypeScriptTailwindVercel

CMS & measurement

SanityWordPressContentfulStoryblokSearch ConsoleGA4

FAQs

Website questions clients actually ask

Get a Free Audit

How much does a website cost?+

Scope drives the number, so we quote after the audit rather than publishing a figure that fits nobody. A focused marketing site on a headless CMS with ten to fifteen templates sits at the low end of a fixed-scope engagement. A multi-language, multi-region site with a design system, editorial workflow, and thousands of migrated URLs sits at the high end. Either way you get a fixed scope and a fixed price before any code is written.

Astro, React, WordPress, or headless. How do you choose?+

The brief chooses. Astro when content is the product and every millisecond of load counts. React when the site carries configurators, calculators, or heavy interaction. WordPress when your team already lives in it and editorial velocity matters more than novelty. Headless, usually Sanity, when the same content has to feed a site, an app, and a partner channel at once. We write the recommendation down with the trade-offs, and we will tell you when the boring choice is the right one.

Will we lose search rankings when we replatform?+

Not if the migration is done properly. We crawl the existing site, map every indexed URL to its destination with 301s, preserve titles, metadata, and structured data, and keep the redirect map under monitoring for ninety days. Search Console impressions are compared week over week against a pre-launch baseline, so a dip is caught in days rather than discovered in a quarterly report.

What is AEO and GEO, and why are they on this page?+

AEO is answer engine optimisation: structuring content so featured snippets, voice assistants, and AI answer panels can lift an accurate answer. GEO is generative engine optimisation: making your pages citable by ChatGPT, Perplexity, Google AI Mode, and Copilot. Both depend on the same engineering as good SEO, clean semantic HTML, complete structured data, stable canonical URLs, and machine-readable summaries, which is why we build for them rather than bolt them on afterwards.

How do you prove the site meets Google's standards?+

Field data, not screenshots of a lab score. We set LCP, INP, and CLS budgets at architecture stage, enforce them in CI so a regression fails the build, and report the 75th percentile mobile numbers from real users after launch. Accessibility is verified against WCAG 2.2 AA with assistive technology, not only automated checks, and structured data is validated on every template.

Do you design the site as well as build it?+

Yes, and the same team does both. Research and content inventory, information architecture, wireframes, then a design system in Figma, built by the engineers who sat in the design reviews. Design that cannot hold its performance budget is not finished, so both disciplines work from one backlog rather than throwing files over a wall.

Can our marketing team edit pages without a developer?+

That is the point of the CMS work. We model content as reusable blocks with guardrails, so marketers compose new pages from approved components without breaking layout, performance, or accessibility. Editors get preview, scheduled publishing, and role-based approvals, and we train the team on the model rather than handing over a manual.

How long does a website project take?+

A focused marketing site typically runs eight to twelve weeks from kickoff to launch. Larger programmes with a design system, multi-locale content, and a substantial migration run four to six months. The audit is the first two weeks either way, and we do not start production build until the URL map, content model, and design system are signed off.

What happens after launch?+

Field vitals, rankings, and AI citation checks are monitored, and the iteration backlog is driven by what that data says. Retainer clients get template work, campaign pages, CRO experiments, security patching, and monthly reporting on traffic and conversion from the same pod that built the site, so context does not reset every quarter.

Free website audit

Find out what your site is losing to speed, search, and AI.

Send us your URL. Within five business days you get a recorded audit covering field Core Web Vitals, accessibility against WCAG 2.2 AA, structured data and AEO readiness, GEO citability, and the three changes we would make first. No cost, no pitch deck.

✓Reviewed by an engineer and a designer, not a sales rep

✓Ten to fifteen minutes of recorded screen, yours to keep

✓No obligation to work with us afterwards

First name

Last name

Company

Current platform

Work email

Anything specific we should look at? (optional)

What matters most right now?

Timeline to start

To process your request, we need your permission to store and process your personal data. Please check the box below to confirm your consent:

I agree to allow Devsinc to store and process my personal data. I agree to receive other communications from Devsinc.

We care about your privacy. Learn how we handle your data in our Privacy Policy.

We use your details for the audit only. No sequences, no list.

Website DevelopmentWant to know what your site is losing to speed, search, and AI answer engines?Get a free audit