Why hand-built sites win

A website is a folder of files

Strip away the systems, and a website is a folder of files on a server. A visitor asks for a page, the server sends the file. That is the whole thing. Every CMS adds machinery on top: a database to hold the content, a theme engine to turn it into HTML, plugins to add features, and a login to manage it all. The machinery has to run on every visit, has to be patched, and has to be hosted on something that can carry it.

For a newspaper with a thousand articles a month, that machinery earns its keep. For a plumber, a law firm, a workshop or a clinic, it mostly sits there costing speed and attention.

Speed is built in, not bolted on

A plain page is fast because there is nothing to do. No query, no template rendering, no plugin scripts queued before the content shows. A typical hand-built page is a few kilobytes of HTML and one stylesheet. The home page of a demo site in cmsspot is under two kilobytes of HTML. Search engines reward that, and visitors on a phone with a weak signal notice it.

CMS sites get fast with caching layers and tuning. A hand-built site starts fast and stays fast without anyone looking after it. More on speed.

Security by having less

Every login form on a domain is a door. Every plugin is code someone else wrote, running on your server, waiting for its next security notice. A hand-built site has no login form on the domain and no plugins. What remains to protect is the web host and your own code, which is a small surface you can actually see.

cmsspot keeps it that way. It does not install anything on the site. It connects over SFTP, reads the files as data, and writes back only the fields that changed. There is nothing of cmsspot running when a visitor loads a page. More on security.

Nothing to update, ever

A file written in 2016 still works in 2026. A CMS site from 2016 that was never updated is a liability. The difference matters for small businesses, because they rarely have anyone whose job it is to keep a system current. A hand-built site asks nothing of them.

The code is yours and readable

Open a hand-built page in any editor and you can see what it does. Hand it to another developer and they can work on it the same afternoon. Nothing is locked inside a theme format, a builder, or a database export. If cmsspot disappeared tomorrow, the site would not notice.

It reads well for search engines and AI

Clean, semantic HTML with a heading, paragraphs and a few links is the easiest thing in the world for Google to index and for an AI assistant to quote. Generated markup from builders buries the content in nesting and scripts. A hand-built page puts it in plain sight. More on AI and SEO.

The missing piece was editing

The honest reason small sites end up on a CMS is that the owner wants to fix a typo or change a price without emailing the developer. That used to mean choosing a CMS and accepting the weight. cmsspot removes the trade-off. The developer builds the site the simple way, the owner edits it in the browser, and the files on the server stay as clean as the day they were written.

When a CMS is still the right choice

If the site needs a shop with carts and payments, user accounts, comments, or hundreds of posts from several authors, use a system built for that. cmsspot is for the far larger number of sites that need none of it.

See the detailed comparisons: WordPress · Squarespace · Wix · Drupal