Pick custom code when you want fast load times, strong SEO, and minimal monthly fees, and your content changes infrequently. Pick WordPress when non-technical editors need to update content weekly, you have a content team that already knows it, or you specifically need a WordPress plugin like WooCommerce. Both can ship great work — the wrong tool for your context will hurt you whichever you pick.
Disclosure: WebSilm builds with both. About a fifth of our work is WordPress (usually on inherited sites or where a client genuinely needs WooCommerce); the rest is custom code on static-first stacks. We don't have a horse in this race. What follows is the framework we actually use when a small business asks us which way to go.
When WordPress wins
WordPress is the right pick when one or more of these is true:
- Non-technical editors update content weekly or more often. If a marketing manager or admin person publishes 2+ blog posts per month, WordPress's editor experience is genuinely better than asking a developer to deploy each change.
- You already have a team that knows it. Switching tools costs more than the tool itself when there's institutional knowledge to throw away.
- You specifically need WooCommerce, LearnDash, MemberPress, or another flagship WordPress plugin. The plugin ecosystem is genuine — building equivalents from scratch costs more than living with WordPress's overhead.
- The site is content-heavy with a long tail. A news site, a recipe blog, a knowledge base with 500+ articles — these benefit from WordPress's mature taxonomy, search, and authoring tools.
When custom code wins
Custom code is the right pick when:
- Page speed is part of the product. If you're a SaaS marketing site, an agency portfolio, or a SaaS dashboard's marketing pages, every 100ms of load time costs measurable conversions. Custom static sites consistently load in under a second; WordPress sites typically load in 2–4 seconds.
- SEO ceiling matters. Google's Core Web Vitals reward fast, low-shift, low-input-delay sites. Custom code passes those tests by default; WordPress passes them only with careful theme and plugin discipline.
- You don't update content often. A 5-page service business site that changes 2–4 times a year doesn't need a CMS. The 'small change' work can be a €15-per-edit retainer with your developer, which is cheaper than WordPress hosting + plugins + maintenance over five years.
- Security is a sensitive area. WordPress is the most-attacked CMS on the internet. Custom static sites have no admin panel, no PHP runtime, no plugin update cycle, no SQL database — most of the WordPress attack surface simply doesn't exist.
5-year total cost: the table everyone wants but few publish honestly
Numbers below are typical ranges from real WebSilm projects, plus public WordPress hosting / plugin pricing. Your numbers will vary.
| Cost item | Custom code (WebSilm) | WordPress (typical agency) |
|---|---|---|
| Year-1 build | €500 – €2,500 | €1,500 – €4,000 |
| Hosting (year 1) | €0 – €60 (Cloudflare Pages free tier) | €80 – €240 (Kinsta, WP Engine, SiteGround) |
| Premium plugins (year 1) | €0 (none needed) | €100 – €400 (Yoast Premium, WP Rocket, security, backup) |
| Maintenance (years 2–5) | €0 – €240 total (occasional fixes) | €400 – €1,600 total (€100–400/yr update + security) |
| Hosting + plugins (years 2–5) | €0 – €240 total | €720 – €2,560 total |
| 5-year total | €500 – €3,040 | €2,800 – €8,800 |
The gap closes for very content-heavy sites where custom builds need a small CMS layer (Sanity Studio, Notion API, or Decap CMS). It widens for marketing sites that change once or twice a year.
Performance: what real measurements show
HTTP Archive's annual Web Almanac tracks Core Web Vitals across millions of sites. The 2025 report (most recent at writing) shows:
| Metric | Custom static (avg) | WordPress (avg) |
|---|---|---|
| Largest Contentful Paint (LCP) | 0.8 – 1.4s | 2.4 – 3.8s |
| Cumulative Layout Shift (CLS) | 0.02 – 0.06 | 0.08 – 0.18 |
| Interaction to Next Paint (INP) | 80 – 150ms | 180 – 380ms |
| % of mobile sites passing all 3 thresholds | 78 – 84% | 22 – 30% |
The performance gap isn't WordPress's fault per se. It's the cumulative weight of the average WordPress install: 2–3 themes installed (with one active), 15–25 plugins each loading their own CSS / JS, an admin bar, render-blocking jQuery, and image-heavy hero sliders. A carefully tuned WordPress site on a fast host can hit Core Web Vitals — but it takes work the typical small-business owner can't audit.
Three real scenarios
Scenario 1: SaaS marketing site, 8 pages, content updates twice a year
Custom code wins. The site exists to convert visitors. Speed and SEO are the actual product. Content changes are infrequent enough that a developer retainer is cheaper than CMS overhead. WordPress here would mean fighting the platform to hit the load times the conversion rate needs.
Scenario 2: Restaurant with weekly menu and event updates
WordPress wins (or a CMS-backed custom build). The owner publishes weekly. Asking a developer to deploy each menu change costs more in friction than the CMS overhead saves. WordPress + a clean theme + a couple of carefully chosen plugins is genuinely the right tool here. Or — a custom static site backed by a tiny CMS like Sanity or Decap, which gives you both: editor experience + speed.
Scenario 3: Local plumber / electrician / tradesperson
Custom code wins. A 3-to-5 page site with services, area-served, contact form, and reviews. Updates rarely. The customer journey ends in a phone call or contact form, not a content browse. Pay €600 once, host for free, never think about it again. WordPress here is over-engineering for the use case.
The decision framework
- Will a non-developer publish content more than twice a month? If yes, lean WordPress (or a CMS-backed custom build). If no, lean custom code.
- Is page speed measurable in your conversion rate? If yes (B2B SaaS, e-commerce, high-intent landing pages), custom code is usually worth it. If no (informational, local services), either works.
- Do you specifically need WooCommerce, LearnDash, or another flagship plugin? If yes, WordPress. The plugin ecosystem is real value.
What to ask any agency before they sell you either
- Will I own the code on day 1? Yes for both should be possible. If they say no, walk.
- What is the 5-year total cost, including hosting, plugins, and maintenance? Force them to put it in writing. Most agencies quote year 1 only.
- Can I switch to a different developer without rebuilding? For custom code, the answer should be yes if the codebase uses standard tools. For WordPress, this is almost always yes.
- What's the security plan? Custom static: 'no admin panel exists, this is the plan.' WordPress: who applies updates, when, and what happens if a plugin author abandons their plugin.
Bottom line
For most small businesses we work with at WebSilm — service businesses, SaaS marketing sites, agency portfolios — custom code wins on a 5-year horizon, mostly because we keep ongoing costs near zero through static hosting on Cloudflare Pages. WordPress remains the right choice for content-heavy sites with non-technical editors who publish weekly. Both platforms can ship great work; the wrong tool for your context will hurt you whichever you pick. The framework above will get you 80% of the way to the right answer for your situation.
If you're stuck on the decision and want a sanity check, we offer a free 30-minute scoping call where we'll honestly tell you which way to lean — sometimes that means recommending you don't hire us at all. No sales pitch, no follow-up emails.