Capability
Sites and web applications that load in under a second, pass Core Web Vitals on real devices, and rank because of it. Built on Next.js, with structured data and a content model your team can actually edit.
From $3,500 · 3–6 weeks · fixed scope, agreed in writing
What your team gets
Not a strategy deck. A running system, the permissions around it, and the code in your repository.
What we build
Different jobs, same non-negotiables: fast on a mid-range phone, readable by a crawler, editable by your team.
The site that has to rank, convert and load instantly. Prerendered by default, so the page comes off a CDN rather than being assembled on request.
A company site where every page is static HTML and still fully dynamic to edit.
Many pages generated from structured content, each one genuinely useful rather than spun. This is how a service business covers a category properly.
A capability page per service and an industry page per segment, all from one content model.
Authenticated, stateful products where the browser is the interface to a real system rather than a brochure.
A member portal handling registration, renewals and documents.
Headless commerce where the storefront is fast and the catalogue lives where your operations already are.
A storefront built to hold a seasonal traffic curve without falling over.
Moving off a page builder or an ageing CMS without losing the rankings you have. Redirects mapped before anything ships.
A WordPress site moved to Next.js with every URL preserved or redirected.
An existing site that is slow, unindexed or both. Diagnosis first, then the fixes in order of what actually moves the number.
Cutting largest-contentful-paint by more than half without a redesign.
How we build it
Speed and ranking are not separate projects. Core Web Vitals are a ranking input, and the architecture that makes a page fast — prerendered HTML from an edge cache — is the same architecture that makes it reliably crawlable. These five decisions carry most of the result.
Pages are static HTML served from a CDN, with dynamic rendering used only where it is genuinely needed. Time-to-first-byte becomes a cache hit rather than an origin round trip.
Server components by default, client interactivity as islands. The heaviest cost on a mid-range phone is parsing and executing script, not downloading it.
Explicit dimensions on images and embeds, fonts with metric-matched fallbacks. Layout shift is the easiest of the three Core Web Vitals to fix and the most often ignored.
One metadata factory, canonical URLs, and JSON-LD generated from the same data that renders the page — so the markup and the content can never drift apart.
Lab scores are a proxy. Real-user metrics from actual visitors on actual devices are the number Google uses, and the only one worth reporting.
A growing share of discovery happens inside an AI answer rather than on a results page. Being cited there depends on things classic SEO never emphasised: explicit entity markup, self-contained answers that can be lifted with attribution, and a clean, structured summary of the site. We build these in rather than retrofitting them.
The right answer depends on who edits and how often. Content in the repository is fastest and free, and suits a site a developer maintains. A headless CMS earns its cost the moment a non-developer needs to publish without a deploy. We ask who will actually be editing before choosing, because the wrong answer here is felt weekly.
Most traffic lost in a rebuild is lost to unmapped URLs. Before anything ships we inventory every indexed URL, map each to its destination, and put permanent redirects in place — then watch coverage and position for the weeks after launch rather than declaring victory on go-live day.
Where it lands
Storefronts fast enough to hold a seasonal peak without conversion falling away.
Public site and member portal on one codebase, one content model.
Listing sites where every property is an indexable, structured page.
Corporate sites that make a serious operation look like one.
Marketing sites with the compliance review built into the publishing flow.
Accessible, fast sites where the content has to be right and readable.
Technology
We pick the boring option unless there is a reason not to — the framework is the part most likely to be abandoned before your system is.
How the engagement runs
Every phase ends in a named deliverable. You can stop after any of them and keep what has been built.
What the site has to do — rank, convert, serve an audience — and what is stopping the current one. Thirty minutes.
Information architecture, keyword and intent mapping, the content model, and who will be editing it after launch.
Key templates designed rather than every page, so the system scales to pages that do not exist yet. Reviewed on a phone as well as a desktop.
Templates built as reusable components, content loaded, structured data generated from the same source that renders the page, redirects mapped for any migration.
Go-live, Search Console verified, field vitals monitored, and coverage and position watched for the weeks that follow.
Why Devs Core
Core Web Vitals are measured in the field. We build for a mid-range phone on a normal connection, because that is what is scored.
JSON-LD generated from the same arrays that render the page, so the markup cannot drift from what a reader sees.
Entity markup, liftable answers and a structured site brief, because a growing share of discovery happens inside an AI answer.
Editing text should not risk the layout, and adding the hundredth page should cost the same as the tenth.
Every indexed URL inventoried and mapped before launch. Lost traffic in a rebuild is almost always an unmapped URL.
WCAG 2.1 AA verified with real tooling and keyboard testing, not assumed because the design looked clean.
Questions
Next.js with React, TypeScript and Tailwind CSS, deployed on Vercel or Cloudflare. Pages are prerendered and served from an edge cache by default, which is what makes them fast, and dynamic rendering is used only where it is genuinely required. We use Astro for content-heavy sites with little interactivity.
Web development starts at $3,500 for a fixed scope over three to six weeks. The variables are the number of unique templates, whether content has to be migrated, and whether a CMS is needed for non-developer editing.
That is the design constraint rather than a hope. Prerendered HTML from a CDN, minimal client JavaScript, explicit dimensions on media, and metric-matched font fallbacks. We report field Core Web Vitals from real visitors after launch, not just a lab score on a fast laptop.
Yes, and we choose the content layer based on who will actually be editing. Content in the repository is fastest and free but suits a developer-maintained site; a headless CMS such as Payload or Sanity earns its cost the moment a marketer needs to publish without a deploy. We ask before choosing.
Not if the migration is done properly. Every indexed URL is inventoried and mapped to its destination with permanent redirects before anything ships, and we watch coverage and position for the weeks after launch. Traffic lost in a rebuild is almost always an unmapped URL rather than anything to do with the new site.
Yes. That means explicit JSON-LD entity markup, answers written to be self-contained enough to lift with attribution, a structured summary at /llms.txt, and a crawler policy that deliberately allows AI crawlers — because being excluded from an AI answer is a worse outcome than being scraped.
We build on WordPress where a client’s team is committed to it, and we run it headless with a Next.js front end where the editing experience matters but the performance ceiling does not. For a new marketing site with ranking goals, Next.js is usually the better answer and we will say so.
Yes, to WCAG 2.1 AA, and verified — automated checks with axe, plus keyboard and screen-reader testing on the key flows. It is not an add-on line item, partly because retrofitting it costs several times what building it in does.
Thirty minutes, no preparation, no deck. You describe what keeps going wrong and we tell you whether AI is the answer — including when it is not.
Prefer email? contact@devs-core.com