Platform / Astro
Astro development for marketing sites that have to be fast.
We build content-driven sites on Astro: pre-rendered, shipped to the edge, and near-zero JavaScript by default. It is the fastest honest way to build a marketing site in 2026.
Request a fit checkOverview
How Astro actually works
Astro is a static-first web framework that renders your pages to HTML at build time and ships almost no JavaScript to the browser. For a marketing site, which is mostly content, not application, that architecture is close to ideal: the visitor downloads finished HTML from a CDN edge, not a bundle that has to boot before the page is usable.
Its islands model means the rare interactive component (a search box, a calculator) hydrates in isolation, while the rest of the page stays static. You get React, Svelte, or Vue where you genuinely need them without paying for a single-page-app on pages that don't.
The opportunity is a site that scores 95+ on Lighthouse without heroics, costs almost nothing to host, and has essentially no runtime attack surface. The discipline is resisting the temptation to reach for a heavier framework's patterns: Astro rewards content-model clarity and punishes treating it like Next.js.
We build on Astro for exactly the sites it was designed for: fast, content-led, SEO-critical marketing platforms fed by a headless CMS.
Challenges
Where Astro builds go wrong
Shipping unnecessary client JS
Reaching for client-side framework islands where static HTML would do reintroduces the bundle weight Astro exists to remove.
No incremental build strategy
A large site with no thought to build performance turns every content change into a slow full rebuild.
CMS coupling
Hard-coding content into components instead of a clean CMS boundary means the marketing team can't ship without a developer.
Ignoring image and font budgets
Astro makes the HTML fast; unoptimised images and blocking fonts undo it. LCP lives or dies here.
What we build
Production Astro, done properly
Sub-second Core Web Vitals
Pre-rendered HTML, optimised images, and a controlled font strategy for 95+ Lighthouse across every page.
Clean CMS integration
Content sourced from Payload, Sanity, or Contentful behind a typed boundary your editors control.
Minimal, deliberate JavaScript
Islands only where interaction is genuine, so the median page ships close to zero JS.
Edge deployment
Static output on a global CDN: fast everywhere, cheap to run, nothing to patch.
Structured data & SEO
Per-page metadata, JSON-LD, sitemaps, and OG images generated at build time.
Scalable content architecture
Content collections and build strategy that stay fast as the site grows to hundreds of pages.
Our approach
How we ship a Astro project
Define the content model
We map pages to content collections and a CMS schema before writing components.
Build the system
A small set of typed, reusable components and layouts: a design system, not one-off pages.
Optimise the vitals
Images, fonts, and any islands are tuned to hit 95+ Lighthouse before launch, measured not assumed.
Deploy to the edge
Static output ships to a CDN with atomic deploys and instant rollbacks.
FAQ
Astro, questions we get asked
Is Astro good for SEO? +
Yes. Astro pre-renders pages to static HTML, which is the format search engines and LLMs parse most reliably, and it makes 95+ Lighthouse scores achievable without special effort. Fast, crawlable HTML with clean metadata and structured data is exactly what on-page SEO rewards, and Astro produces it by default.
Astro vs Next.js: which should we use for a marketing site? +
For a content-led marketing site, Astro is usually the better fit: it ships near-zero JavaScript and is simpler to keep fast. Next.js is the stronger choice when the site is really an application with heavy interactivity, authentication, and server-rendered dynamic data. Most B2B marketing sites are the former.
Can Astro use a headless CMS? +
Yes. Astro is CMS-agnostic and integrates cleanly with Payload, Sanity, Contentful, and others. Content is fetched at build time and pre-rendered, so the CMS never sits in the visitor's request path: the site stays fast regardless of the CMS's own performance.
Does Astro work for large sites? +
Yes, with a deliberate build strategy. Astro handles hundreds to thousands of pages; the consideration at scale is build time, which we manage with content collections and incremental patterns so publishing stays quick.
Start here
Ready to build on Astro?
A short conversation to understand your goals and determine if there's a fit. No sales pressure, no obligation.
Payload · Astro · Sanity · Next.js
Related