WordPress vs Astro: what actually costs

01 · WordPress vs Astro: two ideas of what a website is

In WordPress, a page does not exist until someone asks for it. A visitor arrives, PHP runs, the database is queried, plugins add their contributions, and a page is assembled. Caching avoids repeating that every time, but the model underneath is assembly on demand.

In Astro, assembly happens once, at deploy. Every page becomes a finished file, distributed to servers worldwide. When a visitor arrives, the file is handed over — nothing computes, nothing queries, nothing fails under load.

Almost every difference below follows from that distinction. WordPress trades runtime work for flexibility; Astro trades flexibility for having nothing at runtime to go wrong. It belongs to the tools usually called static site generators, though the name undersells it.

02 · Content management: WordPress editor vs Astro content files

This is where the two platforms are furthest apart, and it is the difference that decides most projects.

WordPress gives every author a browser editor, media library, revisions, scheduling, drafts and user roles — free, out of the box. A marketing manager can add a page at 4pm on a Friday without speaking to anyone. Twenty years of refinement went into that, and it shows.

Astro has no editor. Content lives as structured files with a defined shape — a product must have a price, an article must have an author — checked when the site builds. A record that does not match stops the build rather than publishing broken.

The trade is consistency for immediacy. You gain a guaranteed shape for every record and a full history of every change. You lose the Friday-afternoon edit.

Can non-technical staff still publish on Astro?

Yes, provided you give them somewhere to write. A headless CMS restores the browser editor, previews and roles, and the site rebuilds when they publish. The choice is not editor versus no editor — it is whether the editor comes bundled or is attached deliberately.

Our rule of thumb: if more than two non-technical people publish, or anyone publishes daily, budget for a CMS from the start. Retrofitting one later costs more.

If keeping the familiar editor matters more than dropping the maintenance, pairing Astro with a headless CMS is the middle path.

03 · Development: plugins in WordPress, components in Astro

WordPress development is largely assembly. There is a plugin for most requirements, and the fastest path to a feature is to find it, install it, configure it. That is a real advantage — a booking system or membership area can be running in an afternoon.

The cost arrives later. Each plugin is code you did not write, updating on its own schedule, sometimes conflicting with another. Thirty plugins means thirty upgrade paths that must stay compatible with each other, the theme and the PHP version.

Astro development is composition. You build components and lay out pages with them. Less to install means less to conflict — but also nobody to install a booking system from. Interactive features are designed and built, and only those parts ship JavaScript. The rest is plain HTML.

WordPress is faster to a first version. Astro is cheaper to keep correct. Which matters more depends on whether you are treating the site as a project or as a permanent asset — which is the question we work through in how we build on Astro.

04 · Hosting: WordPress servers vs Astro static delivery

WordPress needs somewhere to run PHP and somewhere to keep a database: a server, backups of both, a PHP version to keep current, and usually a caching layer in front. Managed hosting exists because that is more moving parts than most teams want.

An Astro site is a folder of files on a content delivery network, close to your visitors, with no server to size and no database to back up. This is what people mean by JAMstack: static files at the edge, with dynamic behaviour added only where needed.

The phrase “no server” gets misused. Forms, search and anything personalised still need logic somewhere — usually a small serverless function. Far less infrastructure than a WordPress install, but not zero, and any comparison claiming otherwise is selling something.

05 · WordPress vs Astro cost, over three years

Sticker price favours WordPress and total cost usually favours Astro, which is why the two camps talk past each other. The way to compare them is to separate the costs that behave differently over time.

Compare over two or three years rather than at launch. A cheaper build that needs monthly attention often overtakes a more expensive one that needs almost none.

What does an Astro site cost to run?

Less than a WordPress site, but not nothing. Hosting for a pre-built site is often free at typical business volumes. Against that, count CMS seats, any form or search service, and the developer time a content change consumes when there is no Publish button.

The WordPress equivalent is hosting that scales with traffic, annual plugin licences, and a maintenance retainer that runs whether or not the site changed. Most comparisons leave that last line out, and over three years it is usually the largest number on either side.

06 · Maintenance and security: the WordPress update cycle

A WordPress site is never finished. Core, plugins, theme and PHP all move independently, and each update carries a small chance of breaking something. The work is not hard, but it is perpetual, and it happens whether or not the site changed.

Is WordPress less secure than Astro?

Not inherently — WordPress core is scrutinised more heavily than most software. The difference is surface area. A WordPress site exposes a login page, a database and whatever endpoints its plugins add; each is a door that has to stay locked. An Astro site exposes files, so most of those doors do not exist.

Scale is the other half. Because WordPress runs so much of the web, automated scanning is constant and indiscriminate — a small site gets probed as often as a large one. That argues for keeping WordPress current, not abandoning it, but it is why a neglected WordPress site carries a different risk from a neglected static one.

WordPress needs ongoing attention to stay safe. Astro needs attention only when you want it to change. For an organisation with no technical person on hand, that difference is often the whole argument.

07 · WordPress vs Astro: performance and SEO

A well-built WordPress site with good hosting and sensible caching is fast. The comparison is not WordPress-is-slow; it is that Astro starts from a position where the usual causes of slowness are absent.

Three things make a WordPress page heavy, and all three come from the plugin model rather than WordPress itself. Plugins add their own stylesheet and script to every page, whether it uses the feature or not. Themes ship broadly, so they load broadly. And the page still has to be assembled before it is sent.

Astro ships no JavaScript by default. Interactive components are opted in individually, so a page with one interactive element sends only that code. Combined with pre-building, good performance becomes the default rather than something you tune towards.

You can still build a slow Astro site. Oversized images ruin either platform, and no framework saves you from a 3 MB hero photo.

Does moving to Astro improve SEO?

Not by itself. Astro does not make your content more relevant, and relevance is what ranks. It changes the technical floor: pages render fully in the HTML without waiting for JavaScript, load quickly on mobile, and do not shift while settling. Those are ranking inputs, but tie-breakers rather than the main event.

WordPress can hit the same floor with disciplined hosting, a lean theme and caching. The difference is that Astro arrives there by default and stays there, while a WordPress site drifts as plugins accumulate. If your organic traffic is already healthy, treat a platform change as protection, not a growth lever.

The real SEO risk sits in the move itself, not the platform. Rankings attach to web addresses, so any replatform that changes URLs without redirecting them properly costs you visibility regardless of which technology you land on. There are sites we have rebuilt, with the numbers, if you want to see how that plays out.

08 · Scalability: traffic, page count and team size

Scale means three unrelated things in these conversations, and the platforms rank differently on each.

Which kind of scale do you actually have?

Be precise about which one you have. A campaign spike or press mention is traffic, and pre-built pages absorb it without you doing anything. Tens of thousands of product pages is build time, and needs incremental builds. Fifteen people who all publish is a workflow problem, and no framework solves it — you need a CMS either way.

Most teams asking about scale mean traffic, where Astro wins clearly. The ones who should worry have tens of thousands of pages or a large pool of non-technical publishers — both cases where WordPress earns its keep.

09 · When to choose WordPress, and when to choose Astro

We build on Astro and still recommend WordPress regularly. It is the better choice more often than the framework conversation admits.

If you recognise your site in the right-hand column and you are already on WordPress, moving is a well-understood project — the main thing to get right is moving a WordPress site without losing its URLs.

WordPress vs Astro: common questions