Astro or WordPress for a business website in Morocco?

Most business websites in Morocco run on WordPress. That’s not a mistake — WordPress powers a large share of the web for good reasons. But it isn’t automatically the right answer, and the decision is usually made by default rather than deliberately.

Here’s how I’d actually compare the two for a Moroccan business.

The underlying difference

WordPress builds each page on demand. A visitor arrives, PHP starts, queries a MySQL database, runs the active plugins, assembles the HTML and sends it. That work repeats for every visitor, every time.

Astro builds pages once, at publish time. The result is plain HTML files served from a CDN. The assembly work happens on my machine before deployment, not on a server during your customer’s visit.

Almost every practical difference follows from that one distinction.

Speed

A static site is faster, and the gap widens on the conditions that matter in Morocco: mid-range Android phones on 4G, and servers often located in Europe rather than locally.

Two caveats, because precision matters more than marketing here.

A well-built WordPress site — lightweight theme, few plugins, proper caching, a CDN — is genuinely fast. I’ve seen excellent ones. The difference is that speed is WordPress’s achievement and static’s default.

And speed is a real but minor Google ranking factor. Nobody reached page one because their site was fast. Where it counts is conversion: visitors abandon slow pages, sharply so on mobile past about three seconds.

Security

This is the strongest argument, and the least discussed.

Every WordPress plugin is code running on your server, and an out-of-date plugin is the most common way sites get compromised. It’s not hypothetical — abandoned Moroccan business sites regularly end up redirecting to spam, and deindexed by Google as a result.

A static site has no database and no exposed admin panel. There’s very little to attack. That’s a difference in kind, not degree.

Three-year cost

Delivery price is the wrong comparison. Here’s the shape of the total:

A 6,000 MAD WordPress site realistically costs 8,000–10,000 MAD across three years. A static site stays close to its initial price.

I’ve deliberately left development cost out — it’s comparable, and depends far more on the developer than the technology. Be wary of comparison tables (including ones I’ve seen on Moroccan agency sites) that show WordPress costing four times as much. They inflate the maintenance line and assume you’d pay nothing for a static site’s upkeep.

Content management

The honest gap. WordPress’s editor is mature, familiar, and lets you restructure pages freely.

A static site pairs with a headless CMS — Pages CMS in my case — which exposes defined fields: text, images, blog posts, prices, opening hours. You can change all the content. You cannot drag blocks around or restyle pages.

For most businesses that’s a good trade: you can’t accidentally break the layout, which is the main reason sites drift into incoherence after a year of page-builder editing. But if you genuinely want to recompose pages yourself, WordPress does that better and you should say so upfront.

When WordPress is the right choice

I don’t build everything static, and claiming otherwise would be dishonest. WordPress wins when you have:

• An online shop with real inventory. WooCommerce is mature and solves problems you shouldn’t rebuild.
• User accounts and gated content. Memberships, private areas, per-user data.
• A large editorial team publishing several times daily with approval workflows.
• A niche plugin requirement that only exists in that ecosystem.
• An existing site that works. If your WordPress is clean, fast and maintained, migrating carries risk for little gain. Spend the money on content instead.

When static is the better fit

• Brochure and service sites
• Professional practices — medical, legal, architectural
• Portfolios
• Company sites with a blog
• Multilingual sites, including Arabic RTL
• Landing pages for ad campaigns

That covers the large majority of Moroccan SME websites.

How to decide

Three questions settle it.

Does your site need to do things, or show things? Booking with live availability, payments, accounts — that’s “do,” and WordPress or a custom build is the path. Presenting your business, services and contact details is “show,” and static is ideal.

Who will edit it, and how often? Once a month, one person: a Git CMS is fine. Several people daily: you want a hosted CMS with workflows.

What’s your three-year budget, including maintenance? If recurring cost is a real constraint, static removes an entire category of expense.

If you want a straight answer for your specific case, send me your site URL. I’ll tell you honestly whether changing anything is worth it — including when it isn’t.

---

See also: the website redesign page and the migration checklist.