Templates are fast and cheap. For a weekend project or a throwaway landing page, they make sense. For a business that wants its website to actually do something — rank on Google, convert visitors, represent the brand accurately — a template is almost always the wrong starting point.
This is why every client site I build at tonibarisic.com starts from an empty file.
The template trap
A typical WordPress or Wix template ships with code for features you will never use: sliders, mega-menus, testimonial carousels, portfolio filters, shop widgets, appointment bookers. Every one of those features loads JavaScript and CSS on every page visit, whether you use it or not.
The result is a homepage that weighs two to five megabytes before a single image loads. On a mid-range phone over 4G that is a four-to-seven-second wait. More than half of visitors leave before a page that slow finishes rendering. You paid for a website, and you are losing customers on the homepage.
Template authors cannot optimize for your specific use case because they do not know what it is. So they build for everyone, which means they build for no one in particular.
What "custom" actually means
Custom does not mean "bespoke for the sake of bespoke." It means the code that ships to the browser contains only what your project needs. If the site is a five-page brochure, it loads a brochure. If it is a store with filtering and checkout, it loads exactly that. Nothing more.
In practice, a custom build looks like this:
- Stack chosen for the job. A brochure site might use plain React + Vite. A content-heavy site with SEO requirements uses Next.js. An e-commerce store uses Next.js with Supabase or Shopify depending on catalog size.
- Design driven by content. I do not start from a theme. I start from your copy, your products, and your goals, then design the layout around them in Figma.
- Performance budget from day one. Every page has a target weight and loading budget. Images are converted to AVIF and WebP. Fonts are subset and preloaded. JavaScript is split so each page downloads only what it needs.
- SEO structure baked in. Headings, schema markup, canonical tags, sitemaps, and Core Web Vitals are part of the build, not an afterthought.
Brand consistency
The other half of the template problem is visual. A template forces your content into someone else's structure. You end up rewriting product descriptions to fit a card that holds exactly 42 characters, or cropping a photo that was never shot in that aspect ratio. Your brand bends to the theme.
With a custom site the structure bends to the brand. Every section exists because it serves a specific purpose for your business. Spacing, typography, and motion are picked to match how you want customers to feel when they arrive.
Clients consistently tell me the same thing after launch: their new site feels like their business, not like a dressed-up theme. That difference matters when a visitor is deciding in the first three seconds whether to trust you.
When a template is fine
To be fair: not every site needs a custom build. Personal blogs, one-off event pages, internal tools, and proof-of-concept ideas can ship on a template in a day and get the job done. I have used templates myself for exactly those reasons.
The line I draw is this: if the site has to earn money or represent the business to new customers, it should be custom. Everything else is negotiable.
The real cost comparison
A custom site costs more upfront than a template. That is the honest trade-off. But templates carry hidden ongoing costs that rarely get discussed:
- Monthly platform fees (Wix, Squarespace, Shopify Plus)
- Plugin license renewals on WordPress
- Performance penalties that suppress search rankings
- Conversion loss from slow or awkward interfaces
- Rebuilds every two to three years when the theme is abandoned
Across a three-year horizon, a well-built custom site is usually cheaper than a templated one — and it outperforms the template on every metric that matters. I wrote more about this in How Much Does a Custom Website Cost.
Work with me
If you are considering a new website and weighing custom against a template, I am happy to give you an honest answer about which is right for your project. Some of my recent builds live at the portfolio index, including FEIT, Razmjer, and White Sail Split.
Get in touch via info@tonibarisic.com or the contact form on tonibarisic.com.