NEEDS FIRST, TOOLS SECOND
What is a CMS, and why your business may not need one
A CMS is the software that lets you change your website's text and photos from a dashboard, without touching code. It sounds essential, which is why so many local business websites end up running a WordPress install nobody uses. Here is what a CMS is, the options available, and why, in most cases, an HTML and CSS website with a small custom panel is easier to look after.
What a CMS is, in two sentences
CMS stands for Content Management System. It is software installed on the server (or rented as a service) that stores the website's content and gives you a private dashboard to create and edit it without programming.
WordPress is the best known, but not the only one. The name matters less than the idea: a CMS separates content from design. You type a text or upload a photo into a form, and the system places it on the page with the site's look.
A CMS solves one specific problem: letting someone without technical knowledge publish content often. If that problem does not exist, the CMS is surplus.
How it works under the hood
A classic CMS such as WordPress has four parts:
- A database that stores text, pages, users and settings.
- Templates or themes that define the design and where each piece of content goes.
- The admin dashboard, with its username and password, where you edit.
- Extensions or plugins that add features: forms, languages, backups, SEO, galleries…
Every time someone visits, the server runs the program, queries the database and assembles the page (unless a cache has already stored it). That is why a CMS needs a server running PHP or similar, updates for the software and its extensions, and someone watching who can log in.
A static website works the other way round: pages are already prepared as HTML files and the server simply delivers them. There is no program to run and no database to query on each visit.
The options available today
- Self-hosted WordPress
- Free and open source, installed on your hosting. Very flexible, with thousands of plugins and professionals. In exchange, maintenance and security are your responsibility, or that of whoever you hire.
- Joomla and Drupal
- Also open source. Drupal suits large projects with many content types and permissions; Joomla now has a small share. For a local business site, both are usually more than you need.
- Hosted builders: Wix, Squarespace, Webflow
- You pay a monthly fee and the provider handles the server and updates. Convenient to start with, but the site lives on their platform: if you leave, you usually cannot take the design with you, and the provider sets the price.
- Shopify and other shop platforms
- Built for selling: catalogue, payments, shipping and stock. If your business is an online shop, this is where to look; if you do not sell online, it makes no sense.
- Headless and flat-file CMSs
- Tools such as Strapi, Sanity or Contentful store content and deliver it to a separately built site. Others, such as Kirby or Grav, skip the database and keep everything in files. They are good technical solutions, but still one more piece to configure and maintain.
- No CMS: HTML, CSS and JavaScript
- The site is written directly in code, or with a generator that produces the pages. It is the lightest and safest option, and the one that needs least maintenance. Its weak point is that the owner cannot change anything without help… unless a small panel is built for the few things that really change.
The same goes for sales funnel platforms: ClickFunnels: what it is, what it costs and whether you need it
What people use today: the data
According to W3Techs, which tracks the ten million most visited websites, these were the usage shares across all websites in early November 2026:
- WordPress: 39.5% of all websites, or 58.2% of those using a recognisable CMS.
- No CMS detected: 32.2%.
- Shopify: 5.3%.
- Wix: 4.2%.
- Squarespace: 2.4%.
- Joomla: 1.1%; Webflow: 0.8%; Drupal: 0.7%.
Two takeaways: WordPress dominates the CMS market by a wide margin, and almost one in three websites runs without a recognisable content management system. WordPress is the usual choice, not a requirement.
Source: W3Techs, usage of content management systems (November 2026).
A local business website rarely needs WordPress
Think of a physiotherapist, a garage, a small estate agent, a law office or a renovation company. Their website has five to ten pages: who they are, what they do, some work, reviews, where they are and how to get in touch. How often does that change? In most cases, a few times a year.
For that, installing a full CMS is like buying a van to pick up bread. It works, but it brings costs you never use:
- Constant updates to the core, theme and plugins, which someone has to apply and check.
- More ways in for automated attacks: the login page, vulnerable plugins, the database. I speak from experience: this very website was hacked with casino spam back when it ran WordPress. It had security and anti-spam plugins, I am an IT professional, and cleaning up clients' hacked websites is part of my job. Even so, they got into mine.
- Dependencies that expire: an abandoned plugin, or a licence to renew every year.
- More weight and less speed if it is not well optimised, because the system loads things your page does not need.
An HTML and CSS website, by contrast, is uploaded to the server and simply works. There is no software to update, it is very fast, there is no dashboard to attack, and any copy of the folder is a complete backup. The contact form is handled by a small, secure service, with no CMS behind it.
And for bigger changes, such as a new page or a new service, the person who designed the site usually makes them, just as they would with WordPress when the change affects the design.
WordPress pros and cons compared with HTML
How I found out and fixed it, step by step: My website was hacked: what I did, step by step
The middle ground: a small custom content panel
The obvious objection is: “Fine, but I want to change things without calling anyone.” Fair enough. But you rarely need to change everything; you need to change four specific things. For example:
- Add a completed project with photos and a description.
- Change the opening hours, a phone number or a holiday notice.
- Update prices or rates.
- Publish occasional news, offers or events.
For that, a very small custom panel can be built: a private dashboard with one form for each of those things and nothing else. The owner logs in, fills in “new project”, uploads the photos and saves. The system generates or updates the website's pages, which stay static.
EXAMPLE
A renovation company wants to show every finished job. In its panel it sees just one option: “Projects”. It types the title, the area and a paragraph, uploads the photos and clicks publish. Photos are resized automatically, the project appears on the work page and the home page shows the latest three. No themes, no plugins, no updates.
The advantages over a generic CMS are clear:
- Easier to use: the panel only contains what the business uses, in its own words. No intimidating menus and no way to break the design.
- The public site stays static: just as fast, with a smaller attack surface.
- Less maintenance: one small, known piece instead of an ecosystem of third-party plugins.
It is not magic: the panel needs protected access, backups and someone who has built it properly. And it is development work to plan from the start, knowing which content will be edited. If the list grows a lot and you need several editors, review workflows or daily publishing, then it is time to talk about a full CMS.
When I would choose a CMS
- You publish content every week
- An active blog, a publication or a busy news section justifies a full content management system.
- Several people edit the site
- If there are writers, reviewers and different permissions, a CMS already has that organisation built in.
- You sell online
- A shop with a catalogue, payments and stock needs an e-commerce platform, whether Shopify, WooCommerce or another.
- You already have a working, well-maintained WordPress
- I would not change it just for the sake of it. I would compare the cost of maintaining it with the cost of migrating.
If yours is a presentation website with a few changes a year, my recommendation is the opposite: well-built HTML and CSS and, if you need them, a few editable fields made for you.
Common questions
Does a website without a CMS rank worse on Google?
No. Google does not care how the page was built; it cares about content, structure, speed and being able to crawl it. A well-built static site often starts with a speed advantage.
Can I change the text myself without a CMS?
Small code changes are easy for someone who knows how, but not ideal for a business owner. That is why, if some content will change often, a custom panel is built just for it.
What if I need a CMS later?
It can be added. The design and text of a static site can be moved into a CMS when it is really needed, keeping page addresses with redirects.
Aren't Wix or Squarespace easier?
To start with, yes. In exchange, you pay a fee for as long as the site exists, depend on the provider's terms, and usually cannot move the site elsewhere. Your own HTML website belongs to you and runs on almost any hosting.
A website you can look after without hassle
Before choosing technology, we look at what you will change yourself and how often. If it is little, an HTML and CSS website is the most convenient. If you need to add projects, prices or news on your own, we include a small custom panel in the proposal.
See web design options