A ready-made theme wins at the start, a custom theme wins after a year - and that one sentence sums up the whole choice. You buy an off-the-shelf template once, launch it in a few days and pay the least for it. A custom WordPress theme is code written for your site: it costs more and takes longer to build, but it does not carry hundreds of features you will never use. The decision does not rest on what is “technically better”, but on how many pages you ultimately need, how much your look has to be yours, and whether the site is meant to earn or just exist.
Below I take both options apart: what you get, what you really pay (not just on the day you buy), and how to tell when custom code pays off for you.
What a ready-made theme is and what a custom one is
A WordPress theme is a set of files responsible for the look and layout of the site - the content sits separately, in the database. That is why a theme can be swapped without losing posts and products, though not without work.
- A ready-made theme (template) is a product sold to thousands of people. You buy it on a template marketplace or download it from the free WordPress directory. The classics I see most often on client sites are Salient, Divi, Avada and Astra. You change the look in an options panel and a page builder, without touching code.
- A custom theme is a template written from scratch for one project: only the sections you use, and only the code those sections need. Instead of a panel with a thousand switches you get fields to fill with content.
- A child theme is a layer on top of a ready-made theme where your own changes live so they do not vanish on update. It is a middle option rather than a separate category - and the only correct way to modify an off-the-shelf theme.
A localised theme is usually a foreign theme with a translation loaded on top rather than a separate product - and that is fine, as long as the translation also covers cart and form messages.
Comparison: cost, time, life after launch
| Criterion | Ready-made theme | Custom theme |
|---|---|---|
| Up-front spend | lowest - licence plus the work of filling it in | higher, because you pay for design and code |
| Time to launch | days | weeks |
| Look | recognisable, because thousands of companies use it | yours alone |
| Speed | depends how many features load “just in case” | only what the site actually uses loads |
| Changes a year in | easy within the options, hard outside them | anything, because the code is at your disposal |
| Dependence on the author | high - the theme can be abandoned | none, the code is yours |
| Updates | frequent, sometimes break your own modifications | rare, made deliberately |
The row that matters most is dependence. A ready-made theme is someone else’s product: when the author stops developing it or changes the licensing model, you are left with code nobody patches any more. With a custom theme that problem does not exist.
What it really costs
The licence price is usually the smallest part of the bill. The real cost of an off-the-shelf theme comes in several layers that only reveal themselves along the way.
| Item | Ready-made theme | Custom theme |
|---|---|---|
| Theme licence | one-off or annual, usually in the low hundreds of zloty - vendor pricing changes, check at the source | none |
| Page builder | often required in the Pro version, paid yearly | not needed |
| Extra plugins | slider, forms, builder add-ons - each with its own licence | only the ones doing real work |
| Work filling it in | from a few days up, depending on the number of pages | included in the project |
| Stronger hosting | sometimes necessary when the theme is heavy | standard is usually enough |
| Changes a year in | cheap within the options, expensive outside them | quoted normally, with no workarounds |
With me, sites built on custom code usually fall in the 5,000-10,000 PLN net range (Polish market rates), quoted up front, in writing, before we start. That is not a price per page - it is a quote for a scope we describe together beforehand. If you want to compare the cost of the licences alone on the off-the-shelf side, I broke that down separately in what Elementor Pro costs.
When a ready-made theme is a good decision
A ready-made theme makes sense when the site mainly needs to exist and look tidy, and the budget is limited. Specifically:
- A company calling card - a few pages, contact details, references, no elaborate features
- A first version of an idea that needs testing on the market quickly
- An internal site - for the team, recruitment, an event
- A blog or portfolio, where content matters more than layout
- No materials - without photos, copy and a visual identity, a custom project will stall anyway
In those cases, bespoke code is money spent on capabilities you will not use. Better to take a solid, light theme and put the difference into photos and copy. How to pick the theme itself - what to look for in the description, what to avoid - I covered in how to choose a WordPress theme.
When a custom theme comes out cheaper than a ready-made one
A custom theme starts paying off the moment fighting the limitations of an off-the-shelf one costs more than writing it fresh. Signs that you are at that point:
- You are paying to work around the theme - every other change needs an extra plugin or a snippet of code
- The site is slow despite optimisation - cache, compression and better hosting have all happened and the score is still poor
- A theme update breaks the look - a sign that the modifications live outside the child theme
- You have repeatable layouts - a portfolio, a price list, offers that an editor should add through a form rather than assemble by hand in a builder
- The site earns - it is part of your sales, so load time and how comfortable the form is translate into money
- You have a visual identity an off-the-shelf theme cannot reproduce, and your customers recognise it
For a store that threshold arrives sooner than for a company site, because the product page, cart and checkout come into play. I took that thread apart separately in a WooCommerce theme versus a custom design.
Where the speed difference comes from
The difference does not come from ready-made themes being “badly written”, but from the fact that they have to serve everybody. A theme sold to tens of thousands of companies contains layouts for a restaurant, a law firm and a photo gallery - and the browser downloads a fair share of that baggage even when you use one layout.
Then there are page builders. A builder saves the layout as nested containers, so a simple section with a heading and a button can grow to a dozen levels of code. On a powerful laptop you do not see it; on a phone with a weak signal you see it clearly.
Before you blame the theme, though, check three things: the weight of your images, the number of active plugins and the PHP version on the server. Very often those are what drive the score. If the site still drags after they are sorted, the problem sits in the presentation layer and is worth a separate round of optimising the existing site.
The third route most people take
You do not have to pick an extreme. What usually wins is the middle option: a light base theme plus a custom layer on top. You take a simple block theme and build your own layout templates and content fields above it.
What that gives you:
- the look is fully yours, because the layouts are built around your content
- the editor fills in a form instead of arranging blocks, so the site does not drift out of shape after a month
- there is no panel with a thousand options, so there is none of its weight either
- the cost sits between an off-the-shelf theme and a full build from scratch
I recommend it most often to companies that already have a working site and a list of things that chafe. We do not rebuild everything then - we replace the presentation layer and leave content, addresses and search rankings untouched.
How I approach this myself
I start with a free diagnosis: I check what your site runs on today, whether the theme got an update in the last year, whose name the licences are in, how many plugins exist purely to work around the template’s limits, and how all of that affects speed. I reply concretely - sometimes with the conclusion that tidying up what is there is enough and there is no point rebuilding the look.
If the diagnosis says a custom theme or a bespoke layer on a light base is worth it, you get a written quote before we start: scope, deadline, figure. No hourly billing along the way and no items added mid-project. Standard website projects with me fall in the 5,000-10,000 PLN net range, and if after launch you want peace of mind about updates and backups, ongoing support comes on top - Basic from 1,000 PLN, Pro from 2,000 PLN, Premium from 3,500 PLN net per month, depending on how much happens on the site.
Frequently asked questions
Can a theme be changed without losing content? Yes. Posts, pages, products and orders sit in the database and survive a theme swap. The problem is layouts built in a page builder - they are often saved in code specific to the old theme and have to be recreated afterwards. That is why I always start such an operation with a full backup and a working copy on a separate address.
How long does it take to build a custom WordPress theme? For a typical company site it is measured in weeks, not days. The biggest part of the calendar is usually not the code but preparing content and photos on the client’s side. When the materials are ready before the start, the project moves considerably faster.
Is a free theme enough for a small business? Often yes. Free themes from the official WordPress directory go through review and are sometimes lighter than expensive marketplace templates. The condition is checking when the theme was last updated and whether it has active support - an abandoned free theme is a security risk.
Will a custom theme help my SEO? Indirectly. Lighter code improves load time and comfort on a phone, and those are signals Google takes into account. But nobody can honestly promise you rankings in exchange for a theme swap - visibility is mostly decided by content, addresses and who links to you.
Sitting on this yourself and unsure where to start? I speed up and repair existing sites and stores - Core Web Vitals, outages, the features that are missing. Tell me what is happening and you will get a concrete quote with a date.