WordPress or a custom website? How to choose, and when each one pays off

The short answer

Choose WordPress when a standard structure fits your business, your team already knows it and you want a large ecosystem of themes and plugins. Choose a custom-built site when your offer doesn't fit a theme's sections, when performance, security and ownership matter more than plugin choice, or when the site has to connect to systems a plugin can't handle well. Neither is cheaper in every case: WordPress usually costs less to launch, and a custom site usually costs less to keep fast and secure.

If the alternative you're considering is a hosted builder rather than a coded site, see Webflow vs WordPress and Framer vs WordPress.

We should say where we stand. Dardo's published projects are custom builds in Astro and Next.js, so read this as the view of a studio that builds the custom side, and use the table below to check our reasoning.

What each option actually means

WordPress is free, open-source software released under the GPL (WordPress.org). It's by far the most common CMS: on 12 October 2026, W3Techs reported it on 40.1% of all websites and 58.6% of the sites whose CMS it can identify (W3Techs). A WordPress site can be a purchased theme with plugins, or a custom theme built for one business. Those two are very different projects.

A custom website is designed and coded for your content and visitors, without a general-purpose theme. "Custom" doesn't mean you lose an admin panel: most custom sites today use a headless CMS, where editors write in a web interface and the site is built from that content. That's how this site works: dardo.studio is built with Astro on Cloudflare, and its pages, services and articles are edited in a headless CMS with drafts, previews and scheduled publishing.

Side by side

For speed, our website platform speed report shows the share of WordPress sites (with and without Elementor or Divi) that pass Core Web Vitals for real visitors, next to Webflow, Wix, Shopify, Astro and Next.js.

When WordPress is the right choice

• Your structure is standard. A blog, a services site or a small catalogue fits WordPress's model well, and a good theme gets you there quickly.
• Your team already runs WordPress and knows how to update, back up and secure it.
• You need a specific plugin that solves a real problem, such as memberships or a particular booking flow, and building it would cost more than living with the plugin.
• Budget is tight and time is short. A theme-based site is the fastest way to be online with something decent.

When a custom website pays off

• Your offer doesn't fit a theme. If you keep bending a theme's sections to explain what you sell, the structure is working against you.
• Speed and stability matter. Every plugin adds code to load and update. WordPress's own security guide warns that older versions don't receive security updates (WordPress hardening guide), and the same applies to themes and plugins: someone has to keep them current.
• You need real integrations. Payments, bookings, a CRM or your own data are often cleaner as code than as a chain of plugins. For Superame we built the ranking, payment verification and refund handling directly into an Astro app.
• You publish in several languages. A custom site can give every language its own URLs and metadata from the start. A medio tono runs in four languages with a 2,144-URL sitemap and hreflang alternates on every page.
• You want to own everything. The code lives in your repository and the content in a CMS you control, on hosting you choose.

The middle path: headless WordPress

You can keep WordPress as the editing tool and build the public site separately, reading content through the WordPress REST API (WordPress developer docs). Editors keep the interface they know; visitors get a fast custom front end. The trade-off is that you now run two systems, and previews and plugins that change the front end need extra work.

If you're already on WordPress

Moving off WordPress is a migration, not a redesign. WordPress's export tool writes posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies and users to an XML file (WordPress.org), and Astro maintains a guide for migrating from WordPress. The hard parts are the things outside the post body: SEO titles stored by plugins, shortcodes, image URLs under /wp-content/uploads/, and category or tag archives that still get traffic. Each one needs a place in the new site or a permanent redirect. Our website migration SEO checklist walks through that process.

Questions to settle before you decide

1. Who will edit the site every week, and what do they need to change?
2. Which integrations are must-haves, and does a maintained plugin exist for each?
3. Who will apply updates and backups, and how often?
4. Do you need more than one language now or within a year?
5. How much does each option cost over three years, including hosting, plugins, maintenance and changes?

The last question changes most decisions. A cheap launch with expensive upkeep isn't cheap; our guide to what a website costs in Colombia lists the recurring fees to include.

How Dardo can help

We design and build custom websites through our web design and web development services, and move existing WordPress sites through website migration. If your team needs to stay on WordPress, tell us in the brief; we'll say before quoting whether we're the right team for it. Start with a short brief.