Gatsby to Astro: Why Static Site Generators Are Evolving

The Rise and Fall of Gatsby

If you were building a fast, modern website between 2018 and 2022, there’s a good chance Gatsby was on your shortlist. It was the darling of the JavaScript world — a static site generator built on React that promised blazing-fast websites with a great developer experience.

I used Gatsby for several client projects during that period. It was genuinely impressive at the time. But the landscape has shifted, and a newer tool called Astro has emerged as the framework I now reach for on almost every project.

This isn’t a hit piece on Gatsby. It’s an honest look at how static site generators have evolved, why Astro represents the next step forward, and what this means for businesses that need fast, reliable websites.

What Are Static Site Generators?

Before we get into the comparison, let me quickly explain what a static site generator (SSG) actually does, in case the term is new to you.

A traditional website (like one built on WordPress) generates each page on the fly. Every time someone visits your homepage, the server has to query a database, assemble the page from templates, and send the result to the browser. This takes time and server resources.

A static site generator does all that work ahead of time. It builds every page once, during a build step, and produces simple HTML files that can be served instantly. There’s no database to query, no server-side processing — just pre-built pages that load incredibly fast.

Think of it like the difference between cooking a meal to order versus having it pre-prepared and ready to serve. Both give you a meal, but one is dramatically faster.

What Gatsby Got Right

Credit where it’s due. Gatsby introduced a lot of people to the benefits of static site generation.

Performance by Default

Gatsby sites were fast. The framework handled code splitting (breaking your JavaScript into smaller chunks so browsers only load what they need), image optimisation, and prefetching (loading the next page before you click on it) automatically. Out of the box, Gatsby sites scored well on performance benchmarks.

Rich Plugin Ecosystem

Gatsby had plugins for everything — pulling content from WordPress, Contentful, Markdown files, Shopify, and dozens of other sources. This made it flexible enough for a wide range of projects.

Developer Experience

For developers who already knew React, Gatsby felt familiar and productive. The documentation was solid, the community was active, and there were starter templates for every type of project.

Where Gatsby Started to Struggle

Despite its strengths, Gatsby developed some serious pain points that became harder to ignore over time.

Build Times

As sites grew in size, Gatsby’s build times became a real problem. A blog with a few hundred posts could take five to ten minutes to build. For larger sites, builds could take 20 minutes or more. Every time you wanted to preview a change, you were waiting.

This wasn’t just a developer inconvenience — it affected clients too. Making a quick text change and then waiting ten minutes to see it live is a frustrating experience for anyone.

JavaScript Overhead

Here’s Gatsby’s biggest structural issue: because it’s built on React, every Gatsby site ships a significant amount of JavaScript to the browser, even for pages that don’t need any interactivity.

Your “About Us” page is just text and images? Gatsby still sends React’s runtime to the browser. Your contact page has a single form? Still loading the full React framework. This JavaScript has to be downloaded, parsed, and executed before the page becomes fully interactive. On slower devices and connections, this creates a noticeable delay.

Complexity

Gatsby’s GraphQL data layer was powerful but added complexity that many projects didn’t need. If you just wanted to build a straightforward business website with a blog, you were dealing with GraphQL queries, node creation, and a build pipeline that felt over-engineered for the task.

The Company Behind It

Gatsby Inc, the company behind the framework, was acquired by Netlify in early 2023. Since then, development has slowed considerably. The framework isn’t abandoned, but it’s clearly in maintenance mode rather than active development. For anyone choosing a tool for a new project, that’s a significant concern.

Enter Astro

Astro launched in 2021 and has been gaining momentum ever since. It takes the best ideas from Gatsby and earlier static site generators, learns from their mistakes, and adds some genuinely innovative features.

Zero JavaScript by Default

This is Astro’s killer feature. By default, Astro sends zero JavaScript to the browser. Your pages are pure HTML and CSS, which means they load as fast as physically possible.

“But wait,” you might ask, “what if I need some interactivity?” That’s where Astro’s “islands” architecture comes in. You can add interactive components — a contact form, a image carousel, a search widget — and Astro will only load the JavaScript for those specific components. The rest of the page stays as lightweight HTML.

This is a fundamental shift from Gatsby’s approach, where the entire page is a React application. With Astro, JavaScript is opt-in rather than opt-out.

Framework Agnostic

While Gatsby locks you into React, Astro lets you use components from React, Vue, Svelte, or even plain HTML. You can mix and match within the same project. This means you can use the best tool for each job rather than being constrained by a single framework.

Faster Builds

Astro’s build times are significantly faster than Gatsby’s. A site that took five minutes to build in Gatsby might build in 30 seconds with Astro. For developers and content editors alike, that speed makes a real difference to the workflow.

Content Collections

Astro has a built-in content management system based on local files (Markdown and MDX) with type-safe schemas. This means you get validation and autocompletion when working with your content, catching errors before they reach your live site.

Simpler Mental Model

Astro’s architecture is more straightforward than Gatsby’s. There’s no GraphQL layer to learn, no complex data sourcing pipeline. You write components, import your content, and build pages. It feels closer to writing regular HTML, which makes it more accessible to a wider range of developers.

What This Means for Your Business

If you’re a business owner reading this, you might be wondering why any of this matters to you. Here’s the practical impact.

Faster Websites

An Astro site will almost certainly load faster than an equivalent Gatsby site. Faster sites mean better user experience, lower bounce rates, and higher conversion rates. Google also rewards fast sites with better search rankings.

Lower Costs

Astro sites are cheaper to host because they’re lighter. Many hosting platforms offer free tiers that are more than sufficient for a typical business website.

Future-Proof Technology

Astro is actively developed, well-funded, and has a growing community. Choosing a platform with strong momentum means your site is less likely to be built on abandoned technology in a few years.

Easier Maintenance

With fewer moving parts and less complexity, Astro sites are easier and cheaper to maintain over time. Updates are less likely to break things, and changes can be made more quickly.

Should You Migrate from Gatsby?

If you currently have a Gatsby site that’s working well, there’s no urgency to migrate. But if you’re experiencing slow builds, performance issues, or you’re planning a redesign anyway, moving to Astro is worth serious consideration.

And if you’re starting a new project from scratch, I’d recommend Astro over Gatsby without hesitation. It’s faster, simpler, and better positioned for the future.

This very website is built with Astro, and the difference in performance and developer experience compared to my earlier Gatsby projects is night and day.

If you’re curious about what Astro could do for your website — whether it’s a migration from Gatsby, WordPress, or something else — I’d be happy to chat through the options with you.

Drop me a message and let’s explore what’s possible.