A template can put you online this week, but the things that make it fast to launch, generic structure, heavy code and stacks of plugins, are what slow it down and cost you sales for years. This is a decision about how the site is built, and it applies on Shopify, WooCommerce, WordPress or a coded framework alike; choosing the platform itself is a separate question.
Does a template really slow your site down?
Usually, yes, and the reason is structural. A commercial theme is built to suit thousands of different stores, so it ships code for sliders, layouts, animations and integrations most sites never use, and every plugin or app added afterwards brings its own scripts and styles. Visitors download all of it before the page becomes usable. A custom build, whether it's a bespoke Shopify theme or a fully coded Next.js site, includes only what your pages need, which is why near-instant loads are the default rather than an optimization project. This is a different question from which platform to use: you can run a bloated template or a lean custom theme on Shopify, WooCommerce or WordPress alike. The platform sets the rules; the build method decides how much weight you carry.
How does a custom build improve conversion?
By shaping every page around your actual buyer rather than a theme's demo store. A template decides your structure before you've thought about your customers: where the hero goes, how products are grouped, what the product page emphasises. A custom build starts from the buying journey instead, from what visitors need to see first, which objections stop them and what proof gets them to the button, and designs the pages to answer those in order. For a skincare brand that might mean ingredients and results above the fold; for a scooter dealer, specs, financing and local pickup. It also lets the brand identity carry through properly, so the store looks like the brand rather than a template wearing its colors. Conversion comes from that fit between page and buyer, which is hard to retrofit into a structure designed for someone else.
Is custom code cheaper in the long run?
Often, yes, once you count the years after launch. Clean custom code has fewer moving parts: no theme updates that break your customizations, no plugin conflicts after a security patch, no paying for features you've hidden. That keeps maintenance predictable and makes new features faster to add, because developers work with code they understand rather than around someone else's. Search benefits accumulate too, since fast, well-structured pages are easier to crawl and tend to hold their performance instead of degrading plugin by plugin. The upfront price is higher, so the comparison only works over a realistic horizon of three years or more, including hosting, licenses, maintenance and the cost of an eventual rebuild. Our website cost guide breaks those numbers down; the short version is that the gap between custom and template doesn't shrink after launch, it usually grows.
What does "custom" actually mean?
The word gets abused, so let's define it. A custom website is designed and coded from scratch for your brand: the structure follows your buying journey, the design follows your identity, and the code contains only what your site needs. What it is NOT: a purchased theme with your colors swapped in, a page-builder layout assembled from blocks, or a template "heavily customized" by hiding sections you don't use — in all three cases you still carry the full weight of code built for everyone. A quick test when a provider says "custom": ask whether they're starting from a theme, and ask who owns the final code. If the answer involves a theme license, it's customization, not custom, and you should pay accordingly.
How do you tell if your template is the problem?
Run three checks before deciding to rebuild. First, test a product or service page in PageSpeed Insights on mobile and look at how much JavaScript and CSS is never used; on a heavy theme it's often most of it. Second, list every plugin or app and what it does, then mark the ones that exist only to patch the theme, such as speed boosters, page builders or style fixes. Third, ask what your team avoids changing because something might break. If most of the weight is unused code, a third of the plugins are workarounds and simple edits feel risky, the template is now the bottleneck, and optimizing it further means adding weight to fix weight. If the scores are fine and the plugin list is short, keep the template and spend the budget on content and conversion instead. What slow pages cost in lost visitors is covered, with the research, in our e-commerce guide and our Core Web Vitals explainer.
When is a template the right call?
Sometimes a template is the correct choice. If you're validating an idea and need any presence this week, a template does that. If the budget is genuinely a few hundred dollars, a well-chosen template beats a badly built "custom" site at the same price. And if the site is temporary, an event, a short campaign, don't over-invest. The template becomes a mistake at the moment your website turns into your main sales channel: when you're paying for traffic, competing on search, or building a brand people should remember. At that point the template's invisible taxes, slower pages, generic feel, plugin maintenance, cost more every month than the custom build you postponed. Validate on a template if you must; scale on real foundations.
Thinking about a new site or a rebuild? We build fast, custom-coded sites on the platform that fits. Tell us about your project.