A template gets you online quickly with a proven structure, but you accept someone else’s layout, code and limits. A custom build fits your content and goals closely, but it takes more planning and needs ongoing care. Neither is automatically better. The right choice depends on how much your website has to do beyond showing basic information.
What a template really is
A template (or theme) is a pre-built design and code base that you fill with your own content. Good ones are well tested and cheap to adopt. The trade-off is that the design was made for a generic business, not yours. Queensland’s business.qld.gov.au guide to building and managing your website notes of template-based builders that “other businesses may have a similar website to yours”, and that moving content to another platform later may be difficult.
What custom means (and does not mean)
“Custom” covers a range. It might be a fully bespoke design and build, or a customised theme with new sections and templates built for your content. The point is that structure follows your needs: your products, your enquiry path, your story. It does not guarantee better results by itself. A custom site with unclear messaging will convert no better than a tidy template.
Comparing the two
| Factor | Template | Custom |
|---|---|---|
| Design fit | Generic, adjustable within limits | Built around your brand and content |
| Setup effort | Low | Higher, needs a brief and decisions |
| Performance | Varies; many themes carry unused code | Can be lean, but depends on build quality |
| Flexibility | Limited by the theme and plugins | High |
| Ongoing upkeep | Theme and plugin updates | Code maintenance, usually with a developer |
| Distinctiveness | Others may look alike | Can be unmistakably yours |
Performance and accessibility are not guaranteed by either route
Whichever you choose, ask how it performs. Google’s Core Web Vitals set “good” thresholds of 2.5 seconds or less for Largest Contentful Paint, 200 milliseconds or less for Interaction to Next Paint, and 0.1 or less for Cumulative Layout Shift, measured at the 75th percentile of page loads for mobile and desktop. A template can pass or fail; so can a custom build. Test the demo of any template on a phone before committing, and see our business guide to Core Web Vitals.
Accessibility works the same way. The W3C describes WCAG 2 as the international standard, with WCAG 2.2 organised under four principles (perceivable, operable, understandable, robust) and success criteria at levels A, AA and AAA. Template vendors may claim accessibility, but you are the one publishing the content, so check the result against the criteria yourself or have it audited.
A decision framework
Ask these in order:
- Is the website mostly a brochure? If you need a handful of pages with contact details, a template is often enough.
- Does it need custom behaviour? Calculators, configurators, booking logic or integrations push toward custom work. See what makes a business website convert for how structure affects enquiries.
- Is brand distinctiveness part of your value? Premium or creative businesses often need a look that a shared theme cannot give.
- Who will maintain it? A template you can update yourself costs less to run. Custom code needs a named person or provider.
- What is the cost of getting it wrong? If the site is central to revenue, spend on fit. If it is a placeholder, do not.
A middle path
Many businesses start with a template, learn what their customers need, then commission a custom design. If you plan to do that, keep your content portable, own your domain, and avoid features that lock you to one platform. The Queensland guide advises registering your domain through a different party from your builder or host so you own it entirely.
For a comparison of publishing technologies, see Astro vs WordPress.
Where Radiance Impact fits
Radiance Impact’s Technology division builds business websites and redesigns, landing pages, workflow automation and ongoing care. If you are weighing a template against a custom build, see /technology or talk to us through /contact.
Sources
- Build and manage your website, Queensland Government business.qld.gov.au
- Web Vitals, web.dev (Google)
- WCAG 2 Overview, W3C Web Accessibility Initiative
