What is the Astro framework and when is it worth it for a business website?

The Astro framework is an open-source tool for building fast websites that are built around content: company websites, blogs, campaign pages and documentation. It generates pages as ready-made HTML and sends JavaScript to the browser only where it is actually needed. The result: the site loads faster, Google reads it more easily and visitors get in touch sooner.

In short:

• Astro is free (MIT licence). Since January 2026 it has been owned by Cloudflare, but it remains open source and can be deployed on any hosting.
• Its core idea is called islands architecture: the page is static HTML and only interactive elements get JavaScript.
• It is ideal for company websites, blogs, campaign pages and documentation. Web applications and complex online stores are better served by other tools.
• Paired with a headless CMS, you edit content yourself without touching code.

Why website speed matters

Website speed translates into money. The Milliseconds Make Millions study, run for Google by Deloitte and 55 across 37 brands and more than 30 million sessions, found that making a mobile site 0.1 seconds faster led to:

• retail: 8.4% more conversions and a 9.2% higher average order value,
• travel: 10.1% more conversions,
• lead generation: 21.6% more form submissions.

Astro is not the only way to get a fast website. But it makes speed the default rather than something you have to fight for with plugins and after-the-fact optimisation. How to measure speed is covered in our article on website speed and Core Web Vitals.

What Astro is and where it came from

Astro grew out of a simple observation: most websites are there to be read, not to be clicked around like a complex application. A company website, a blog or a product page mainly needs to show text, images and a contact form quickly. Yet many are built on technologies designed for web applications and send hundreds of kilobytes of JavaScript to the browser that the visitor never needs.

The stable 1.0 release came out in 2022. Today Astro is used by brands such as Unilever, Visa, NBC News, Webflow and Wix. In January 2026 Cloudflare acquired Astro. The framework stays open source and can still be deployed outside Cloudflare. For clients this is good news: a stable company stands behind the technology, so the risk of the project disappearing in a few years is low.

The current major version is Astro 7, released in June 2026. It brought a compiler rewritten in Rust and builds that are 15 to 61% faster.

Astro's philosophy in five points

1. 1Content first. Astro is built for websites where the main product is text, images and information.
2. 2Server first. The heavy lifting is done by the server or the build, not by the visitor's phone.
3. 3Fast by default. Without special optimisation you get a site that loads quickly. You have to slow it down with your own mistakes.
4. 4Easy to use. The syntax is based on HTML, so developers pick it up quickly.
5. 5Open. You are not locked into one ecosystem: Astro works with React, Vue, Svelte and headless CMSs.

If you are not sure what a framework actually is, our glossary explains it without jargon.

Key features of the Astro framework

Islands architecture: interactivity only where it is needed

This is the main reason Astro is fast. Picture the page as a sea of static content: headings, text, photos, footer. In that sea there are small islands of interactivity, such as a review carousel, a price calculator, a chat widget or a shopping cart. Astro renders the whole page as plain HTML and attaches JavaScript only to those islands.

You also decide when an island "wakes up". That is what client directives are for:

In practice, a calculator at the bottom of the page does not slow down the first impression. Its code downloads only when the visitor actually sees it.

Astro also has server islands (the server:defer directive). They solve the opposite problem: the page is static and fast, but one block is personalised, for example the name of a logged-in customer or current stock availability. That block is computed on the server separately and does not hold up the rest of the page.

Zero JavaScript by default

Most modern frameworks send the whole application to the browser and only then bring it to life. Astro does the opposite: if a component does not need interactivity, it ships not a single line of JavaScript for it. Less code means faster loading, especially on weaker phones and slower mobile connections.

Bring your own framework, or none

Astro is framework-agnostic. One project can include components from React, Vue, Svelte, Preact, SolidJS or Alpine.js. For a business this has two practical consequences:

• if you already have components from another application, there is no need to rewrite them,
• you do not depend on one type of developer, and a team working with a different technology can take over the project.

Content collections: content with structure

Blog posts, case studies or products can be stored in files or pulled from a CMS. Astro gives them a fixed structure, for example: every article must have a title, a date and an author. If something is missing, the build fails before the error reaches the live site. For SEO that is a welcome safety net: no article without a meta description.

Static and dynamic pages in one project

Astro supports both rendering modes and lets you mix them page by page:

• SSG (static site generation): the page is generated once at build time. Ideal for services, the blog and case studies.
• SSR (on-demand rendering): the page is assembled on every visit. Suited to search, a client area or prices that change in real time.

On top of that, Astro has built-in API endpoints (form handling, webhooks), image optimisation and, since version 7, stable route caching.

How Astro works in practice

The whole process comes down to three steps:

1. 1Build or server. Astro runs all components on the server side and turns them into ready-made HTML and CSS.
2. 2Browser. The visitor receives the complete page in the very first response: text, images and links are visible without waiting for JavaScript.
3. 3Island hydration. Only the interactive parts download their code, each one separately and at the moment set by its directive.

A model example: a company page has a header with a menu, a hero banner, a services section, a price calculator, a block with available dates, a review carousel and a footer. In Astro only four of these seven blocks need JavaScript, and three of them load only when the visitor actually needs them. A classic React application would ship code for all seven.

What Astro does for your business

Technology is not a goal in itself. It only becomes interesting when it improves the numbers you track: enquiries, orders or running costs. With Astro we see four areas.

1. Speed that visitors can feel

Less JavaScript means the page becomes usable sooner. The biggest difference is on mobile, where many company websites now get most of their visits. Every second of waiting raises the chance that a visitor goes back to the search results and clicks a competitor.

2. A better starting point for SEO

Google assesses user experience through Core Web Vitals: how quickly the main content appears (LCP), how the page responds to interaction (INP) and how stable the layout is (CLS). Astro helps with all three:

• ready-made HTML means a fast LCP,
• less JavaScript on the main thread means a better INP,
• built-in image optimisation with dimensions helps CLS.

What Google sees also matters. With a site built as a classic React single-page application (SPA) without prerendering, the search engine first receives an almost empty page and has to render the content itself. Astro sends finished text, headings and links in the very first response. The same applies to AI search engines and assistants, many of which do not run JavaScript at all.

Speed is not an SEO strategy, though. If a site lacks the right keywords, structure and content, Astro will not put it in first place. See how we approach SEO.

3. Lower hosting costs and better security

Static pages can be hosted on a CDN (Cloudflare, Netlify, Vercel) for a few euros a month, and smaller sites often fit into a free plan. The site handles traffic spikes after a campaign without going down.

A static site also gives attackers very little to work with. There is no admin panel at a public address, no database query on every visit and no ten plugins to keep updated. On WordPress, outdated plugins are a common way in for attackers. More in our website security checklist.

4. Scaling without a rebuild

As the company grows, the website grows with it. You start with a static company site, later add a blog connected to a CMS, a client area via SSR or a configurator as an interactive island. All in one project, without starting from scratch.

When Astro is not the right choice

Astro is not a universal solution, and we are not saying you should switch to it at any cost. Choose a different tool if:

• you are building a web application, not a website. An internal system, a CRM, a dashboard or a tool where users spend hours clicking is the domain of Next.js, Nuxt or plain React. We explain the difference in what is a web application.
• your product depends on complex application state. If most of the page changes based on user actions (filters, drag and drop, real-time collaboration), the advantage of islands architecture disappears.
• you need an online store with thousands of products and a ready-made backend. Astro can be a fast frontend on top of Shopify or another headless e-commerce platform, but orders, payments and stock have to be handled by another system. For a typical shop, a proven e-commerce website or an off-the-shelf platform is often more efficient.
• content is managed by a non-technical team and you do not want a CMS. Astro itself has no admin interface. Without a headless CMS, content lives in files and text changes need a developer.

Pitfalls to watch for, even with Astro

An Astro site can still be slowed down. The most common mistakes:

1. 1Too many islands. If a developer puts client:load on every component, the site ships as much JavaScript as a classic SPA.
2. 2Third-party scripts. Chat, heatmaps, pixels, three analytics tools: each adds weight that no framework can remove. A disciplined tag manager setup and deferred loading help.
3. 3Unoptimised images and fonts. A 5 MB photo will kill even the fastest framework. Use the built-in image component and font-display: swap.

The last factor is a smaller community. Astro has excellent official documentation, but the ecosystem of ready-made add-ons is smaller than for React or WordPress. For an agency that is not a problem; for a company that wants to assemble its own site from plugins, it is.

Astro vs Next.js vs WordPress

The most common question we hear from clients is not "what is Astro" but "why not WordPress, when everyone knows it". The short answer: each tool solves a different problem.

Astro vs Next.js

Next.js is stronger when most of the page lives in the browser: dashboards, client portals, applications. Astro wins when most of the page is content and interactivity is an add-on. In practice: if you would describe your site as "pages people read", Astro is usually the simpler and faster choice. If you would describe it as "a tool people use", go for Next.js.

Astro vs WordPress

WordPress has one huge advantage: an admin interface anyone can use. For many company websites it is still a sensible choice, and we explain why in our article on why WordPress is enough for most clients. The price is plugins, updates and speed that tends to degrade over time. Astro connected to a headless CMS offers similar comfort when editing content, without those drawbacks. If you have a working WordPress site with good SEO, switching for the sake of fashion makes no sense. If your site suffers from slow loading, security incidents or expensive maintenance, a redesign is a good moment to consider Astro.

Where Astro makes the most sense

Company websites

A typical services website: home, services, case studies, about, contact. Content changes a few times a month and interactivity is minimal. That is exactly the situation Astro was designed for: a fast site with almost no maintenance. You can read how we approach website development on our service page.

Blogs and content SEO

If you win clients through educational content, you need pages that Google indexes quickly and people read on mobile. Astro handles hundreds of articles, generates a sitemap and RSS through official integrations, and can be set up so that every article has the required SEO fields.

Campaign pages for PPC

With PPC campaigns you pay for every click. If a landing page takes three seconds to load, some of the visitors you paid for leave before they see it. A fast landing page helps your cost per conversion, and in Google Ads landing page experience also feeds into Quality Score.

Product catalogues and configurators

Premium products such as furniture, wellness or building solutions need high-quality photos and educational content before the purchase. The catalogue can be static and fast, while the configurator or price calculator runs as an interactive island. Customers get a rich experience without paying for it in speed on every page.

Documentation, guides and glossaries

For documentation there is the official Starlight template, which powers, for example, Cloudflare's developer documentation. The same principle works for company knowledge bases, FAQs and glossaries: formats that build trust and capture long-tail searches.

Multilingual websites

Astro has built-in internationalisation support (language-based routing, a default language, redirects). For companies operating in several markets this is practical: several language versions in one project, each with correct hreflang tags.

Astro and a headless CMS: speed plus easy content editing

The most common concern we hear: "Will I be able to edit text or add an article myself?" Yes, if you connect Astro to a headless CMS.

A headless CMS is an admin interface without its own front end. Editors write articles, update prices or upload case studies there, and the content is sent through an API to Astro, which builds the pages. Separating content from presentation has three advantages:

• editors cannot break the design, because they fill in fields rather than use a visual builder,
• one piece of content, many channels, so the same product appears on the website, in an app and in a newsletter,
• a new website without migrating content, because at the next redesign the CMS stays and only the frontend changes.

How it works in practice

1. 1An editor saves a change in the CMS, for example a new article.
2. 2The CMS sends a webhook to the hosting.
3. 3Astro rebuilds the pages. For a typical company website that takes minutes, not hours.
4. 4The new version is deployed to the CDN and is available worldwide.

If a change has to be visible immediately (stock levels, for example), that page or block is rendered on demand via SSR or a server island.

Which CMSs work with Astro

Astro's official documentation has guides for dozens of CMSs, and practically any CMS with an API can be connected. The most common options:

The last row is interesting for companies that already run WordPress. The admin can stay; only what visitors see changes. WordPress is then not publicly exposed and site speed no longer depends on plugins.

How to get started with Astro

For developers: a first project in minutes

You need Node.js (according to the docs, version 22.22 or newer; odd-numbered versions are not supported), a terminal and an editor, such as VS Code with the official Astro extension. Create a new project with npm create astro@latest. The wizard asks for a folder name, a template, whether to install dependencies and whether to initialise Git.

The resulting structure is easy to follow:

• src/pages – each file is one URL,
• src/components – reusable parts such as a header or a service card,
• src/layouts – the shared page skeleton,
• public – images, favicon, robots.txt,
• astro.config.mjs – configuration and integrations.

Start the development server with npm run dev and open the site at the local address on port 4321. Pages are written in .astro files that look almost like HTML. An interactive component, such as a React calculator, goes into the page with the client:visible directive, and its code loads only when the visitor scrolls to it. Build the production version with npm run build and deploy it to Cloudflare, Netlify, Vercel or your own server.

When migrating from another framework (typically Gatsby or Next.js), it pays to go step by step: static pages first, then simple components, and stateful components last. Existing React components can be used as they are at first.

For business owners: how to decide

You do not need to understand code to know whether Astro is right for you. Three questions are enough:

1. 1Is your website mainly about content? Services, products, case studies, a blog: yes. An internal application: no.
2. 2How fast is it today? Test it in PageSpeed Insights. If Core Web Vitals are red on mobile, you are losing visitors and rankings.
3. 3What does maintenance cost you? Add up the hours and money spent on updates, plugin fixes and security over the past year. You can also hand maintenance over; see our website maintenance service.

If you answered yes to the first question and got an unfavourable number for the second or third, Astro is a strong candidate for your next redesign. You can put together the scope of a new website in our configurator.

Conclusion: technology is the tool, results are the goal

Astro is currently one of the best choices for content-driven websites. It is fast by default, indexes well, costs little to run and, with a headless CMS, can be managed by a non-technical team. Under Cloudflare it also has stable backing.

It is not the answer to everything, though. For web applications, complex online stores or companies that want to assemble their own site from plugins, there are better options. So the right question is not "Astro or WordPress?" but "What should the website do for the business, and how will we measure it?"

At Weboptim we choose the technology only once we know the goals, the budget and how you will manage the site. If you are considering a redesign or your current website is holding your business back, get in touch. We will look at the data and tell you whether the change is worth it, even if the answer is no.