The template trap

Most website builders work the same way. You pick a template, you swap in your logo, you change some colors, and you call it done. It is fast. It is cheap. And your site ends up looking like every other site built with that template, including your competitors’.

The aesthetic problem is real — looking like everyone else is bad for a business that wants to be remembered — but it is the smaller problem. The bigger problem is that templates carry baggage, and you pay for that baggage on every single page load.

Bloated code. A WordPress template often ships with thirty or forty plugins, each loading its own CSS and JavaScript. Your homepage can easily pull three megabytes of code it does not need, to display text and a few images.

Performance penalties. Template builders prioritize flexibility over speed. They have to work for every possible buyer and every possible use case, so they load everything for every visitor. The cost of that flexibility is paid in milliseconds, on every device, forever.

SEO limitations. Many templates generate messy HTML — deeply nested divs, inline styles, missing semantic tags, duplicate content blocks. Search engines can still read it, but they read it less confidently, and you lose points you did not have to lose.

Lock-in. When your site is built inside a page builder, your content lives in that builder’s proprietary format. Move hosts, change developers, or try to leave the platform, and you often find there is nothing portable to take with you.

What “from scratch” actually means

When we build a site, we start with a blank file. We write the HTML structure first — semantic, clean, accessible. Then we add the CSS, only what the page needs, no framework shipping a thousand utility classes you never use. Then, if a specific component genuinely needs interactivity, we add a small, targeted piece of JavaScript.

This approach means four things.

The code is exactly what your site needs and nothing it does not. There is no generic “works for anyone” code running on your pages. Every line earns its place.

Performance is built in from the first commit, not bolted on at the end. There is nothing to strip out, because we never added it.

Every page is structured for search from the first line. Proper heading hierarchy, descriptive metadata, structured data, clean URLs. The SEO fundamentals are free when you write the HTML yourself.

The design is unique to your brand. Nobody else’s site looks like yours, because nobody else’s site is built from your files.

A code editor showing clean hand-written HTML and CSS next to a bloated template's file tree

It is faster than you think

“From scratch” sounds slow. It is usually faster than customizing a template.

Here is why. When you start with a template, you spend the first several hours undoing decisions the template author made for hypothetical buyers. You fight the framework. You override styles with !important because the template’s CSS is more specific than yours. You hack around limitations the builder imposed. You discover, three days in, that the template cannot do the thing you assumed it could, and you start over.

Starting from scratch means every decision is intentional. We build the structure you need and nothing you do not. There is no fighting, because there is no framework to fight. An Astro site with five pages typically takes us one to two weeks, end to end. That is faster than most template-customization projects we have seen, and the result is dramatically better.

The reason is simple. With a template, the work expands to fill the time you spend wrestling with it. With a from-scratch build, the work is bounded by what the site actually requires, and that is usually less than people expect.

What you get when we hand it over

When the project ends and we hand over your site, here is what is in the folder.

The contrast is a WordPress site with Elementor, fifteen plugins, a monthly hosting fee, an annual theme renewal, and a security patch that needs applying every few months. It looks cheaper on day one. Add it up over three years — the subscriptions, the maintenance, the lost leads from slow load times — and it is not cheaper. It is more expensive and worse.

Why this approach is rare

Honest question: if building from scratch is better and often faster, why do most agencies and freelancers use templates and page builders?

Because templates scale the agency, not the result. A page-builder shop can produce fifty sites a month with a small team, because each site is mostly configuration rather than craft. The economics work for the shop. They do not work for the client, who gets a slower, more generic, more fragile site.

Building from scratch does not scale the same way. It scales with skill and repetition and a good component library you have refined over dozens of projects. It produces better sites for the client. It just does not produce as many of them per developer-hour, which is why most of the industry does not do it.

We chose the trade that favors the client. We would rather build fewer sites that we are proud of than many sites we are not.

The takeaway

A from-scratch site costs a little more thought and a little more skill upfront. It pays you back for the entire life of the site in speed, in search performance, in not breaking, and in not looking like your competitors. You own something good, and you own it outright.

The alternative is renting a template from a platform that can change the terms on you next year, on a codebase you cannot read, that loads three megabytes of code to show a paragraph. We have seen the back end of enough of those projects to know how they end. We would rather you own something good.

Want a site built for your business, not assembled from a template? See our pricing or tell us what you need.