Astro vs WordPress

WordPress is an application. It runs on a server around the clock, and when someone visits your site it assembles the page on the spot — pulling your content from a database, running it through your theme and plugins, and sending back the result. Everything about it flows from that: the admin dashboard, the plugin ecosystem, the need for hosting that can run PHP, and the need to keep all of it updated.

Astro is a build tool. It generates your entire site in advance, so every page already exists as a finished HTML file before anyone asks for it. There's no application running, no database answering queries, and JavaScript ships only on the pages that genuinely need it. Your site is a set of files on a global network, and serving files is about the cheapest, fastest, most secure thing the web knows how to do.

Neither approach is new-fangled or obsolete. They're different trade-offs, and the right one depends on what your website actually has to do day to day.

Speed, mostly — and everything that follows from it. Because the pages are pre-built, there's nothing to compute when a visitor arrives. That shows up directly in Google's Core Web Vitals, which affect both your rankings and how many visitors stick around long enough to enquire. It's the platform behind most of the marketing sites we design and build now, including this one.

We can use our own site as the receipt. northbase.au runs on Astro and scores 99 for performance on desktop in Google Lighthouse — with straight 100s for accessibility, best practices, and SEO, and a high-80s performance score on mobile's much harsher simulated connection. We didn't get there by squeezing a heavy platform through an optimisation regime. The platform starts light.

The editor. Log in, change a page, add a post, swap an image, publish — done, by anyone on your team, at 9pm on a Sunday if that's when the idea strikes. For a business with a real content operation — weekly articles, landing pages for campaigns, product updates — that independence is worth a great deal, and it's the thing static builds have historically struggled to match.

Then there's the ecosystem. Two decades of plugins cover almost any feature you can name, WooCommerce runs serious online stores, and roughly 40% of the web runs on WordPress — which means finding people who can work on your site is never a problem, and handing it over to an in-house marketer is painless. None of that is going anywhere.

We say this as an agency that manages WordPress sites for clients every week. In the right context it's a genuinely good platform, and some of the best-performing sites we look after run on it.

The build quote is where most comparisons stop, and it's the least interesting number. WordPress's real cost arrives after launch: core updates, plugin updates, the occasional conflict between the two, PHP versions, security monitoring, backups. Left unmanaged, a WordPress site decays — slowly, then suddenly. That's a solvable problem, and solving it is exactly what a proper WordPress management arrangement is for, but it's a real line item for the life of the site.

Astro's real cost sits on the other side of the ledger. The site barely needs looking after, but content changes are developer work. If your site changes quarterly, that cost is tiny. If your team wants to publish twice a week, routing every change through a developer is the wrong shape entirely — at that point you either want WordPress, or a content backend feeding the Astro build, which is a bigger conversation.

WordPress earns its place when your team publishes often and wants independence; when the store runs on WooCommerce; when non-technical people need to edit everything; and when there's a plan (and budget) for keeping it maintained. Those conditions describe a lot of businesses, which is why so much of the web runs on it.

Astro earns its place when the site's job is marketing and lead generation, where speed measurably affects rankings and conversion; when content changes are measured in months; when you're building landing pages that ad spend depends on; and when you'd rather own almost no maintenance burden at all.

And it's a decision, not a marriage. Sites move from WordPress to Astro and back as businesses change, with URLs preserved and rankings intact when the migration is done carefully. The platform should follow the way your business works — never the other way around.