WordPress vs Astro for Business Websites - An Honest Decision Guide

We build on Astro, so you should read this with that in mind. But we also spend a lot of time inside WordPress sites — fixing them, speeding them up, adding landing pages to them, and migrating them — and most of what we do for existing clients starts on WordPress. The honest version of this comparison is not “WordPress bad, Astro good.” It is that they are different tools, they are good at different jobs, and a service-business website is a job where the differences point one way more often than not.

What each one actually is

WordPress is a content management system. Content lives in a database. When a visitor requests a page, a server running PHP assembles it from the database, the theme, and whatever plugins are active, then sends the result. Themes control appearance; plugins add features, from contact forms to SEO settings to page builders. Roughly a third of the web runs on it, which means there is a plugin for almost everything and a developer in almost every town.

Astro is a web framework. Content lives in files (or in a headless CMS that produces files). Pages are built in advance, at build time, into plain HTML, and served as-is. Astro’s documentation describes its approach as “zero JS, by default”: no JavaScript reaches the browser unless a specific part of a page needs it, and then only that part. There is no server assembling pages on request, no database at runtime, and — on a platform like Cloudflare — nothing to host except files on an edge network.

Both can produce a professional business website. The question is what happens after launch.

The three questions that decide it

1. How fast does it need to be on a phone, and how much effort are you willing to spend keeping it that way?

A WordPress site can be fast. Keeping it fast is a maintenance job: the theme adds weight, each plugin adds weight, updates change things, and the caching layer has to be tuned. Most business WordPress sites we test fail mobile Core Web Vitals, not because WordPress is slow but because the accumulated stack is. Why Is My Website Slow? walks through exactly what accumulates.

An Astro site is fast as a property of how it is built. Pre-built HTML, minimal JavaScript, images optimized during the build, served from the edge. It tends to pass all three Core Web Vitals on mobile without tuning, and it stays that way because there is nothing accumulating.

2. How often does content change, and who changes it?

This is the real trade-off. WordPress’s editing dashboard is familiar, and for a team publishing several times a day it is hard to beat. If your business publishes at that volume, WordPress is a genuine strength.

For most service businesses, content changes a few times a month: a new project, a price update, a new service page, a blog post. Astro handles that through markdown files (a text editor and a commit) or a headless CMS that gives editors a form-based screen without a database on the live site. We have built both patterns for clients, including CMS-driven Astro sites where non-technical staff edit pages and publish on a schedule. The question to answer before the build is who edits and how often, so the right editing path is chosen deliberately.

3. How much does it cost to run, and who patches it?

WordPress needs hosting that runs PHP and a database, updates to core, theme, and plugins, backups, and a security posture, because the admin login is on the public internet. Managed hosting handles some of this for a monthly fee; none of it disappears.

A static Astro site on Cloudflare has almost nothing to run: files on an edge network, small server functions for forms, no admin login, no database, nothing to patch. Hosting cost is often zero or close to it, and the security surface is a fraction of the size. Cloudflare’s own documentation now steers new projects toward Workers with static assets rather than the older Pages product, which is a naming change more than a capability one; either way, the model is the same.

The comparison, honestly

When WordPress is the right answer

We will say this plainly because a comparison that never concedes anything isn’t worth reading:

• You run a substantial store on WooCommerce. The ecosystem — payments, shipping, tax, inventory, subscriptions — is mature and deep. Rebuilding it elsewhere is expensive and rarely worth it.
• You publish at volume with several editors. Daily content, editorial workflows, revisions, scheduled posts across a team. The WordPress editor and its role system are built for this.
• Your operation depends on specific plugins — a membership system, an events engine, a booking plugin with years of data — that would take real money to replace.
• The site is fine. If your WordPress site is fast, secure, edited comfortably, and converting, the answer is to keep it and fix the specific things that leak. This is exactly the advice on our platform help page, and plenty of our engagements end with “your platform is fine, here are the three things costing you.”

When Astro is the right answer

• The site is a set of pages that are the same for every visitor — services, locations, proof, contact — and speed on phones matters, which for a service business it always does.
• You run paid traffic and need landing pages that load instantly and track reliably. Ad-ready websites are built this way for a reason.
• You are tired of maintenance: plugin updates, security notices, the developer who vanished, the site that broke after an update.
• The current site fails mobile Core Web Vitals after the dashboard fixes, which means the weight is the foundation.
• You want the site to belong to you — files in a repository you own, hosted on infrastructure you control, with no vendor lock-in.

What the migration involves

Moving from WordPress to Astro is a real project, and the part that protects your rankings is the URL work, not the design. Keep slugs identical wherever possible so most pages need no redirect. Map the rest one-to-one. Plan for what WordPress generated invisibly — image paths under /wp-content/uploads/, ?p= links, category and tag archives, feeds, plugin pages — and rebuild what SEO plugins were injecting: titles, canonicals, structured data. The redesign SEO checklist has the full sequence, including the WordPress-specific table. Done properly, the migration is one of the best things that can happen to a site’s search visibility, because it comes out faster and cleaner than it went in.

Deciding

If you can answer the three questions — speed on phones, who edits and how often, and who runs it — the decision usually makes itself. If you’d like it made with evidence rather than opinion, a free website roast reviews your current site across ten categories, speed and structure included, and says plainly whether it needs a tune-up, a landing-page layer, or a new foundation. And if it’s the last one, the packages that include migration price the URL work as the line item it deserves to be.