The end of heavy templates. Does a small business website really need WordPress?

When you order a website for a small business, you often hear that “everyone builds on WordPress,” because it’s convenient and anyone can change things later. For some businesses that’s true. For most small businesses, freelancers and personal brands, though, setting up a complex system to run a site that changes a few times a year is like buying a truck to deliver one briefcase of documents. It’ll get there, but fuel, inspections and repairs cost more than the whole trip is worth. In this article I compare both approaches honestly, including the situations where WordPress is the better choice.

What a small business website really needs

Before you choose a technology, it’s worth writing down what the site is for. For most of my clients the list looks similar: a clearly described offer, proof that you know what you’re doing, meaning past work and reviews, an easy way to get in touch, fast loading on a phone and good visibility on Google. The content changes rarely, usually when prices are updated or a new project is added.

That list doesn’t include a store with hundreds of products, a customer portal or an editorial team publishing several articles a day. Yet those are exactly the jobs large content management systems were built for. If you don’t need them, you’re paying for capabilities you don’t use and for the risks that come with them.

WordPress or pure HTML: an honest comparison

Both approaches have their place. They differ mainly in what happens after the site goes live:

• • Speed: a pure HTML site is a set of ready-made files sent straight to the browser. WordPress assembles each page from the database, theme and plugins on every visit, which takes extra server work and often extra tools to speed it up.
• • Security: according to a Patchstack report, 7,966 new security vulnerabilities were found in the WordPress ecosystem in 2024, and 96% of them were in plugins. A static site has no login panel, database or plugins, so most typical attacks have nothing to grab on to.
• • Maintenance: WordPress, the theme and plugins need regular updates, and one outdated plugin can break the site or open a door for attackers. An HTML file, once uploaded, works the same years later.
• • Editing it yourself: this is where WordPress wins. You change text yourself from a dashboard, without knowing any code. With an HTML site, small changes are usually made by the designer, either as part of a maintenance plan or one-off.
• • Cost over time: a static site avoids most upkeep costs, such as paid plugins, updates and repairs after something breaks. Hosting for a site like this can even be free.

When WordPress makes more sense

It would be dishonest to pretend one tool fits everything. A content management system like WordPress is worth choosing if you plan to publish a lot of content regularly and want to do it yourself, if you run an online store, need customer accounts or have several people with different permissions working on the site.

In that case, go for a lightweight theme and a minimal number of proven plugins, and treat updates like a car service rather than an annoying chore. If none of these situations applies to you, a fast HTML site will probably pay off better.

Speed that both customers and Google notice

Site speed isn’t just about convenience. Google measures real users’ experience with its Core Web Vitals and considers a page fast when its main content appears within 2.5 seconds, it responds to clicks within 200 milliseconds and the layout doesn’t jump around while loading. These values are a good benchmark for you too, because behind every second of waiting is someone who might just go back to the search results and click a competitor.

You can check your current site in a few minutes with Google’s free PageSpeed Insights tool. Paste in the address and look at the mobile score, since that’s where most visitors come from. The design itself affects speed as well: pages overloaded with graphics load more slowly, which I touch on in my article about the cost of visual noise.

Peace of mind for years instead of constant patching

The biggest problem with complex sites doesn’t show up on launch day, but a year or two later. A plugin stops being maintained, the theme doesn’t work with the new version of the system and the contact form quietly stops sending messages, which you only discover after a week of silence in your inbox.

A site hand-written in clean code doesn’t have those weak points. A contact form or a portfolio gallery can be built without heavy plugins, and the site itself can run for years without any updates. The site you’re reading this on is built exactly that way. It also helps when its look matches the rest of your business’s materials, because the website is often a customer’s first touchpoint, as I explain in my article on brand image management.

Already have a WordPress site?

You don’t have to throw it away right away. If it’s fast, kept up to date and does its job, changing technology for its own sake makes no sense. It’s worth considering when the site is slow on phones, something keeps breaking or you pay more to maintain it than it brings in.

When moving, one thing matters most: keeping your page addresses, or setting up redirects from the old addresses to the new ones. Google already knows your old links, and if they suddenly stop working, you’ll lose some of the visibility you’ve spent years earning. A well-planned move shouldn’t lower that visibility, and a faster site usually improves it over time.

Let’s build something logical

A small business website doesn’t need to be complicated to sell well. It needs to be fast, clear and trouble-free. Designing and coding a pure HTML site costs 2,000 to 10,000 PLN with me, depending on the number of pages and features, and the whole thing usually takes 5–8 weeks. You’ll find the details on my services page. If you want to check whether this approach fits your business, write to me and I’ll tell you honestly whether HTML or a CMS will serve you better.