Custom Website vs Template: When Is Custom Worth It?

Every company planning a new website hits the same question sooner or later: use a template (a WordPress theme, Wix, Squarespace, a Shopify theme), or have the site built from scratch?

Most articles on this stop at price. Price matters, but it doesn't tell you what you're actually getting. Here we go through what really differs between the two, when a template is honestly the better choice, and how to judge a developer and their portfolio.

Our example is Lõke, a demo site we built. It's a concept restaurant site made as a sales demo. There is no real restaurant or client behind it, but everything on the page works and you can try it yourself.

What "template" and "custom" actually mean

A template is a ready-made design and structure. You swap in your text, photos and colours. The logic, speed and capabilities are mostly decided for you, and extra features come from plugins or apps.

A custom website is written for your business. Design, motion, forms and integrations are built for the one job the site has to do. Nothing is included "just in case".

Neither is better by default. The real question is how different your site needs to be, and whether that difference pays for itself.

Speed and Core Web Vitals

Google measures page experience with three Core Web Vitals. According to Google's guidance, a good result is:

• LCP (largest content element loaded) within 2.5 seconds;
• INP (response to a click or tap) of 200 milliseconds or less;
• CLS (layout shifting while loading) of 0.1 or less.

These are measured at the 75th percentile, so the site has to be fast for visitors on slower phones, not just on the developer's laptop.

With templates, the design itself is rarely what makes a site slow. What slows it down is what piles up over time: plugins, page builders, extra scripts, unoptimised images. Each looks harmless. Together they add up.

On a custom site, everything in the code is there on purpose. Lõke is built with Vite, GSAP, Lenis, OGL (WebGL) and plain JavaScript, with no large framework. Despite all the motion, Lighthouse scores it 98 to 100 in all four categories. Heavy parts load only when needed: the menu's WebGL effect only runs when a visitor moves onto a dish.

One caveat: speed doesn't replace content. Google's own page experience documentation says Search always tries to show the most relevant content, even if the page experience is sub-par. Speed is part of the whole, not a magic fix.

SEO: what you actually control

For search engines, the gap between template and custom is smaller than people think. You can build a findable site either way. The difference is in details that are hard or impossible to change in a template:

• real HTML text, not headings baked into images or content hidden behind JavaScript;
• a clean heading structure and a unique title and description on every page;
• structured data (for a restaurant: Restaurant schema and opening hours);
• multiple languages with correct hreflang tags;
• lean code that crawlers get through quickly.

On Lõke, everything that matters for search (address, opening hours, the menu) is plain HTML text, even with a lot of motion around it. Even on the illustrated map, the street names and the restaurant marker are text laid over the image, not part of it.

Booking and contact flows that convert

A website isn't a magazine. Usually it has one job: get the visitor to book a table, request a quote, buy, or call.

In a template, that step is usually a third-party widget or a generic contact form. It works, but it rarely fits your process.

Lõke's booking flow shows what custom allows here:

1. party size (1 to 8 guests);
2. a custom calendar that only shows days the restaurant is open (Tuesday to Saturday, 90 days ahead);
3. available times in 30-minute slots;
4. contact details with clear inline error messages;
5. a summary where you can jump back to any answer;
6. an .ics file at the end, so the booking goes into the guest's own calendar in one click.

Every step works with a keyboard, and focus moves to the right place. In the demo there's no system behind the booking; in a real project we'd connect it to the restaurant's booking or POS system.

The same logic applies to commerce. AMPSU is a live platform where the shop, local payments and delivery, and paid recipes form one journey. Products and orders run on Medusa, payments through Montonio, delivery through Omniva, and recipes and subscriptions through Directus and Stripe. No off-the-shelf theme gives you that combination.

Ownership and maintenance

Before deciding, ask: who owns the site, and what happens in three years?

• On a platform like Wix or Squarespace, you're renting. Cancel the subscription and you can't take the design or code with you.
• With a WordPress theme, the code is yours, but the theme, plugins and WordPress itself need regular updates, and any update can break something.
• With a custom site, the code should belong to you. Put it in the contract, along with access to the repository, domain and hosting.

A custom site isn't maintenance-free either. It still needs occasional updates. The difference is fewer dependencies, and you know exactly what's inside.

When a template is honestly the better choice

We don't recommend custom for every business. A template makes more sense when:

• you need a site quickly and the budget is small;
• the site is essentially a business card: who you are, what you offer, how to get in touch;
• you want to edit content yourself daily without a developer;
• your business model is still settling and the site will change in six months anyway;
• a standard shop with standard payments and shipping covers what you need.

A well-configured template beats a badly built custom site.

When custom pays off

Custom is worth it when the difference makes money or saves it:

• The first impression is part of the product. Restaurants, hotels, property developments, design brands. When visitors decide on feeling, the site does the selling. On Lõke, scrolling walks you through an oak pocket door straight into the dining room, up to the grill. That's the moment people remember; the rest of the page stays deliberately calm. Visitors who have reduced motion turned on see still images instead.
• The site has to connect to your systems. Bookings, stock, CRM, accounting, payment and delivery providers.
• The flow is your own. Multi-step booking, a price calculator, orders, gated content.
• Speed is tied directly to sales. For example, a shop where much of the traffic comes from phones.
• The plugin pile is already a problem. The current site is slow, fragile, and nobody dares touch it.

What drives the cost of a website

We don't publish prices, because every project is different. But the cost drivers are always the same:

• number of pages and languages;
• how much custom design and motion there is;
• forms, bookings, calculators and other logic;
• integrations with other systems;
• whether content (copy, photos, video) exists or has to be created;
• content management: whether and how much you'll edit yourself;
• maintenance and further development after launch.

When two quotes differ several times over, it's usually because they cover different work. Compare what's included, not just the total.

What a good brief contains

A good brief saves everyone time and gets you quotes you can actually compare. It doesn't need to be long. Answer these:

• Goal: what should a visitor do on the site? One main action.
• Audience: who visits, and on what device?
• Content: what exists (copy, photos, logo) and what's missing?
• Pages and languages: rough structure and number of languages.
• Features: forms, bookings, shop, member area.
• Integrations: which systems are already in use?
• Content management: who edits the site, and how often?
• References: 2–3 sites you like, and why.
• Timeline and budget range.
• Ownership: who keeps the code, domain and hosting?

How to judge a developer's portfolio

Screenshots are the easy part. Opening the work yourself tells you much more:

• Open it on your phone. Is it fast, and does everything work on a small screen?
• Run Lighthouse or PageSpeed Insights. It takes a minute.
• Try the main action. Fill in the form, complete a booking, add something to the cart. Where do you get stuck?
• Use the keyboard. Can you get through everything with Tab?
• Check that the work is real. Is the site live, and is the developer honest about what's a client project and what's a demo?
• Ask what they actually did. Design, code, content, integrations? Can you talk to them directly?

You can run the same checks on us. In our work, every web development clip is a scroll-through of a live site you can open yourself.

The short version

A template fits when you need a simple site fast. Custom fits when the site is part of how you sell: it has to be memorable, fast, and carry the visitor all the way to a booking, an enquiry or a purchase.

If you're planning a new website or rebuilding an old one, in Tallinn or anywhere else, get in touch. We'll look at what your site needs to do and tell you honestly whether a template would do the job.