Why static HTML beats WordPress for trades websites

First, what is static HTML?

When you visit a website, your browser requests a page and the server sends it back. The question is: how does the server produce that page?

With WordPress, the process goes like this: the server receives the request, queries a database for the content, runs PHP code to assemble the page, processes whatever plugins are active, and then sends the finished HTML to your browser. All of that happens in real time, on every visit, for every visitor.

With static HTML, the process is: the server receives the request, sends the HTML file. That's it. The file already exists. There's nothing to process.

Static HTML is just files. Fast, dumb, reliable files.

Why that matters for speed

The WordPress process — database query, PHP processing, plugin stack — takes time. On a decent server, maybe half a second. On shared hosting (what most small business WordPress sites use), often two or three seconds. Add in unoptimised images, render-blocking scripts, and multiple plugin stylesheets loading in sequence, and you're looking at five, six, seven second load times on mobile.

A static HTML site sends pre-built files from a CDN (content delivery network) — a network of servers distributed around the world that serves files from the location nearest to the visitor. There's no processing, no database, nothing to go wrong. Load times under half a second are normal. PageSpeed scores of 95+ are standard.

Why that matters for security

WordPress has a database. Databases can be compromised. WordPress has plugins. Plugins have vulnerabilities. WordPress has an admin login page. Login pages can be brute-forced.

Static HTML has none of these things. There is no database to compromise. There are no plugins to exploit. There is no login page. The attack surface is essentially zero.

This matters because WordPress sites are attacked constantly — not because anyone is specifically targeting your business, but because automated bots scan the entire internet looking for WordPress sites with known plugin vulnerabilities. They find them within hours. If your site is running an outdated plugin with a known security hole, you will be found.

The attacks are rarely obvious. The most common goal is to inject spam links or hidden pages that Google's crawlers find and penalise your site for. You might not know for months. By then, you've lost ranking positions you won't easily get back.

Why it matters for SEO

Page speed is a direct Google ranking factor. Faster sites rank higher, all else being equal. A static HTML site consistently outperforms WordPress on every speed metric Google measures:

• Largest Contentful Paint (LCP) — how long it takes for the main content to appear. Static sites excel here.
• First Input Delay (FID) — how quickly the page responds to interaction. Without a heavy plugin stack, interaction is immediate.
• Cumulative Layout Shift (CLS) — how much the page moves around as it loads. Static sites with explicit image dimensions have essentially zero CLS.

These three metrics make up Google's Core Web Vitals — the speed and experience signals Google uses as ranking factors. A well-built static HTML site scores green on all three. A typical WordPress site often fails all three.

Why barely anyone offers it

If static HTML is faster, more secure, and better for SEO, why does almost everyone still build WordPress sites?

The honest answer is that WordPress is easier to sell and easier to build for most agencies. WordPress has a dashboard that clients can update themselves, which feels like a feature. WordPress themes make building sites faster for agencies. WordPress plugins handle complex functionality without custom code. And most clients don't know enough to ask why their site is slow or insecure — they just know it exists.

Static HTML requires writing code. It requires understanding SEO properly rather than relying on a plugin for it. It requires knowing how to configure Netlify, how to set up security headers, how to structure HTML for accessibility. There are no shortcuts. It's harder to build and easier to get wrong — which is why most agencies don't bother.

We bother because it produces better results. A static site loads faster, ranks better, can't be hacked the same way, and stays consistent forever without maintenance. For a trades business that just wants a website that works, it's the right choice.

What static HTML can't do

Honesty requires acknowledging the limitations:

• No CMS dashboard — you can't log in and change your own content. Changes need to go through a developer. For most trades websites where the core content rarely changes, this is a minor inconvenience rather than a real problem.
• No built-in blog without a build process — adding a blog requires either a static site generator (which adds complexity) or writing HTML directly. We handle this for care plan clients; otherwise it's a one-off request.
• Complex applications aren't suitable — if you needed an ecommerce store, a booking system with real-time availability, or user accounts, static HTML alone wouldn't be enough. For a trades business, none of those are needed — a contact form and a phone number covers 99% of use cases.

The verdict for trades businesses

A trades website needs to do three things: load fast on mobile, rank on Google, and convert visitors into enquiries. Static HTML does all three better than WordPress. It can't do the things WordPress can do that you don't need it to do.

If your current site is slow, you've been hacked before, or you're not ranking where you should be — it's worth understanding whether the platform is part of the problem. Get a free audit and we'll check your current site's speed, security, and ranking performance and give you a straight answer.