Astro vs Next.js vs WordPress: choosing the right tool

People ask us which is “best”, Astro, Next.js, or WordPress, as if there’s a winner. There isn’t, any more than there’s a best vehicle. A pickup, a sports car, and a city bus are all correct answers to different questions. The mistake isn’t picking the “wrong” one; it’s picking without first being clear about the job. Here’s how the three differ and when each is the right call.

WordPress: maximum familiarity, maximum baggage

WordPress runs a huge share of the web for good reasons: it’s familiar, there’s a plugin for everything, and almost any agency can work on it. If you need a content site, a non-technical person to edit it, and a plugin ecosystem to bolt on features, it’s a known quantity.

The costs are equally real. WordPress is a traditional CMS that renders every page through a heavy engine on each request, so it tends toward slow without serious effort. The plugin ecosystem that gives it superpowers is also its biggest liability, every plugin is code from a stranger running on your site, a security surface and a performance drag. And the “anyone can work on it” advantage means a lot of WordPress sites are built by whoever was cheapest.

Reach for it when: you need a conventional content site, broad editor familiarity matters more than speed, and you’ll genuinely use the plugin ecosystem.

Next.js: a framework for applications

Next.js is a React framework built for applications, software that lives in the browser. Dashboards, products with logins, anything with significant interactivity, real-time data, and complex state. If your “site” is really an app wearing a website’s clothes, Next.js is built for exactly that, with the full power of React and a mature ecosystem behind it.

The cost is that all that power is weight you carry whether or not you use it. Building a marketing site or a blog in Next.js means shipping a JavaScript application to render what is fundamentally a document, slower, heavier, and more complex than the job requires. It’s a sports car doing the grocery run: impressive, and the wrong tool.

Reach for it when: you’re building an actual application: logins, dashboards, heavy interactivity, real-time data.

Astro: built for content

Astro is built around a specific insight: most “websites” are content, not applications, and content should ship as fast static HTML with almost no JavaScript. It renders your pages to plain HTML at build time and ships zero JavaScript by default, adding interactivity only as small islands where you need it. The result is near-perfect performance on content sites without giving up modern components and tooling.

Astro’s limit is the mirror image of Next’s: it’s not the tool for a heavily interactive application. It happily embeds React (or Vue, or Svelte) islands where you need them, but if your whole product is an app, you’re fighting the framework’s grain. For content sites (marketing, blogs, publications, documentation, most small-business sites), it’s the sharpest tool available.

Reach for it when: the site is fundamentally content, and speed and SEO matter, which is most marketing sites, blogs, and publications.

The decision in one question

Strip away the tribalism and the choice comes down to a single question: is this thing a document or an application?

• Mostly a document (marketing site, blog, publication, brochure) → Astro. Fast by default, great for SEO, cheap to host.
• Mostly an application (logins, dashboards, real-time, heavy interactivity) → Next.js. Built for exactly that.
• A conventional content site where editor familiarity and plugins outweigh speed → WordPress, eyes open to the trade-offs.

Plenty of real projects are a blend, a fast Astro marketing site in front of a Next.js app, say, and that’s a perfectly good answer too.

Why we lead with the question, not the tool

We use all three depending on the job, and we’ll tell you which one fits yours before we write a line of code, including when the honest answer is the boring one. A studio that always reaches for the same framework regardless of the project isn’t choosing a tool; it’s applying a habit. The right tool for the job is one of the few things we’re genuinely dogmatic about.

If you’re not sure which camp your project is in, that’s exactly the conversation we like to have first. Tell us what you’re building.