Static vs WordPress: why static loads faster

“Your site is slow” is a useless diagnosis until someone explains where the time goes. Here’s what actually happens between a click and a visible page — and why the gap between WordPress and a static site widens at almost every step.

The journey of a WordPress page

A visitor in Marrakech clicks your link. Your site is on shared hosting. In order:

1. DNS resolution and connection to the server. If it’s in Europe, every round trip costs 40–80 ms.
2. PHP starts and loads WordPress core, your theme, then every active plugin. Twenty plugins means twenty blocks of code executed on this request.
3. Database queries to MySQL: content, options, menus, plugin settings. A single page can trigger dozens.
4. HTML assembly by the theme.
5. Delivery to the browser, usually alongside the theme stylesheet, several plugin CSS files, jQuery and assorted scripts.
6. The browser downloads and executes all of it before it can show anything useful.

Steps 2 and 3 happen on every visit, for every visitor. The server redoes identical work forever to produce an identical page.

The journey of a static page

1. Connection to an edge server — with a CDN, the file is served from the point of presence nearest the visitor.
2. The HTML file is sent, already generated.
3. It renders.

There is no step 4. The assembly happened once, at build time, on my machine or a build server. The visitor receives the finished result.

That’s the whole difference: compute once for everyone, instead of recomputing for each person.

The caching argument, and its limits

At this point a WordPress developer will say: “just install a caching plugin.” Correct, and effective. A cache serves a pre-generated version of the page and removes steps 2 and 3.

Three caveats.

Caching is remediation, not architecture. You’re adding a layer to avoid work the system shouldn’t have been doing. It holds until a plugin bypasses it — cart, member area, dynamic form.

It doesn’t fix browser weight. Caching speeds up server-side generation. It doesn’t remove jQuery, four stylesheets and assorted plugin scripts from what the visitor downloads. On a mid-range phone over 4G — the reality for much of Moroccan traffic — that’s often where most of the time goes.

It needs maintaining. Misconfigured caches, bad purge rules, plugin conflicts: a recurring source of problems.

A well-built WordPress site — light theme, few plugins, good caching, a CDN — is fast. I’ve seen excellent ones. But it takes skill and ongoing attention, whereas a static site’s speed is the default state rather than an achievement to defend.

Why the gap is amplified in Morocco

Two factors make this more visible here than in Europe.

Server location. Many Moroccan sites are hosted in France. Every network round trip pays for the distance. A static site on a CDN is served from a nearby point of presence.

The device mix. A large share of traffic comes from mid-range phones on 4G. On those devices, executing JavaScript is expensive in CPU time. A page that renders in 1.5 s on a recent iPhone over fibre can take 6–8 s on a 1,500 MAD handset on a congested network. That’s the visitor you should be measuring.

What it actually changes

Worth being honest about the size of the effect.

For SEO: speed is a Google ranking factor, but a minor one. A slow site with excellent content outranks a fast empty one. Nobody reached position one purely because their site was fast. Be sceptical of anyone selling you the opposite.

Where it does matter: with comparable content and authority, speed is a tiebreaker. And a site that’s slow on mobile is actively penalised.

For conversions: the effect is far more direct. Every extra second of waiting loses visitors, and abandonment is steep on mobile past three seconds. On a contact or booking page, that’s revenue.

For costs: static hosting is free on Netlify, Vercel or Cloudflare Pages, versus 600–1,200 MAD a year for decent shared hosting. Over three years the difference covers part of the site.

For security: no database and no exposed execution layer means almost no attack surface. Arguably the strongest argument, and the least promoted.

When WordPress is still the better choice

I don’t build everything static, and it would be dishonest to pretend otherwise.

WordPress remains preferable for an online shop with a large catalogue and stock management, for sites needing user accounts and gated content, when a large team publishes several times daily with approval workflows, or when a specific business plugin exists only in that ecosystem.

Static is the right call for brochure sites, service sites, professional practices, portfolios, blogs and institutional sites — that is, the overwhelming majority of Moroccan SME websites.

How to measure your own site

Three free tools, in order of usefulness:

PageSpeed Insights. Look at the field data if it exists — those are measurements from your real visitors, far more meaningful than the lab score.

WebPageTest, choosing a mobile profile and a 4G connection rather than the defaults.

Your own phone, on mobile data, away from the office. The most honest test, and often the most depressing.

If you want a second opinion on the numbers you get, send me the URL — I’ll tell you what’s holding it back, whether or not you work with me.

---

See also: the website redesign page, which explains how I apply that choice to an existing site.