Bespoke Website vs WordPress: Why We Don't Use Templates

A bespoke website is written specifically for your business. A WordPress site is a template filled in with your content. The distinction sounds obvious, but the consequences run deeper than most clients realise before they've bought both.

What a Template Actually Is

A WordPress theme is code written to work for thousands of different businesses. To achieve that, it includes layout options, colour pickers, font selectors, page builder blocks, widget areas, and plugin hooks. Most of this infrastructure exists to let non-developers customise the template without touching code.

You're paying for flexibility you almost certainly won't use — and carrying the weight of it in load times, update risks, and plugin conflicts.

A typical WordPress site built on a premium theme ships with 40–100kb of CSS for layout options you've never selected. It loads a page builder JavaScript bundle whether or not you're in editing mode. It makes database queries to check for plugin updates every time a page loads. None of this is visible in the editor. All of it is visible in the load time.

What a Bespoke Site Is

A custom site has no unused code. Every component does exactly one job for your business. There are no page builder abstractions between the design intent and the output HTML.

The difference is measurable.

Load time. Our bespoke sites consistently score in the high 80s to mid-90s on Google Lighthouse mobile. Elektra by Mariyana, a violinist with a client-facing booking site we built from scratch, scores 94/100 on mobile. Mobility Scooters Mallorca, a booking and cart platform, scores 93/100. Nash Software, the studio's own site, scores 86/99 (desktop). WordPress sites with a theme and five plugins average 45–65 on the same metric, according to data from the HTTP Archive Web Almanac.

Search performance. Core Web Vitals are a confirmed Google ranking signal. A site that loads in 1.2 seconds competes differently than one that loads in 4.8 seconds — not just in user experience, but in how Google evaluates the page relative to competitors. A Lighthouse score in the 90s isn't a vanity metric. It's a structural SEO advantage.

Long-term maintenance. WordPress requires plugin updates, theme updates, PHP version compatibility checks, and security patching. A bespoke site has no plugin ecosystem to manage.

A Real Before and After: Mobility Scooters Mallorca

Before working with us, Mobility Scooters Mallorca had an existing site — content on a page, but no rankings for the terms that mattered, no booking capability, and a visual presentation that didn't reflect the quality of the service.

We rebuilt the site as a custom Next.js application. The new site achieved a 93/100 mobile Lighthouse score. Within weeks of launch, it was ranking on page one of Google for "hire a mobility scooter mallorca" and "mobility scooter hire mallorca" — competitive local search terms where the site had previously had no presence. Bookings started coming in through the site directly, confirmed via Resend.

The before and after here isn't about aesthetics (though those improved too). It's about a business that previously had no web presence worth speaking of, and now has one that earns its keep.

The Cost of WordPress Maintenance Over Three Years

The real cost of a WordPress site isn't the build. It's the ongoing management.

A typical mid-range WordPress site will incur:

Plugin licences: Most professional WordPress functionality requires premium plugins — SEO tools, form builders, caching, security, backup. Plan for €200–€400 per year in recurring plugin licences. These are not optional: stop renewing, and you lose security updates. Let security updates lapse, and the site becomes a liability.

Managed hosting: Shared WordPress hosting is cheap and unreliable. A managed WordPress hosting plan with adequate performance and reliability — WP Engine, Kinsta, or similar — costs €150–€300 per year.

Compatibility maintenance: WordPress, PHP, and the plugin ecosystem are in constant motion. When WordPress releases a major update, plugins may break. When a plugin releases an update, it may conflict with the theme. When PHP reaches end-of-life and the host upgrades, something will break. Budget 1–2 hours of developer time per year at minimum, more if you're unlucky.

The rebuild: Most WordPress sites based on a purchased theme have a natural lifespan. Theme developers stop issuing updates. Plugin dependencies conflict. The Gutenberg editor evolves in ways the theme wasn't designed for. The site that cost €1,200 in 2022 often needs a full rebuild in 2024 or 2025 — and you're back at the start.

A bespoke Next.js site runs on Vercel (€0–€20/month for most traffic levels), has no plugin licences, and doesn't require compatibility maintenance. The code doesn't rot. The total cost of ownership over three years is frequently lower than the equivalent WordPress site, built on less robust foundations.

What Content Management Looks Like in Practice

One of the most common objections to bespoke sites is the assumption that clients will be locked out of editing their own content. This hasn't been true for several years.

We use Sanity for larger content-managed sites. Sanity is a headless CMS — the editing experience lives at a separate URL from the site, and the editor is clean, structured, and designed for non-developers. Adding a blog post, updating a service description, or editing a team member's bio is done through a straightforward admin interface. No code required. No theme dependencies. No risk of accidentally breaking the site with an edit.

For clients who compare this to WordPress's wp-admin, the practical difference is significant. WordPress's editing experience is cluttered with plugin notices, update warnings, theme settings menus, and widgets that may or may not be connected to what's visible on the site. Sanity's content interface shows only the fields that exist on the page — nothing more.

For smaller sites, content lives in MDX files or TypeScript data files in a GitHub repository. Non-developers can edit these via GitHub's web interface. The studio handles anything more complex through the retainer.

Either way: content updates are accessible to clients. The site doesn't require us to make a copy change on their behalf.

The Real Reason Most WordPress Sites Underperform

Performance is the most visible symptom, but it's not the only one. The more fundamental problem is that a WordPress template wasn't designed for your business. It was designed for all businesses, which means it's optimised for none of them.

The homepage hero of a template is designed to accommodate any headline — which means it's designed to make no headline particularly compelling. The navigation structure was designed to support any number of pages — which means there's no strategic thinking about which pages your specific audience needs to reach quickly. The typography scales to fit any content — which means no deliberate choice was made about how your content should feel to read.

A bespoke site starts from the opposite direction. Before any design work begins, we understand what the business does, who the audience is, and what the site needs to make them do. Every structural and visual decision follows from that. The result is a site that's been designed to do a specific job — not a site that could theoretically do any job if configured correctly.

A focused site does more with the same traffic — because the visitor is not fighting the design to find what they came for.

When WordPress Makes Sense

We're not arguing that WordPress is always the wrong choice. It's the right choice when:

• You need a site tomorrow and have no budget for design
• You have an in-house team trained on WordPress CMS
• You're building a content-heavy site with 500+ posts that need community plugins

None of these apply to most of the clients we work with. Most need a site that loads fast, ranks well, and doesn't require a developer to update the homepage hero text. If you're comparing on price, our pricing is transparent — bespoke is often closer than people expect.

What We Use Instead

We build in Next.js — a React framework that generates static pages at build time. Content is managed through a headless CMS (Sanity) or simple MDX files, depending on the project. The result is a site that deploys to a global CDN, has no server to maintain, and can be updated by non-developers for content changes.

The performance gap between this approach and a WordPress template is structural — not a configuration problem or an optimisation gap. A statically generated Next.js site serves pre-built HTML from a CDN edge node. A WordPress site queries a database and renders HTML on every page load. Different architectures, different results.

Frequently Asked Questions

Can you migrate my existing WordPress site?

Yes. We rebuild the design and content in Next.js. The URL structure is preserved where possible, and we handle 301 redirects for changed paths so SEO isn't disrupted. Typical timelines for a migration follow the same pattern as a new build — up to 2 weeks for The Mark, up to 3 for The Site.

What CMS do you use if not WordPress?

We use Sanity for larger content-managed sites. For smaller sites, content lives in MDX files or TypeScript data files — no CMS login needed for minor updates.

Will I be locked in to your studio for future changes?

No. Everything is in a GitHub repository that you own. Any Next.js developer can pick up the project. We write clean, documented code with that handoff in mind.

How significant is the Lighthouse score difference in practice?

It's significant enough that it affects both user behaviour and search ranking. Google's own research shows that as page load time increases from one second to three seconds, the probability of a mobile user bouncing increases by 32%. The Core Web Vitals ranking signal means that performance also affects where the site appears in search results. A score in the 90s versus a score in the 50s is not a cosmetic difference. It's a commercial one.