For 20 years, "I want a website" automatically meant "I need a CMS". WordPress, Joomla, Drupal. Install a back office, pick a theme, stack up plugins. It was the universal reflex.
That reflex has become a trap. Today, the majority of brochure sites, blogs and landing pages don't need a traditional CMS. And those that use one pay the price: slowness, security holes, constant updates, and a hosting bill that no longer makes sense.
The very site you're reading right now runs without a CMS. No database, no PHP, no admin panel. Static HTML served by a CDN. And it does everything a WordPress site would do: full SEO, blog articles, contact form, analytics. Except it loads in under a second and requires no maintenance.
What this article covers
- The real cost of a CMS (beyond the license)
- The 3-layer method to find out whether you need one
- The concrete alternatives that exist today
- When a CMS is still essential (and which one to choose)
The real cost of a CMS (the one nobody shows you)
WordPress is "free". That's the first thing you're told. The reality is that WordPress is free to install and expensive to maintain.
Typical WordPress site
- PHP + MySQL hosting: 10-30 euros/month
- Premium theme: 50-80 euros/year
- Premium plugins (SEO, cache, security): 100-300 euros/year
- Maintenance, updates, troubleshooting: 2-5h/month
- Total over 3 years: 1,500 - 3,000 euros
Equivalent static site
- Cloudflare/Netlify hosting: 0 euros/month
- Global CDN included: 0 euros
- SSL, DDoS protection: included
- Maintenance: almost none
- Total over 3 years: 0 - 100 euros
And that's not counting the invisible cost: the 500 errors that crash the site on a Saturday night, the WordPress updates that break a plugin, the security flaws that call for an emergency intervention.
From the field
Over the past 12 months, we were called in 8 times for WordPress emergencies: sites hacked through plugins that weren't kept up to date, 500 errors after an automatic update, or load times that had crept up to 8+ seconds. None of these problems exist on a static site.
The 3-layer method: do you need a CMS?
After dozens of web projects, we've developed a simple framework to guide clients. A website breaks down into 3 layers of complexity. Your real need determines the layer, and the layer determines the tool.
1 "Brochure" layer — no CMS
Your site presents your business, your services, a contact form. You publish a blog article once a week or once a month. The content is managed by one or two people.
- Brochure sites, portfolios, landing pages
- Personal or corporate blogs with low posting frequency
- Documentation sites, product pages
Recommended tool: static HTML, Astro, Hugo, or Next.js in static mode.
2 "Dynamic content" layer — headless CMS
Several writers publish regularly. The content has to be editable without touching the code. But the front end doesn't need to be generated by the CMS.
- Team blogs with an editorial calendar
- Sites with multilingual content
- Product catalogs (without a cart)
Recommended tool: Sanity, Contentful or Strapi + a static front end.
3 "Application" layer — traditional or custom CMS
The site has business logic: e-commerce, member areas, personalization, complex workflows. The CMS is no longer a convenience choice, it's a functional need.
- E-commerce with stock management and payment
- Community platforms with user accounts
- Sites with content personalized by profile
Recommended tool: WordPress, Shopify, or a custom application.
The classic trap
Most SMEs are in layer 1 but pay for a layer 3 solution. It's like renting a 40-ton truck to deliver a parcel: it works, but it's absurd.
What a static site can do in 2026
The historical argument against static sites was: "it's too limited". That was true in 2010. It isn't anymore, at all. Here's what this site does without a CMS:
Full SEO
- Automatic XML sitemap
- Meta tags, Open Graph, Twitter Cards
- Schema.org / JSON-LD structured data
- Canonical URLs, robots.txt
Features
- Blog with categorized articles
- Working contact form
- Analytics (Google Tag Manager)
- Responsive, accessible, high-performance
The key difference: on a static site, the HTML is pre-generated. The server has nothing to compute. It sends a file. That's why load times are on the order of 200-400ms versus 2-5 seconds for an unoptimized WordPress.
For visibility with AI engines (ChatGPT, Perplexity), a static site is actually an advantage: the HTML is clean, without the noise generated by WordPress plugins, which makes it easier for AI crawlers to extract the content.
AI makes the "easy to edit" argument obsolete
The main advantage of a CMS was the visual interface. "I want my client to be able to change the text themselves, without touching the code." That was a valid argument. It's disappearing.
With generative AI assistants, editing content becomes conversational. Instead of navigating a WordPress back office, you say: "Change the homepage title to X" and it's done. No graphical admin panel needed for that anymore.
Conversational editing vs a classic CMS
Classic CMS (7 steps)
- Log into the back office
- Navigate to "Pages"
- Find the right page
- Open the editor
- Look for the block to edit
- Edit the text
- Publish
AI editing (1 step)
"Replace the price on the pricing page with 499 euros/month and update the date."
The AI edits the file, generates the HTML, deploys. Total time: 30 seconds.
This isn't science fiction. It's exactly what we do for clients who entrust us with managing their site. And it works for non-technical people too: a WhatsApp chatbot connected to the Git repository lets you update your site by message.
When a CMS is still the right choice
This isn't an anti-CMS article. It's an article against the default CMS. Some cases fully justify a content management system. Here they are:
A multi-user editorial team
5 writers publishing daily with approval workflows (draft, review, publish). A CMS with role management is essential.
E-commerce with stock management
As soon as you sell physical products with an inventory, variants, promotions and a payment system. Shopify or WooCommerce then make sense.
Member area or personalized content
If each visitor sees different content depending on their profile, their purchases, or their subscription. Static content isn't enough.
A complex, evolving data model
When the content structure changes often: new content types, relationships between entities, dynamic taxonomies. A headless CMS like Strapi excels here.
The key question to ask
If your content changes less than once a day and fewer than 3 people edit it, you probably don't need a CMS. It's as simple as that.
Migrating from WordPress to a static site: what you need to know
The migration isn't trivial, but it's simpler than people think. Here are the concrete steps we follow with our clients:
1 Content export
Extraction of pages, articles and media from WordPress. The text is converted to clean HTML or Markdown. Images are optimized and versioned.
2 Front-end rebuild
The design is rebuilt in HTML/CSS (Tailwind CSS in our case). We don't reproduce the WordPress theme: we simplify it. Less code = more performance.
3 SEO and redirects
URLs are preserved or redirected with 301s. The XML sitemap, structured data and meta tags are rebuilt manually. Search rankings are not only preserved, but often improved thanks to Core Web Vitals.
4 Deployment and monitoring
The site is deployed to a CDN (Cloudflare, Netlify). Availability is 99.99%. No more watching a PHP server or patching vulnerabilities.
The full process takes between 3 and 10 days depending on the size of the site. For a typical brochure site of 5-15 pages, it's usually wrapped up in a week.
Frequently asked questions
Can a site without a CMS rank well on Google?
Yes, and often better. Static sites produce cleaner HTML, load faster (a Core Web Vitals factor) and don't have the SEO plugin conflicts typical of WordPress. XML sitemaps, meta tags and structured data are just as easy to implement without a CMS.
How do you edit the content of a site without a CMS?
Several options: editing Markdown files in a Git repository, using a headless CMS like Sanity or Contentful, or using a conversational AI assistant to update content with natural-language commands. The right solution depends on your profile and your needs.
Are static sites more secure than WordPress?
Yes, by design. A static site has no database, no admin panel, no server-side PHP. There is nothing to hack. WordPress is the number-one target of automated attacks: vulnerable plugins, brute force on wp-admin, SQL injections.
How much does migrating from WordPress to a static site cost?
For a brochure site of 5 to 15 pages, expect 3 to 10 days of work. The investment pays for itself within 12 to 18 months thanks to savings on hosting and maintenance. And the site will be faster, more secure and cheaper to operate over the long term.
What if I need a contact form or analytics?
Forms work via third-party services (Formspree, Netlify Forms) or serverless functions. Analytics integrate identically: Google Tag Manager, Plausible or Matomo work on any site, static or dynamic.
Read also
Is your WordPress site slowing you down?
We'll audit your site for free and tell you frankly whether a CMS is justified in your case. No sales pitch: just a technical analysis.
Get in touch for a quick diagnosis of your web stack.
Request a free audit