Astro vs WordPress: when to use each one
If you're building a site for a client, how do you choose between WordPress and Astro? Direct comparison on speed, cost, maintenance, SEO and when one is clearly better.
Published: June 3, 2025
There is no universally right answer. It depends on one single question: who manages the site content after you hand it over?
WordPress: when it’s the obvious choice
WordPress wins every time the client needs to update content on their own, without going through you. The admin is intuitive, plugins cover almost everything, and hosting costs €5-10/month on SiteGround, Bluehost, or similar providers. A real estate agency uploading 20 new listings a week needs WordPress — not because it’s technically superior, but because it works without training.
The drawbacks are real: constant updates (core, theme, plugins), outdated plugins that become attack vectors, mediocre performance without caching plugins (WP Rocket, W3 Total Cache) and image optimization. An unmaintained WordPress site on cheap shared hosting can reach 5-8 seconds Time to First Byte. That’s a measurable SEO problem.
Astro: when it’s the right choice
Astro generates pure static HTML. Zero PHP running, zero database to protect, load times under 1 second on Netlify or Vercel (free for static sites) or nginx in a Docker container at €0. An optimized Astro site hits Lighthouse scores of 95-100 effortlessly — WordPress needs real work to reach 80.
The limitation is the absence of a native content admin. If the client never touches anything (brochure site, portfolio, landing page), that’s not a problem. If they want to update news or a blog, you have two options: Sanity or Decap CMS integrated as a headless CMS, or Astro’s Content Collections — Markdown files in a folder, committed to Git. Works well for technical teams or clients who accept a Git workflow.
Direct comparison
| WordPress | Astro | |
|---|---|---|
| Content updates | Visual admin, self-service | Git/Markdown or external CMS |
| Performance | Mediocre without optimization | Excellent by default |
| Security | Frequent updates, attack surface | No server-side = minimal surface |
| Hosting | €5-15/month shared hosting | Free (Netlify/Vercel) or Docker |
| SEO | Plugins (Yoast, RankMath) | Built-in with Astro SEO component |
| Maintenance | High (updates, backups) | Almost zero |
Real case: I built a medical practice site in Astro — stable content (services, team, contacts), performance critical because patients arrive on mobile over 4G, zero maintenance after delivery. For a client with a real estate listings portal, WordPress with Elementor Pro: they update it themselves, every day, no dependency on me.
What to do
- If the client updates content more than once a week → WordPress. If less than once a month or never → Astro
- For an Astro site with dynamic content, try Content Collections first (Markdown in Git): they are simpler than they look and eliminate the dependency on an external CMS
- Always measure the Lighthouse score of the delivered site on mobile with simulated 3G throttling: if it’s below 70, the client is paying in lost conversions