Astro
Astro is our choice when a site is content-first and performance is the point. It ships almost no JavaScript by default, so the performance budget holds long after launch.
- Type
- Content-focused framework
- Model
- Islands architecture
- Default output
- Static HTML, minimal JS
- Best paired with
- Storyblok or Sanity
What Astro is
Astro is a web framework built for content. It renders to static HTML by default and only hydrates the interactive components you explicitly opt into — its "islands" model — so most of a page ships as plain, fast HTML. It works with React, Vue, Svelte and others inside the same project.
Editor & developer experience
For the people running the site, Astro’s payoff is felt rather than seen: pages load fast and stay fast, which visitors and Google both reward. Editing happens in whichever headless CMS we pair it with — usually Storyblok or Sanity — so the content experience is as rich as the project needs, while the published site stays lean because Astro ships almost no JavaScript by default.
For developers, the islands model is the whole story. Everything renders to static HTML unless you explicitly opt a component into interactivity, so the default output is plain, fast HTML and JavaScript only appears where it earns its weight. It is framework-agnostic too — a React, Vue or Svelte island can live in the same project — which keeps us from over-committing the whole site to a heavy runtime for the sake of one interactive pocket.
Where it earns the shortlist
Astro earns the shortlist whenever a site is content-first and performance is the point: marketing sites, blogs, documentation and content estates where Core Web Vitals and page weight are non-negotiable. It produces some of the leanest, fastest output available, and lets us add an interactive island only where it is genuinely needed. Reach for it when interactivity is the exception rather than the rule.
- Content-heavy marketing sites, blogs and documentation
- Projects where Core Web Vitals and page weight are a priority
- Sites with a few interactive pockets rather than app-wide interactivity
When teams choose it — and when they don’t
Choose Astro when
The site is content-first
Marketing sites, blogs and documentation where words and speed matter most.
Core Web Vitals are the priority
Near-zero JavaScript by default keeps the performance budget intact after launch.
Interactivity is occasional
A few islands rather than app-wide state — hydrated only where they earn it.
Page weight and carbon count
Less JavaScript means faster loads and lower carbon per visit.
Look elsewhere when
The build is genuinely app-like
Heavy state, logged-in areas and real-time features belong on Next.js.
You need deep React tooling everywhere
App-wide interactivity is cleaner in a React framework than in islands.
The surface is a product, not a site
Dashboards and portals outgrow a content-first framework quickly.
Pricing, in plain terms
Astro is free, open-source software with no licence. Because it outputs static HTML, hosting is about as cheap as the web gets — a static site on Cloudflare Pages, Vercel or similar often costs little to nothing at typical traffic. The real cost is the build, plus the headless CMS you pair it with; the hosting bill for a fast Astro site is usually the smallest line in the project.
The SmartaStudio take
Astro is the tool we reach for when a site is all about content and the performance budget has to hold long after launch — blogs, marketing sites, documentation. It routinely produces the fastest output of anything in our stack. The honest caveat is that it is deliberately content-first: the moment a build turns genuinely app-like, with heavy state or logged-in areas, we switch to Next.js rather than fight the islands model. Right tool, right shape of job.
Not sure Astro is the right call?
Answer a few questions and Build Spec recommends the stack for your project — no jargon, no sales call.
Other framework platforms
Build with Astro?
Tell us about the project and we will confirm whether this is the right platform for it — and scope the build if it is.