WordPress vs Webflow vs Astro for small business client sites: a developer's comparison (2026)
Short answer: For most local business clients who want to edit their own pages and might move to another developer one day, WordPress is still the safest default. Webflow is the better pick when you design visually and t
Short answer: For most local business clients who want to edit their own pages and might move to another developer one day, WordPress is still the safest default. Webflow is the better pick when you design visually and the client is happy to pay a yearly site plan ($15/month for Basic or $25/month for Premium with the CMS, billed yearly, as of November 2026) in exchange for no plugin updates. Astro gives you the fastest and cheapest site to host, but it only fits clients who rarely change content or who stay on a care plan with you.
The rest of this post is the detail behind that answer.
A quick definition so we're talking about the same thing. By WordPress we mean self-hosted WordPress (the free software from wordpress.org) or managed WordPress.com. Webflow is a hosted visual site builder with its own CMS. Astro is an open-source framework for content sites that builds to static HTML you can host almost anywhere.
How do WordPress, Webflow and Astro compare at a glance?
WordPress wins on owner familiarity and portability, Webflow on low maintenance for visual designers, and Astro on speed and hosting cost. Here are the values we checked in November 2026:
| WordPress | Webflow | Astro | |
|---|---|---|---|
| Software cost | Free (GPL) | Included in site plan | Free (MIT license) |
| Typical hosting | Any PHP host, or WordPress.com ($25/mo Business, billed yearly) | Webflow only: Basic $15/mo, Premium $25/mo (billed yearly) | Static hosts, e.g. Cloudflare Pages free plan |
| Built-in CMS | Yes | Premium plan only (20,000 items) | No, add Decap, Keystatic or TinaCMS |
| Owner editing | Familiar admin, easy to break layouts with page builders | Edits content on the page, hard to break structure | Only through a Git-based CMS, or you edit for them |
| Default front-end JS | Depends on theme and plugins | Webflow's runtime plus any interactions | Zero JS by default |
| Upkeep | Core, theme and plugin updates | Handled by Webflow | Dependency updates at build time only |
| Leaving | Full export, move to any host | Code export excludes CMS items and pages | Code lives in your Git repo |
How much does each option cost the client per year?
Astro is the cheapest to run, WordPress varies the most, and Webflow is the most predictable. These are platform fees only. Your build and care plan fees sit on top, and a domain name is extra in every case.
WordPress. The software is free. What the client pays depends on where it's hosted. As one checked reference point, WordPress.com lists its Business plan at $25 per month billed yearly ($40 billed monthly), and plugins are available on every paid WordPress.com plan, including Personal at $4 per month billed yearly. Self-hosted on a regular PHP host, prices vary too much between hosts to quote one number. Premium themes, page builders and form or SEO plugins with paid licences add up, and those renew every year.
Webflow. The client pays a site plan per site. As of November 2026 Webflow lists three: Starter (free, webflow.io domain only, 2 static pages), Basic at $15 per month billed yearly (custom domain, 300 static pages, 10 GB bandwidth, no CMS) and Premium at $25 per month billed yearly (adds the CMS with 20,000 items). On your side, the Freelancer workspace is $16 per month billed yearly and includes one free client seat per site. Extra limited seats for people who edit content are $15 per month each.
Astro. The framework is MIT licensed and free. A static Astro site fits comfortably on a free static host. Cloudflare Pages' free plan allows 500 builds a month, one build at a time, and 100 custom domains per project. Two traps on other hosts are worth knowing:
- Netlify's free plan has a monthly credit limit, and when a site hits it, the site is paused until the next billing cycle. That's fine for a demo and a bad surprise for a plumber's homepage.
- Vercel's Hobby plan is for non-commercial personal use only. Vercel's own definition of commercial includes "receiving payment to create, update, or host the site", so a paid client build needs the Pro plan.
Who hosts the site, and who gets the call when it breaks?
With Webflow, Webflow hosts it and you're never debugging a server. With WordPress, someone owns a hosting account, and that someone should be the client, with you added as a user. With Astro, the build output is plain files, so hosting is the easy part, but the Git repo and the deploy pipeline are a thing someone has to own.
Our rule on all three: the client owns the domain registrar account and the hosting or site plan billing, and you get access.
Can the business owner edit the site themselves?
Yes on WordPress and Webflow, and only with extra setup on Astro.
WordPress has the editor most owners have seen before. The risk is the opposite of difficulty: with a page builder, an owner can drag a section, delete a column and break the mobile layout without noticing. Give them the Editor role instead of Administrator, and lock what you can.
Webflow lets the owner click on text and images on the live page and change them, while the layout stays as you designed it. For "change the hours and swap a photo" clients, it's the nicest editing experience of the three.
Astro has no admin panel. Content lives in Markdown or data files in the repo. If the owner needs to edit, you add a Git-based CMS:
- Decap CMS: MIT licensed, free, stores content in your own Git repository.
- Keystatic: MIT licensed, with an official Astro integration; edits content locally or on GitHub.
- TinaCMS: TinaCloud's free plan includes 2 users; the Team plan is $24 per project per month billed yearly.
Our honest take: most local business owners edit their site about twice a year. For them, "email us and we'll change it today" on a care plan beats any CMS.
Which one is fastest for Core Web Vitals?
Astro, by default. Astro's docs describe it as "zero JS, by default", rendering HTML on the server and adding client-side JavaScript only where you ask for it. On a brochure site for a dentist or a roofer, that means there's little to slow the page down unless you add it.
WordPress can be just as fast with a lean block theme and few plugins; it's usually slow because of a heavy page builder, a slider and five tracking tags. Webflow sits in between: reasonably clean output, but interactions, fonts and embeds add weight like anywhere else. On any platform, the same targets apply: LCP of 2.5 seconds or less, INP of 200 ms or less and CLS of 0.1 or less, at the 75th percentile of page loads.
How much maintenance does each one need?
WordPress needs the most, Webflow the least, and Astro needs some only when you rebuild.
WordPress maintenance is mostly plugin maintenance. Patchstack's 2026 report counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025: 91% in plugins, 9% in themes, and only 6 in WordPress core. Fewer plugins is the single best maintenance decision you can make, and a monthly update routine with backups is the minimum for any WordPress client.
Webflow patches its own platform. Your job is content and design changes.
An Astro static site has no server-side code running in production, so there's nothing to patch on the live site. The work shows up later: when you come back after a year to change something, expect to update dependencies before the build runs cleanly.
How locked in is the client on each platform?
WordPress is the most portable, Astro is close behind, and Webflow is the one to explain before signing.
A WordPress site can be exported and moved to any host. An Astro site is a folder of source code in a Git repo, and the output is plain HTML that any static host can serve. In January 2026 Cloudflare announced it had acquired the company behind Astro and said Astro "will remain open source"; the framework is still MIT licensed, and the Astro team said it would stay the best option "whether they host on Cloudflare or elsewhere."
Webflow offers code export on its Core and Growth workspace plans, but its pricing page states that dynamic content, meaning CMS items and CMS pages, can't be exported that way. Static pages come out as HTML and CSS; the blog, service area pages or anything else in the CMS would need rebuilding elsewhere. That's not a reason to avoid Webflow. It's a reason to tell the client before they commit.
So which one should you pick for a given client?
Match the platform to how the owner will treat the site, not to what you enjoy building.
Three fictional examples:
- A fictional two-van plumbing company that wants a fast five-page site and will never log in: Astro on a free static host, with you on a small care plan.
- A fictional bakery whose owner wants to post weekly specials and new photos herself: Webflow Premium, or WordPress with a simple block theme if budget is tight.
- A fictional law office that wants a blog, a booking plugin and the option to hire a different agency later: WordPress.
Whichever you choose, write it down for the client. A handover note like this saves an awkward call in two years:
Your site runs on Webflow (Premium site plan, billed yearly to your card). You own the domain at your registrar. Webflow handles hosting and security updates. You can edit text and photos yourself; we handle layout changes. If you ever leave Webflow, the pages can be exported, but blog posts would need to be moved by hand.
Where to find clients who need a rebuild
The manual way works: search a trade and a town, open the sites on your phone, and note which ones are slow, broken on mobile or obviously unmaintained.
If you'd rather start from a list, LeadReef finds local businesses whose websites are outdated, broken on mobile or missing, shows what's wrong with each one, and helps with a first mockup and outreach message. You choose who to contact and send everything yourself. The free plan includes your first 10 leads. If you already work with an AI assistant, you can connect it to Claude, ChatGPT or Cursor over MCP and ask for leads in plain words. Full disclosure: we build LeadReef. Everything above works without it.
Frequently asked questions
Is Webflow more expensive than WordPress for a small business?
Usually a little, in platform fees. As of November 2026 Webflow's Basic plan is $15 per month and Premium is $25 per month, both billed yearly, while WordPress hosting ranges from very cheap shared plans to managed plans like WordPress.com Business at $25 per month billed yearly. WordPress often ends up costing more once you add paid plugin licences and maintenance time.
Can a non-technical business owner update an Astro site?
Not without help. Astro has no built-in admin, so you either add a Git-based CMS such as Decap CMS, Keystatic or TinaCMS, or you make the changes for them on a care plan.
Can I host a client's Astro site for free?
Technically yes, on hosts like Cloudflare Pages, whose free plan allows 500 builds a month. Avoid hosts where free plans pause sites at a usage limit, and note that Vercel's Hobby plan doesn't allow commercial use, which includes being paid to build or host the site.
Can you export a Webflow site and leave?
Partly. Webflow's code export (on Core and Growth workspace plans) gives you HTML and CSS for static pages, but CMS items and CMS pages can't be exported that way and would need to be rebuilt.
Is WordPress still a good choice in 2026?
Yes, for clients who want control and portability. W3Techs reports WordPress on 39.5% of all websites as of November 2026, which means a client can find someone else to work on it. The cost is plugin maintenance, which you should price into a care plan.
Sources (all checked November 2026): Webflow, Pricing; WordPress.com, Pricing; Cloudflare Docs, Pages limits; Netlify, Pricing; Vercel Docs, Fair use guidelines; Astro Docs, Why Astro?; Astro LICENSE; Cloudflare, Cloudflare acquires Astro (January 16, 2026); Decap CMS; Keystatic; TinaCMS, Pricing; Patchstack, State of WordPress Security in 2026; W3Techs, Usage statistics of WordPress; web.dev, Web Vitals.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.

