Updated 31 August 2026 · Turing Websites
WordPress or a custom website?
A practical WordPress versus custom-build comparison for 2026, covering editing, dependencies, performance, lead capture, ownership and cost.
Choose WordPress when its publishing workflow, editor and ecosystem fit the people operating the site. Put a custom build in the comparison when the brief calls for a specific customer journey, component set or integration model. Test the proposed implementation in either case to establish speed, maintenance work and support for the commercial brief.
If you are also weighing hosted builders such as Wix and Squarespace, use the wider custom versus website-builder comparison.
What each route is
A WordPress proposal may combine a theme or page builder with plugins for forms, SEO, caching, security and backups, on selected hosting. Ask the supplier to list every dependency, licence, update responsibility and account owner.
A custom proposal defines the components and services for the agreed brief. Ask how pages are edited, which external packages and services are used, how updates are handled, and what is included in the handover. Our custom builds include a codebase and accounts in your name.
When WordPress fits the brief
- Publishing workflow. Check the editor with the people who will create, review and update content.
- A suitable theme or component system. Test it with representative pages rather than a demonstration page.
- A required WordPress integration. Confirm compatibility, data access and ongoing licence terms.
- Available WordPress ownership. Name the person or supplier responsible for hosting, backups, dependency updates and support.
When a custom build belongs in the comparison
- A defined customer journey. Forms, booking steps or other interactions can be scoped and accepted against the brief.
- A specific performance budget. Agree the target, representative test pages and test conditions before the build.
- A smaller selected dependency set. Review the selected packages and services, including who maintains each one.
- Explicit handover terms. Document code, repository, hosting, analytics, domain and service-account ownership.
Side by side
| Decision | WordPress | Custom build |
|---|---|---|
| Price to compare | Build, hosting, paid dependencies, updates and support | Build, hosting, external services, updates and support |
| Editing | WordPress editor and configured components | CMS or editing workflow in the agreed scope |
| Performance | Test the chosen theme, plugins, hosting and content | Test the chosen build, services and content |
| Maintenance | WordPress core, theme, plugins, hosting and integrations | Framework, packages, hosting and integrations |
| Lead capture | Configured form or journey | Journey defined in the build scope |
| Ownership | Site, hosting, licences, accounts and data | Code, repository, hosting, accounts and data |
Compare cost from live quotes
Use current written quotes for the brief. Ask both suppliers to itemise:
- discovery, content, design, build and migration
- hosting and third-party services
- themes, plugins, packages and licence renewals
- backups, updates, monitoring and support
- analytics, consent and integration work
- handover, training and change requests
Our custom builds start at £2,000 for a lead-capturing site and £5,000 with ecommerce and CRM, fixed and itemised. Optional care is £450 a month. Use current written prices for the WordPress option and compare both over the same period.
FAQ
Is WordPress suitable for SEO?
It can be. Search performance depends on the content, crawlability, internal linking, structured information and technical implementation. Test the proposed theme, plugins and hosting with representative pages, and assign responsibility for ongoing checks.
Can we edit a custom build ourselves?
Yes, when an editor or CMS is included in the scope. List the content types and fields your team needs to change, then test that workflow during acceptance.
We already have WordPress. Should we move?
Start with the commercial brief and current evidence. Keep the implementation when it supports the required customer tasks, the team can operate it, ownership is clear and measured performance meets the agreed target. Compare a rebuild only when you can name the requirement it would address.
Who owns what on each route?
Ownership depends on the contract and account setup. For either route, record the domain, repository or site export, hosting, analytics, consent tool, licences and administrator access. Our custom-build handover puts the agreed codebase, domain and accounts in your name.
Use the two-minute scorecard to compare the route against your brief and leave with a tailored plan that is yours to keep.
web-design · comparison