Astro vs. WordPress in 2026: when to pick what
I ship both. Here's the honest framework I use to decide which stack to recommend — based on team, content velocity, Core Web Vitals, and the real-world costs Indian businesses face.
I get this question every week from founders: “Should we build on Astro or WordPress?”
The right answer depends on five things — none of which is your developer’s preference.
I’ve shipped 120+ sites across both platforms. Some for Mumbai D2C brands doing ₹20 Cr ARR. Some for solo consultants who just need a portfolio. The stack choice changed the trajectory of the project every time — not because one is “better,” but because the wrong choice creates friction that compounds for years.
The stack debate is a proxy for a harder question: who maintains this site after launch, and how often does it need to change?
The decision framework
1. Who’s publishing?
If your founder or marketing manager updates the site themselves — adding blog posts, changing text, uploading images — WordPress wins. The block editor is genuinely good now. Non-technical people can publish without a developer in the loop.
If a developer updates the site, or if content is managed in markdown files reviewed via pull requests — Astro + MDX wins by a mile. It’s faster to develop, easier to maintain, and the output is cleaner.
The mistake I see: Founders choosing Astro because their developer says it’s better, then needing that developer for every small content change for the next three years. The developer moves on. The site becomes a monument to a technology the team can’t use.
The other mistake: Founders choosing WordPress because “everyone uses it,” then spending ₹30,000/month managing plugins, security, and hosting for a 15-page marketing site that changes once a quarter.
2. How often do you publish?
| Publishing frequency | Recommended stack | Why |
|---|---|---|
| 4+ times per week | WordPress (or headless CMS) | Your editor needs a CMS they can use without Slack-ing a developer |
| 1–4 times per week | Either works | WordPress for non-technical editors, Astro for developer-led teams |
| 2–4 times per month | Astro + MDX | Markdown files in git are fast, clean, and version-controlled |
| Once a month or less | Astro | No CMS overhead, no plugin maintenance for content you barely touch |
3. What’s the Core Web Vitals target?
If you care about Core Web Vitals (you should — they’re a ranking factor), Astro is built for it out of the box. Every page outputs static HTML. Zero JavaScript ships by default. The browser has almost nothing to parse.
WordPress can get there — but it’s a project in itself. Plugin pruning, image optimisation, render-blocking script elimination, caching configuration, CDN setup. I’ve written about this in detail — most WordPress sites I audit score 30–45 on mobile PageSpeed.
Real numbers from my builds:
| Metric | This site (Astro) | Typical WordPress (Elementor) | Optimised WordPress (custom theme) |
|---|---|---|---|
| LCP (mobile 4G) | 0.8s | 3.5–5.0s | 1.5–2.2s |
| PageSpeed mobile | 97 | 30–50 | 70–85 |
| Total page weight | 180KB | 1.5–4MB | 400–800KB |
| JS payload | 12KB | 300–800KB | 80–200KB |
This site loads in under 800ms LCP on mobile 4G. That’s not a WordPress reality without serious engineering.
4. How dynamic is the site?
E-commerce with 10,000 SKUs, member portals, real-time booking systems, user dashboards — WordPress (or a proper headless setup with Next.js/Remix) handles this. Astro will fight you.
Marketing site, portfolio, blog, documentation, service pages — Astro every time. It does static content better than anything else in the ecosystem.
The hybrid option: For larger content sites that need both performance and editorial workflow, I’m increasingly shipping headless WordPress + Astro frontend. WordPress becomes the CMS (editors love it), Astro generates the static site (Google loves it). Best of both worlds, but requires a developer for the initial setup.
5. The hidden cost: maintenance
This is where the real difference lives, and it’s the factor most founders ignore when choosing a stack.
WordPress maintenance reality:
- 20–40 plugins, each with update cycles and potential conflicts
- Security patches (WordPress is the #1 target for malware — 90%+ of hacked CMS sites are WordPress)
- Hosting that needs management (PHP version, database, SSL, backups)
- Performance monitoring (a single plugin update can tank your PageSpeed)
- Annual cost: ₹50,000–1,50,000 in hosting + maintenance
Astro maintenance reality:
npm run build, deploy to Cloudflare Pages or Vercel- Zero security surface (no database, no login, no server-side code)
- Hosting: free tier on Cloudflare Pages handles most sites
- Annual cost: ₹0–5,000 (domain renewal + any premium CDN features)
Over 3 years, the maintenance cost difference between WordPress and Astro for a 20-page marketing site is ₹1.5–4.5 lakh. That’s not trivial for a small business.
Cost comparison for Indian businesses
| Astro site | WordPress (custom theme) | WordPress (page builder) | |
|---|---|---|---|
| Build cost | ₹2,50,000–5,00,000 | ₹3,00,000–6,00,000 | ₹1,00,000–3,00,000 |
| Hosting (annual) | ₹0–6,000 | ₹12,000–36,000 | ₹6,000–18,000 |
| Maintenance (annual) | ₹0–24,000 | ₹36,000–1,20,000 | ₹24,000–60,000 |
| Content updates | Developer needed | Self-serve | Self-serve |
| Speed (mobile) | 90–100 PageSpeed | 70–90 PageSpeed | 30–60 PageSpeed |
| Security risk | Near zero | Moderate–high | High |
| 3-year total cost | ₹2,50,000–5,60,000 | ₹4,44,000–10,68,000 | ₹1,60,000–5,34,000 |
The page builder WordPress site looks cheapest upfront. Over 3 years, it often costs more than Astro — and performs significantly worse.
My current rule of thumb
-
Astro for: portfolios, marketing sites, blogs, documentation, anything where speed matters more than dynamic features. Ideal when a developer is available for updates or content lives in markdown.
-
WordPress for: high-velocity editorial sites, e-commerce (WooCommerce), membership sites, client sites where a non-technical person must publish daily. Worth the maintenance overhead when editorial independence is non-negotiable.
-
Hybrid (headless WP + Astro) for: large content sites where you need both editorial workflow and static-site performance. Higher upfront cost, lowest long-term friction.
-
Shopify for: e-commerce where you don’t want to manage infrastructure. WooCommerce for flexibility, Shopify for simplicity.
The question you should actually ask
Stop asking “Astro or WordPress?” Ask instead:
- Who updates this site after launch? If the answer is “a developer,” Astro. If “our marketing person,” WordPress.
- What does this site need to do in 2 years? If it’s still a marketing site, Astro. If it needs e-commerce, memberships, or user accounts — plan for WordPress or headless.
- What’s my maintenance budget? If zero, Astro. If you’re comfortable with ₹5,000–10,000/month for managed hosting and updates, WordPress works.
This very site is Astro + MDX. The next client I’m shipping is headless WP into Astro. The right tool, every time — not the trendy one.