How WordPress works

WordPress is an open-source content management system (CMS) that powers roughly 40% of all websites on the internet. It separates content (pages, posts, images) from presentation (themes, templates), so you can update text and images through an admin dashboard without touching any code.

WordPress itself is free. Costs come from hosting, premium themes, plugins, and the designer or developer who builds and configures it for you. A professionally built WordPress site typically costs between £1,200 and £4,000 depending on complexity — not vastly different from a custom build at the same level.

The most important thing to understand: WordPress is a platform. A custom site is code written specifically for you. Both can look identical to a visitor. The differences are under the bonnet.

WordPress: pros and cons

Pros

  • Easy for non-technical users to update content
  • Massive plugin ecosystem — almost any feature available
  • Large community — easy to find support and developers
  • Good SEO tools (Yoast, RankMath)
  • Familiar interface — most clients already know it
  • Works well for content-heavy sites and blogs

Cons

  • The most hacked CMS in the world — constant security updates required
  • Plugins add bloat, conflicts, and vulnerabilities
  • Default performance is poor without optimisation
  • Themes and page builders (Elementor, Divi) add layers of CSS and JS that slow pages down
  • Requires ongoing maintenance — updates, backups, security monitoring
  • Can become slow and bloated as sites grow

Custom website: pros and cons

Pros

  • No unnecessary code — loads only what the site needs
  • Significantly faster by default — no CMS overhead
  • No plugins — no plugin conflicts, vulnerabilities, or bloat
  • Full design freedom without theme constraints
  • Smaller attack surface — far less targeted than WordPress
  • Simpler maintenance — no CMS updates to manage

Cons

  • Content updates require developer involvement (unless a CMS layer is added)
  • Fewer off-the-shelf integrations — custom development needed for complex features
  • Higher cost if you need many dynamic features
  • Smaller pool of developers who can maintain it

Speed and performance

This is where the gap is most noticeable. A default WordPress installation, even on decent hosting, typically scores 50–65 on Google PageSpeed mobile. Add a page builder like Elementor, a few plugins, and a premium theme, and that score can drop to 30–40.

A lean custom site — hand-coded HTML, CSS, and minimal JavaScript — routinely scores 95–100. This isn't an unfair comparison: it reflects the actual difference in what gets sent to the browser.

WordPress can be optimised — caching plugins, image compression, removing unused CSS — but you're fighting against the platform's nature rather than working with it. It's harder work to achieve the same result.

Security

WordPress sites are the most frequently targeted by automated attacks because there are so many of them. An unpatched plugin, a weak admin password, or an outdated theme can compromise a site in minutes. WordPress security requires ongoing vigilance: regular core updates, plugin updates, theme updates, backups, and ideally a web application firewall.

Custom sites are not immune to security issues, but they present a much smaller, less predictable target. There are no known plugin vulnerabilities to exploit, no standard admin login URL, and no publicly documented attack surface. The security burden is lower.

When WordPress makes sense

  • You publish content frequently (blog, news, resources) and want to manage it yourself without developer involvement
  • Your team needs multiple editors with different permission levels
  • You need e-commerce via WooCommerce and a developer to set it up properly
  • You require specific plugins that would take significant custom development to replicate
  • The site will grow substantially in content over time and you want a familiar CMS

When a custom site makes sense

  • Performance is a priority — you want top Core Web Vitals scores out of the box
  • Security and low maintenance overhead matter to you
  • Content doesn't change frequently — services pages, landing pages, portfolio
  • You want the lightest possible site without layers of CMS abstraction
  • You've been frustrated by WordPress maintenance, plugin conflicts, or slow page speeds

The hybrid approach: A custom-built front end can be paired with a headless CMS (like Contentful or Sanity) so you get the performance of a custom site with the content management convenience of a CMS. This adds some complexity and cost, but for the right project it's the best of both worlds.

What to do next

If you're comparing website builder options too, the Wix vs Squarespace vs custom site comparison covers that ground. To see what a custom-built site from this studio includes, read about the services or get in touch to discuss which approach suits your project.