For the best part of twenty years, the content management system was the default answer to “we need a website”. WordPress, Joomla and their peers made sense for a simple reason: editing raw HTML meant hiring a web designer, and every change (a new page, a price update, a fresh photo) meant going back to them and paying for it. A CMS put the keys in the business owner’s hands.
That reason has largely gone. SPAWN.LONDON founder Paul Emerton argues that for the majority of business websites, whether brochure sites, service businesses, local trades or professional practices, a hand-built static HTML and JavaScript website is now faster, safer, better at search and AI visibility, and just as quick to change. This isn’t a WordPress witch hunt. It’s a question of fit.
Lightning-fast static sites
Pages are built once and served instantly. Nothing is assembled on request.
No database required
No queries, no MySQL server, no database to hack, corrupt or back up.
Reduced security risk
No admin login, no plugins to patch, a far smaller attack surface.
What actually happens when someone visits your page
When a visitor opens a page on a typical WordPress site, the server starts PHP, loads the WordPress core, initialises the theme, wakes up every active plugin, runs a series of database queries to fetch the content, settings and menus, and only then assembles the HTML. The browser then downloads the theme’s stylesheets and scripts, plus whatever CSS and JavaScript each plugin decided to add, often on every page, whether it’s needed there or not.
A static site skips all of that. The page already exists as a finished file. The server’s only job is to send it.
Caching is the usual answer, and it does help: a good page cache stores a pre-built copy of the HTML so the database isn’t hammered on every visit. But a cache doesn’t make the page any lighter. The theme and plugin payload still travels to the browser, caches still miss and expire, and the caching layer itself becomes one more plugin to configure and maintain.
Caching hides the work. A static site removes it. A straight HTML page is smaller, so your website is simply faster.
Speed is a search signal
Google measures real-world page experience through its Core Web Vitals: how quickly the main content loads, how quickly the page responds to a tap or click, and how stable the layout is while it loads. These form part of Google’s page experience signals. Content and relevance still decide most rankings, but a slow site carries a technical handicap that a lean static site simply doesn’t have.
Speed also changes behaviour. Visitors on mobile data abandon slow pages, and every second spent waiting is a second in which a competitor’s result is one tap away. Lightweight pages are also cheaper and quicker for search engines to crawl, which helps new and updated content get picked up sooner.
Why static sites read better to AI answer engines
Search is no longer just ten blue links. Google’s AI Overviews, ChatGPT, Claude, Perplexity and Copilot increasingly answer questions directly and cite the pages they drew from. Being one of those cited sources, which SPAWN.LONDON calls AIO (AI optimisation), depends on the AI being able to fetch, read and trust your page.
Many AI crawlers fetch a page’s raw HTML and do not run its JavaScript. If your content is injected by scripts, buried under page-builder markup, or only appears after a plugin loads, there is a real chance the crawler sees far less than your visitors do. A well-built static page puts the content directly in the HTML, uses clean semantic headings, and carries structured data (JSON-LD) describing exactly who you are and what you offer. Every SPAWN.LONDON static site is built that way as standard.
“But isn’t WordPress easier to update?”
This is the worry that keeps businesses on a CMS long after it has stopped serving them. In the old days it was fair: a designer typed the HTML by hand, invented the JavaScript, worked from a handful of templates, and any change meant a quote, a wait and an invoice.
That model is gone. SPAWN.LONDON keeps every client’s website code on file and works with an AI-accelerated development workflow. Send over the new content, the new page or the change you need, and it is built, checked and published. That is as fast as, and frequently faster than, logging into a CMS and wrestling with a page builder yourself.
And that wrestling is the hidden cost of a CMS. Page builders turn business owners into part-time graphic designers, nudging blocks, fighting spacing, and discovering after publishing that the layout fell apart on a phone. As Emerton puts it, what a business actually wants is a functioning website, not a new career in layout. You supply the content. The site looks right, reads right, and works.
Built for the phone first
Most visits to a typical business website now come from a mobile device. With a static site there is no theme update or plugin conflict waiting to quietly break the mobile layout. Every page is designed and tested for small screens before it goes live, so when a customer flips to their phone, the site works every time.
People want information, faster
Expectations have shifted. Visitors want the opening hours, the price, the phone number, the answer, and they want it now. They don’t want to sit through a fancy loading animation whose real job is to disguise the fact that the CMS behind it is still pulling in dozens of files. The SPAWN.LONDON approach is simple: keep it simple, keep it straight, make it faster.
Fewer moving parts, fewer ways in
Every plugin is somebody else’s code running on your server. Security researchers consistently find that the large majority of reported WordPress vulnerabilities sit in third-party plugins and themes rather than in WordPress core, and an outdated PHP version or an abandoned plugin is exactly what automated attacks look for.
A static site has no database to inject into, no admin login to brute-force and no plugins to fall behind on. No website is risk-free, as hosting and forms still need to be configured properly, but the attack surface shrinks dramatically, and so does the monthly maintenance burden.
When WordPress is still the right choice
Fairness matters here. A CMS still earns its place when a site genuinely needs a dynamic backend: large editorial teams publishing several times a day with approval workflows, membership and subscription sites, complex e-commerce with live stock and customer accounts, or deep integrations that depend on a particular plugin ecosystem. For those, the right answer may be a well-maintained CMS or a bespoke application.
But most small and medium business websites don’t need any of that. They need to load instantly, look professional, show up in search and AI answers, convert visitors into enquiries, and change when the business changes. That is exactly what a static site does best.