# WordPress or Astro: Choose by What the Site Connects To

> WordPress and Astro both suit business websites, and the choice depends on what the site connects to, who edits it and who maintains it.

- Source: https://choatecatalysts.com/canon/wordpress-or-astro/
- Author: Douglas Choate, Choate Catalysts (https://choatecatalysts.com/craft/douglas-choate/)
- Published: 2026-11-13
- Collection: The Canon (https://choatecatalysts.com/canon/)

---

## At a Glance

- WordPress and Astro are both open source, and each can run a firm's website well.
- In Chrome's records of real visits in October 2026, 84% of Astro sites in the United States passed Google's speed measures on phones, against 63% of WordPress sites.
- Hosted builders such as Wix and Shopify pass at similar rates to Astro, so speed alone does not decide between platforms.
- The deciding points are what the site connects to, who edits it, who maintains it and the work of moving an existing site.

WordPress and Astro, a newer system for building a firm's website, are usually compared on speed. On that measure Astro leads WordPress clearly, but the same data shows that speed does not separate Astro from several other platforms.

HTTP Archive identifies the technology behind millions of websites each month, and Google's Chrome browser records how those sites perform for real visitors. [Among sites with enough US visitors to measure](https://httparchive.org/reports/techreport/comparison?tech=Astro,WordPress&geo=United%20States%20of%20America&rank=ALL) in October 2026, about 10,000 ran Astro and 330,000 ran WordPress. On phones, 84% of the Astro sites passed Core Web Vitals, Google's three measures of how quickly a page loads, responds and stops shifting, against 63% of the WordPress sites.

## Speed Separates WordPress From the Field, Not Astro

| Platform | Sites | Passing |
|---|---|---|
| Wix | 34,241 | 89% |
| Shopify | 118,272 | 86% |
| Astro | 10,072 | 84% |
| Squarespace | 40,344 | 83% |
| Webflow | 15,239 | 81% |
| All US sites | 1,231,797 | 64% |
| WordPress | 330,180 | 63% |

The table shows the number of sites measured and the share that passed on phones, from the [HTTP Archive Tech Report](https://httparchive.org/reports/techreport/comparison?tech=Wix,Shopify,Astro,Squarespace,Webflow,WordPress&geo=United%20States%20of%20America&rank=ALL) for the United States in October 2026.

The table changes the reading of the headline figure. Astro's lead is over WordPress, and hosted builders pass at the same rate or higher. Speed alone therefore points to several platforms, and what separates them is [who owns the site](/canon/the-codes-test/) and what it can connect to.

The figures also describe the teams that build on each platform as much as the platforms themselves. Astro tends to be chosen by teams that put performance first, while WordPress runs everything from carefully tuned publications to sites nobody has maintained in years. The build matters inside WordPress as well: sites made with one widely used page builder pass at 56%.

Astro [describes itself](https://docs.astro.build/en/concepts/why-astro/) as "the web framework for building content-driven websites like blogs, marketing, and e-commerce," and by default it sends visitors finished pages built on the server. Its use roughly tripled in a year, from about 18,000 sites to [about 55,000](https://httparchive.org/reports/techreport/tech?tech=Astro&geo=ALL&rank=ALL) in HTTP Archive's worldwide crawl. WordPress remains far larger: [W3Techs](https://w3techs.com/technologies/overview/content_management) put it on 39.2% of websites on November 13, 2026, and Astro on 0.2%.

## An Existing Site Changes the Calculation

Most firms weighing this choice already have a WordPress site, so the decision is whether to move. Moving to Astro means rebuilding the page templates, moving the content, redirecting every old address to its new one and replacing whatever plugins were doing for visitors, such as forms and search. A WordPress site that is fast and well maintained often has the stronger case for staying.

## Three Things Decide the Choice

**What the site connects to.** A site that takes orders, runs member logins, books appointments or feeds a customer relationship management (CRM) system needs software for each of those jobs. WordPress has mature plugins for most of them, in a [directory of more than 79,000](https://wordpress.org/plugins/). On Astro each connection is built or bought separately, which suits a site that has few. The more of those jobs a site needs ready-made, the stronger the case for WordPress over Astro becomes. A firm whose site is mainly a store also has hosted commerce platforms to weigh.

**Who edits it.** WordPress is a content management system, software that gives non-technical staff a screen for editing pages. Astro itself has no editing screen. Its content lives in files or in a separate content management system, so a firm that publishes every week needs that system chosen before launch. One such system is new. Cloudflare, the infrastructure company that [acquired Astro's maker](https://blog.cloudflare.com/astro-joins-cloudflare/) in January 2026, [released version 1.0 of EmDash](https://blog.cloudflare.com/emdash-cms-plugin-registry/) in September, an open source content management system built on Astro with an admin screen for editors. A firm that picks it is picking a young product beside WordPress's two decades.

**Who maintains it.** WordPress needs steady upkeep, and part of it is security. A WordPress site runs code on every visit, and in July 2026 WordPress issued a release for a flaw [it rated critical](https://wordpress.org/news/2026/07/wordpress-7-0-2-release/), with further security releases through October. The core software, each plugin and [PHP, the language beneath them](/canon/wordpress-php-expiration-date/), all need updating. A pre-built Astro site runs no such code on the server, which removes most of that exposure, although forms or logins added to it bring their own. Astro keeps a calendar too: its team [supports only the newest major version](https://docs.astro.build/en/upgrade-astro/), with security fixes for one version back, and most changes to an Astro site need a developer.

## The Two Can Be Combined

WordPress can serve as a headless content management system, an arrangement in which staff edit in WordPress while a separate system builds the pages visitors see. [Astro's documentation](https://docs.astro.build/en/guides/cms/wordpress/) covers it, noting that WordPress includes a built-in interface through which Astro can read its content.

The combination keeps the editing screen staff already know and delivers pages built by Astro. It also gives up much of what plugins do for visitors, because anything a plugin displays, such as a form or a checkout, has to be rebuilt on the Astro side, and it leaves two systems to maintain. It suits firms with enough content and traffic to justify both.

## How the Choice Plays Out

Consider two firms. The first is a 12-person architecture practice with 30 pages, a web builder on retainer and nobody editing in house. It has little to connect and little to edit, so Astro fits. The second is a regional training company that sells courses, manages student logins and issues certificates. Its site is closer to an application than a brochure, and WordPress gets it there with less custom work because plugins already do each job.

The data suggests the speed gap owes more to how WordPress sites are built and kept than to any advantage unique to Astro. That leaves the decision resting on connections, editing, maintenance and the work of moving.
