--- title: "Astro vs WordPress (2026): Cost, Speed and Which to Pick" description: "Astro vs WordPress compared on editing, plugin upkeep, yearly hosting cost and real-user speed, with headless WordPress as a middle path." url: "https://dardo.studio/en/blog/astro-vs-wordpress/" language: "en" translations: {"es":"https://dardo.studio/es/blog/astro-o-wordpress/","pt":"https://dardo.studio/pt/blog/astro-ou-wordpress/"} updated: "2026-10-22T19:49:07.229Z" --- [Blog](https://dardo.studio/en/blog/) # Astro vs WordPress in 2026: editing, upkeep, yearly cost, speed and when to move Astro vs WordPress for a marketing site: editing, plugin upkeep, yearly hosting cost and real-user speed, plus headless WordPress and when to stay. By [Nicolás Cerón](https://www.linkedin.com/in/nicoceron/) · October 22, 2026 ![An ivy-covered brick townhouse stands beside a slim modern glass house with a crimson front door on a wet cobbled street at night](https://dardo.studio/_astro/01M5JG24CHANAZBDB1TTDADTJA_2oawvW.webp) ## Key takeaways - In September 2026, 71.1% of Astro sites passed Core Web Vitals on mobile against 48.3% of WordPress sites, mostly because more Astro sites load fast (81.1% good LCP against 55.4%). - For a 40-page site with a 150-post blog, WordPress hosting cost USD 300 to 540 a year as of October 2026; a static Astro site on Cloudflare Workers Free cost nothing to host, plus up to USD 540 a year for a hosted CMS. - Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 91% of them in plugins; a static Astro site runs no server code when a visitor arrives, but its dependencies still need upgrades. - Headless WordPress keeps wp-admin for editors and lets Astro render the public site, at the price of still hosting and patching WordPress. - Stay on WordPress when WooCommerce, memberships or a page-builder workflow carry the business; pick a hosted builder when marketers must lay out pages without a developer. ## The short answer Choose Astro when the site is mostly pages and articles that look the same to every visitor, a developer is available for layout changes, and you want less software to patch. Stay on WordPress when plugins do real work for the business, such as a WooCommerce store, memberships or courses, or when many writers and a page builder are how your team publishes. If editors like wp-admin but the site is slow or hard to secure, keep WordPress for editing and let Astro build the public site. Astro leads on speed and running cost: in September 2026, 71.1% of Astro sites passed Core Web Vitals on mobile against 48.3% of WordPress sites, and a static Astro site on Cloudflare Workers can cost nothing to host. WordPress leads on ecosystem: a plugin for almost any feature and an admin panel most editors know. Where we stand: dardo.studio runs on Astro with a headless CMS, we build these sites through our [Astro development](https://dardo.studio/en/services/astro-development/) service, and we maintain WordPress sites other teams built. Prices are as of October 2026, in US dollars before tax. ## Editing: wp-admin and plugins, or a headless CMS and Git WordPress is the editing tool and the website in one install. Editors write in the block editor inside wp-admin and publish with one button. Roles are built in and free per user: a Contributor drafts, an Author publishes their own posts, an Editor publishes everyone's. Plugins add SEO fields, forms, custom fields and page builders, which give marketers drag-and-drop layouts and more ways to break them. Astro has no admin panel. Its documentation says that for editing you'll want a headless CMS, and it lists 45 CMS guides, from Sanity, Contentful and Payload to WordPress itself. Two setups cover most sites: - A hosted headless CMS. Editors work in a web interface with fields, drafts and previews, and the site rebuilds when they publish. On dardo.studio an article goes live two to three minutes after an editor publishes it. - Markdown files in Git. Content sits in the repository as content collections, each with a schema, so an entry with a missing field stops the build instead of reaching visitors. Git-based editors such as Decap CMS, Keystatic and TinaCMS add a web interface for people who don't use Git. The trade-off is layout freedom. Editors fill in fields and arrange sections a developer built; a new page design goes through that developer. That keeps the site on brand and light, and it's the wrong model for a team that invents layouts every week. The CMS shapes the editors' day more than the framework, so choose it with them; our comparison of [Sanity, Contentful and Payload](https://dardo.studio/en/blog/sanity-vs-contentful-vs-payload/) covers the common picks. Astro development Want Dardo to do this for you? Tell us what you need. Nico replies personally within one business day. [Get a proposal](https://dardo.studio/en/contact/?service=astro-development) · [See the service](https://dardo.studio/en/services/astro-development/) ## Plugins, security and upkeep A WordPress site is PHP code and a database answering visitors from a server, so the server software, core, the theme and every plugin need updates. WordPress.org recommends PHP 8.3 or later and MySQL 8.0 or MariaDB 10.11 or later, with HTTPS. Its hardening guide is direct: older WordPress versions get no security updates, plugins should always be current, unused ones deleted, and databases backed up regularly. Plugins are where the risk sits. Patchstack, which sells WordPress security, counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 42% more than in 2024: 91% in plugins, 9% in themes and only six in core, with 46% unfixed when made public. Since WordPress 5.5 you can turn on automatic updates plugin by plugin; they run twice a day, and the documentation suggests making sure you can roll back first. Astro's upkeep is different. A fully static build is a folder of files: no code runs on a server when a visitor arrives, and a missed upgrade leaves the same files in place. The work moves into the repository: dependency updates and major versions, where Astro's core team provides security fixes for only one previous major. Any route rendered on request, such as a form handler or a draft preview, is server code and needs patching like any server. ## What a 40-page marketing site costs to run each year Take a typical B2B marketing site: 40 pages and a 150-post blog in English, edited by three people, with contact and demo-request forms, fewer than 25,000 visits a month and nothing sold online. These are hosting and software costs only, billed yearly where offered; the build, domain, email and staff time are left out. | Line item | WordPress, lower cost | WordPress, managed host | Astro, Markdown in Git | Astro, hosted CMS | | ------------- | ----------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------ | ---------------------------------------------------------- | | Hosting | WordPress.com Business, USD 25 a month: USD 300 | WP Engine Essential: USD 420 (USD 336 the first year) | Cloudflare Workers Free: USD 0 | Cloudflare Workers Free: USD 0 | | Editing | wp-admin, included: USD 0 | wp-admin, included: USD 0 | Files in the repository: USD 0 | Sanity Free: USD 0; Sanity Growth for three seats: USD 540 | | SEO and forms | Yoast SEO and Contact Form 7, both free: USD 0 | Same: USD 0 | Built into the templates, plus a Worker form endpoint: USD 0 | Same: USD 0 | | Updates | Your team's time | Smart Plugin Manager, USD 10 a month: USD 120 | Your developer's time | Your developer's time | | Per year | USD 300 | USD 540 (USD 456 the first year) | USD 0 | USD 0 to 540 | ### Why these choices - WordPress.com Business is USD 25 a month billed yearly (USD 40 month to month), with plugins, SSH, backups with one-click restore and unlimited visitors. Its page showed no renewal price on 22 October 2026; confirm it at checkout. - WP Engine's Essential plan for one site is sized for 25,000 visits a month with daily backups, at USD 420 a year with a 20% first-year discount on 15 October 2026. Its Smart Plugin Manager applies plugin updates with visual regression tests; someone still fixes what breaks. - Cloudflare Workers serves static assets free and without limit, with no bandwidth charge. The Free plan adds 100,000 Worker requests a day, plenty for a form endpoint; Workers Paid starts at USD 5 a month. - Sanity's Free plan covers up to 20 seats and 10,000 documents, with public datasets only. Growth adds private datasets at USD 15 per seat per month. Headless WordPress means paying both sides, about USD 300 to 600 a year here. In every column the software bill is small next to the build. The bigger difference is upkeep: WordPress needs someone applying and checking plugin updates promptly, and Astro needs a developer for upgrades and layout changes. If you pay someone for that, add a [maintenance plan](https://dardo.studio/en/services/website-maintenance/): ours start at USD 79 a month, or USD 948 a year. ## Speed: what field data shows, and what it doesn't Our [website platform speed report](https://dardo.studio/en/tools/website-platform-speed-report/) reads the HTTP Archive's technology report, which pairs Google's Chrome UX Report data from real visitors with the platform each site runs on. For September 2026: | Measure, September 2026 | Astro | WordPress | | ------------------------------------------- | ------- | --------- | | Sites measured on mobile | 47,277 | 2,658,175 | | Pass all Core Web Vitals, mobile | 71.1% | 48.3% | | Pass all Core Web Vitals, desktop | 84.6% | 53.7% | | Good loading (LCP), mobile | 81.1% | 55.4% | | Good responsiveness (INP), mobile | 85.0% | 90.3% | | Good layout stability (CLS), mobile | 93.6% | 87.3% | | Median page weight, mobile | 1.36 MB | 2.72 MB | | Median JavaScript, mobile | 409 KB | 677 KB | | Median images, mobile | 355 KB | 1.04 MB | | Median Lighthouse performance score, mobile | 70 | 43 | The gap is in loading. The median Astro home page weighs half as much, with about a third of the image bytes. WordPress does better on responsiveness, 90.3% against 85.0%. In the United States both pass more often: 84.2% of Astro sites and 62.0% of WordPress sites. Read these as typical sites, not as what a careful build achieves. The HTTP Archive measures the home pages of sites it detects on each platform, and the audiences differ: 2.66 million WordPress sites, from neglected blogs on shared hosting to large publishers, against about 47,000 Astro sites. Page builders pull WordPress down; with Elementor, 36.3% passed on mobile worldwide. A WordPress site on good hosting, with a light theme, few plugins and edge caching, can pass. Before moving for speed, check your own pages in Search Console's Core Web Vitals report. ## SEO and AI-search controls Neither platform ranks a site by itself; content, links and competition do. What differs is where the technical controls live: in plugins on WordPress, in the code on Astro. | Control | WordPress | Astro | | ------------------------------------ | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | | Titles, descriptions, canonical tags | An SEO plugin such as Yoast SEO, with a free version | Written into the page layout and filled from CMS fields | | XML sitemap | In core since WordPress 5.5 at /wp-sitemap.xml; SEO plugins replace it | The sitemap integration builds one from static routes; it can't list dynamic routes rendered on request | | robots.txt | Generated by WordPress unless you upload a file; changed with a filter or an SEO plugin | A file in the repository, or one generated from the site's address at build time | | Structured data | Generated by SEO plugins | JSON-LD written once per template from content fields | | 301 redirects | A redirect plugin or rules at the host | Rules at the host | | AI crawler rules and llms.txt | Rules through a plugin or filter; llms.txt uploaded as a file | Files versioned and reviewed with the code | WordPress SEO plugins give editors a form for every setting. On Astro, a setting exists only if the developer added a field, so ask for SEO title, description, social image and a noindex switch from the start. For AI search, the controls are the same files on both: robots.txt rules per crawler, an llms.txt file and clean HTML with structured data. Our guide to [blocking AI crawlers in robots.txt](https://dardo.studio/en/blog/block-ai-crawlers-robots-txt/) explains each crawler. The host can help either platform: Cloudflare's managed robots.txt, on all plans, can add AI-crawler rules in front of the site's own robots.txt. Our free [AI visibility checker](https://dardo.studio/en/tools/ai-visibility-checker/) shows what a site allows today. ## Stores, memberships and forms This is where WordPress plugins earn their keep. WooCommerce, free and open source, adds products, cart and checkout to the same install, and membership, course and booking plugins handle gated content. Stores need stronger hosting (WP Engine sells an eCommerce Performance Pack at USD 99 a month on top of its plans), but one team runs everything from wp-admin. Astro has no store or login of its own. Its e-commerce guide describes payment overlays such as Lemon Squeezy and Paddle, or cart and checkout through Snipcart; its authentication guide says there is no official solution and covers Better Auth, Clerk, Lucia and Scalekit. Logins need routes rendered on request, with an adapter, and each service adds an account and a bill. That suits a site selling a few products or gating a resource library. A store that is the business belongs on a commerce platform; our [Shopify vs WooCommerce comparison](https://dardo.studio/en/blog/shopify-vs-woocommerce/) prices both. Forms are simple on both. WordPress uses a plugin such as Contact Form 7, free and with 10 million or more active installs. Astro uses Actions on pages rendered on request, or a small Worker endpoint that sends each submission to your inbox or CRM. ## Headless WordPress with Astro: the middle path You can keep wp-admin and let Astro render the public site. WordPress ships a REST API that anyone can read without authentication by default, and Astro's WordPress guide fetches posts and pages from it, with WPGraphQL as an option. Editors keep the dashboard, roles and editorial plugins; visitors get pages built ahead of time. What it costs you: - You still run WordPress: hosting, core and plugin updates, though the install no longer faces the public. - Anything the theme did is rebuilt in Astro: layouts, page-builder sections, forms, search and comments. - Custom post types need REST support switched on, and some hosts and security plugins block the API; one of eight WordPress sites we checked in October 2026 answered 401. - Publishing triggers a rebuild through a webhook, and draft previews need their own route. It fits a large editorial team that likes WordPress, a site whose speed problem is the theme, or a first step before leaving WordPress. Our [headless CMS development](https://dardo.studio/en/services/headless-cms-development/) service sets up either side. ## When to stay on WordPress, and when to choose neither ### Stay on WordPress when - A plugin is the business: a WooCommerce store, memberships, courses, bookings or a directory, and rebuilding it would cost more than maintaining it. - Many people write and an editor approves, and you don't want to pay per seat for them. - Marketers build new layouts every week in a page builder, and there is no budget for developer changes. - Your pages already pass Core Web Vitals, rank well and get updated by someone reliable. Averages favoring Astro aren't a reason to move on their own. ### Choose neither when - Marketers need to design and publish pages visually, without a developer and without plugins to patch. A hosted builder fits better; see [Webflow vs WordPress](https://dardo.studio/en/blog/webflow-vs-wordpress/) and [Framer vs WordPress](https://dardo.studio/en/blog/framer-vs-wordpress/). - Selling is the main job. Start from a commerce platform and keep the content site beside it. - Most of the project is a signed-in product with dashboards and shared state. Next.js is the better base, and our [Astro vs Next.js comparison](https://dardo.studio/en/blog/astro-vs-nextjs/) draws the line. - One person runs a small site with no technical help. A hosted builder that includes hosting and updates is the safer default. ## What moving from WordPress to Astro involves It's a migration, not a redesign, and the work that protects rankings is the same whether you go headless or move the content out: 1. List every URL that earns visits or links, from /wp-sitemap.xml or your SEO plugin's sitemap, plus Search Console's page report. 2. Decide between headless and a full move. For a full move, export the content and copy wp-content/uploads, where the images live. 3. Carry over the SEO titles and descriptions your plugin stored. 4. Rebuild the templates as Astro components and replace the plugins that worked on the front end: forms, search and comments. 5. Keep the permalink structure, trailing slash included, and set 301s at the host for every changed URL, plus feeds, shortlinks, attachment pages and author archives. 6. Launch, keep the old install private until checks pass, and watch Search Console for the following weeks. Our [WordPress to Astro guide](https://dardo.studio/en/blog/wordpress-to-astro/) walks through each step, and our [WordPress to Astro migration service](https://dardo.studio/en/services/wordpress-to-astro/) does the whole move, from URL inventory to redirects. For a straight answer on whether to move at all, [send us the site](https://dardo.studio/en/contact/?service=wordpress-to-astro) and we'll say which path we'd take before quoting. ## Common questions **Is Astro faster than WordPress?** On average, yes. In September 2026, 71.1% of Astro sites passed Core Web Vitals on mobile against 48.3% of WordPress sites, and the median Astro home page weighed half as much. Those are averages of very different sites: a WordPress site with a light theme, few plugins and good hosting can pass too. Check your own field data before moving for speed. **Is Astro cheaper to run than WordPress?** Usually, on hosting. For a 40-page site with a 150-post blog, WordPress hosting cost USD 300 to 540 a year as of October 2026, while a static Astro site on Cloudflare Workers Free cost nothing to host, plus up to USD 540 a year for a hosted CMS. The build costs far more, and both need someone to handle updates. **Can non-developers edit an Astro site?** Yes, through a CMS. Editors work in a web interface such as Sanity, Storyblok or WordPress itself, or a Git-based editor such as Decap CMS, and the site rebuilds when they publish. What they can't do without a developer is create new page layouts. **Can I keep WordPress and use Astro?** Yes. Headless WordPress keeps wp-admin for editing while Astro builds the public site from the WordPress REST API. You still host and update WordPress, and anything the theme did, such as forms or page-builder layouts, is rebuilt in Astro. **Is Astro better than WordPress for SEO?** Neither ranks a site by itself. Both can serve complete HTML with titles, canonical tags, sitemaps and structured data. WordPress gets these through plugins with forms for editors; on Astro they exist only if the developer builds them. Astro sites pass Core Web Vitals more often, which helps, but content and links decide rankings. **Can Astro run an online store or a membership site?** Through outside services. Astro's docs describe payment overlays such as Lemon Squeezy and Paddle, Snipcart for cart and checkout, and authentication libraries such as Better Auth and Clerk. When the store or membership is the business, WooCommerce or a commerce platform is usually simpler. **Will I lose rankings if I move from WordPress to Astro?** Not if every URL that earns visits keeps working. Keep the permalink structure, carry over titles and descriptions, set 301 redirects at the host for anything that changes, including feeds and attachment pages, and watch Search Console after launch. Rankings usually drop because old URLs break, not because of the platform. ## Sources & further reading Sources behind this page, with further detail from the original publishers. - [HTTP Archive: Technology report (September 2026)](https://httparchive.org/reports/techreport/tech) · httparchive.org - [Patchstack: State of WordPress Security in 2026](https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/) · patchstack.com - [WordPress.org: Requirements](https://wordpress.org/about/requirements/) · wordpress.org - [WordPress Developer Resources: Hardening WordPress](https://developer.wordpress.org/advanced-administration/security/hardening/) · developer.wordpress.org - [WordPress.org Documentation: Plugin and themes auto-updates](https://wordpress.org/documentation/article/plugins-themes-auto-updates/) · wordpress.org - [WordPress.org Documentation: Roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) · wordpress.org - [WordPress Developer Resources: do\_robots()](https://developer.wordpress.org/reference/functions/do%5Frobots/) · developer.wordpress.org - [Make WordPress Core: New XML sitemaps functionality in WordPress 5.5](https://make.wordpress.org/core/2020/07/22/new-xml-sitemaps-functionality-in-wordpress-5-5/) · make.wordpress.org - [WordPress.org Plugins: Yoast SEO](https://wordpress.org/plugins/wordpress-seo/) · wordpress.org - [WordPress.org Plugins: Contact Form 7](https://wordpress.org/plugins/contact-form-7/) · wordpress.org - [WordPress.com: Pricing](https://wordpress.com/pricing/) · wordpress.com - [WP Engine: Plans and pricing](https://wpengine.com/plans/) · wpengine.com - [WooCommerce: WooCommerce](https://woocommerce.com/woocommerce/) · woocommerce.com - [Cloudflare Docs: Workers pricing](https://developers.cloudflare.com/workers/platform/pricing/) · developers.cloudflare.com - [Cloudflare Docs: Managed robots.txt](https://developers.cloudflare.com/bots/additional-configurations/managed-robots-txt/) · developers.cloudflare.com - [Astro Docs: Headless WordPress & Astro](https://docs.astro.build/en/guides/cms/wordpress/) · docs.astro.build - [Astro Docs: Use a CMS with Astro](https://docs.astro.build/en/guides/cms/) · docs.astro.build - [Astro Docs: Content collections](https://docs.astro.build/en/guides/content-collections/) · docs.astro.build - [Astro Docs: On-demand rendering](https://docs.astro.build/en/guides/on-demand-rendering/) · docs.astro.build - [Astro Docs: Actions](https://docs.astro.build/en/guides/actions/) · docs.astro.build - [Astro Docs: Authentication](https://docs.astro.build/en/guides/authentication/) · docs.astro.build - [Astro Docs: E-commerce](https://docs.astro.build/en/guides/ecommerce/) · docs.astro.build - [Astro Docs: Upgrade Astro](https://docs.astro.build/en/upgrade-astro/) · docs.astro.build - [Astro Docs: @astrojs/sitemap](https://docs.astro.build/en/guides/integrations-guide/sitemap/) · docs.astro.build - [Sanity: Pricing](https://www.sanity.io/pricing) · sanity.io [Nicolás Cerón](https://www.linkedin.com/in/nicoceron/) Nicolás Cerón is the founder of Dardo, a brand, web design and development studio in Bogotá, Colombia. ## Related articles - [**Astro website performance: what dardo.studio measures**Field Core Web Vitals, Lighthouse runs, page weight and running cost for dardo.studio, an Astro site on Cloudflare Workers, including what failed.](https://dardo.studio/en/blog/astro-website-performance/) - [**Sanity vs Contentful vs Payload: the best headless CMS for your team in 2026**Sanity, Contentful, Payload, Strapi and Storyblok compared on hosting, previews, translations, export and real monthly cost for 5- and 12-person teams.](https://dardo.studio/en/blog/sanity-vs-contentful-vs-payload/) - [**Webflow alternatives in 2026: what each one costs to run, and what it takes to move off Webflow**Framer, WordPress, a coded site, Wix Studio, Squarespace or HubSpot: what each costs to run a 20-page site with a blog, and what leaving Webflow takes.](https://dardo.studio/en/blog/webflow-alternatives/) - [**Webflow pricing 2026: what changes at renewal, what you'll pay and when to leave**Webflow merged its CMS and Business plans into Premium. What your site pays at renewal, with the math, and when staying beats moving to Framer or Astro.](https://dardo.studio/en/blog/webflow-pricing-2026/) ## Keep exploring. - [Service · **Astro development: fast content sites and migrations**](https://dardo.studio/en/services/astro-development/) - [Your project · **Start a conversation**](https://dardo.studio/en/contact/)