WordPress-website laten maken — custom thema, snel, vanaf €1.500

Having a WordPress website built that's still fast, secure and editable five years later. That's what this whole story is about. Not a ThemeForest template with thirty plugins fighting each other. Not a cheap freelancer who's unreachable three months in and nobody can find the page-builder licence. And not "we picked WordPress because it's free", followed by hosting at €99 a month and a site that's still slow.

At SRI Services we build WordPress sites the way software is supposed to be built: in code, under version control, tested, with a custom theme instead of a rented template, and with an admin your editors can actually use without calling a developer for every change. One operator, end to end, from €1,500 for a starter build.

What's in this article: what you actually get when we build a WordPress site, when WordPress is the right call and when it isn't, how we work differently from most WordPress builders, the plugins we include by default and the ones we explicitly avoid, how to get a WordPress site genuinely fast (PageSpeed 90+), when headless WordPress with Next.js makes sense, and what it costs from brief to live.

What you get when we build a WordPress site

A production-ready WordPress site, built on a serious stack and delivered in 2 to 6 weeks depending on complexity. Concretely:

• A custom WordPress theme written in PHP. No Elementor soup, no Divi spaghetti.
• ACF Pro for content structure. Blocks your editors can place without breaking layout by accident.
• Bedrock for project structure. Composer, .env config, proper deploys.
• A small, focused plugin set. Not 50 plugins that overlap.
• Fast hosting. A dedicated VPS or a serious Dutch host with PHP 8.x, NGINX, Redis, and HTTPS configured properly.
• A real SEO foundation. Clean URLs, sitemap, schema.org markup, hreflang for multilingual.
• Security out of the box. Automatic security updates, fail2ban on the server, daily backups.
• A blog that's not an afterthought. Proper typography, reading times, related posts, sitemap priority.

The codebase lives on your GitHub from day one. Content sits in WordPress, code sits in version control. That's how it should be. And not — like 80% of the WordPress installs we encounter — where nobody knows what's actually running on the production server.

When WordPress is the right call, and when it isn't

WordPress is great for:

• Content-driven sites. Blogs, magazines, knowledge bases, publishers.
• Corporate sites and portfolios. Business sites that get updated periodically.
• Local entrepreneurs and small businesses. When editors need to add content themselves, without a developer.
• WooCommerce e-commerce up to roughly €5M revenue — see Having a WooCommerce webshop built.
• Multi-language content sites. WPML or Polylang for NL/EN/DE and others.

Not ideal for:

• Web applications with complex user roles. Laravel is a better fit.
• Heavy real-time interaction. Chat, live dashboards, multiplayer.
• B2B SaaS platforms. Own framework + API + SPA front-end makes more sense.
• Marketplaces with complex matching algorithms. Not WordPress.

On the strategy call you'll hear honestly which direction works best for your situation. Sometimes that's WordPress. Sometimes not. Sometimes a hybrid where WordPress handles content and a separate application handles functionality.

Our approach — no plugin soup, no template show

Most WordPress builders work in one of two ways. Either tweaking a ThemeForest template until the client is happy — fast, fragile, not unique. Or using a page builder like Elementor for everything — slow, locked to a licence, nobody can maintain it later.

We do it differently:

1. Custom theme in PHP. A clean theme, based on a minimal foundation (e.g. _underscores or our own starter), that does what the site needs and nothing more.
2. ACF Pro for content structure. Editors place, reorder and edit content blocks. But can't break layout.
3. Performance from day one. Redis caching, optimised images via WebP, lazy-loading, critical CSS inline.
4. Limited plugin set. Yoast for SEO, ACF Pro for fields, WPForms or Gravity Forms for forms, Wordfence for security. No 30-plugin pile-up.
5. Version control and deploys. Git, staging environment, automated deploys via SSH or CI/CD.

The result: a WordPress site that loads fast (PageSpeed 90+), can run for years without rebuild, and that any WordPress developer can maintain — not just someone trained on your specific page builder.

Plugins we include by default, and plugins we keep out

WordPress sites we audit or take over have an average of 28 plugins. Usually three or four are genuinely needed, and the rest duplicates functionality the theme or another plugin already provides. Our standard set is deliberately small:

What we include:

• ACF Pro. For custom fields and content blocks. The spine of any maintainable WordPress theme.
• Yoast SEO or Rank Math. For sitemap, breadcrumbs, schema.org, meta-tag control.
• WPForms or Gravity Forms. For forms with spam protection and mail-tool integrations.
• Wordfence or iThemes Security. For login rate-limit, fail2ban-style blocking, malware scan.
• WP Rocket or a server-side cache (Redis + NGINX FastCGI Cache). For caching and page speed.
• UpdraftPlus or a server-side backup. For daily backups stored off the server.

What we explicitly avoid:

• Elementor, Divi, WPBakery and other page builders. Slow (40+ database queries per page), licence lock-in, they generate HTML nobody wants to maintain later.
• All-in-one SEO plugins that also do caching, security and social. Too heavy, too much responsibility in one place. A failure breaks the whole site.
• Plugins for "cosmetic problems". Animations, glittery sliders, exit-intent popups. All extra JavaScript and not essential.
• Translation plugins with external runtime dependencies. If your translations are pulled from an external API on each pageload, your site will be slow or broken at some point.
• Heavy cookie-banner plugins that load everything. Use a lightweight banner or build a minimal version yourself. The default cookie plugins are needlessly bloated.

The rule we follow: every plugin added must solve one concrete problem that wouldn't otherwise be solved. Two plugins doing the same thing — remove one. Plugins installed "just in case" but not actively used — gone.

Performance on WordPress — how we hit PageSpeed 90+

WordPress can absolutely be fast. The reason most WordPress sites are slow isn't WordPress. It's an accumulation of choices that were each "almost OK" but became unmaintainable together. Our approach to PageSpeed 90+ on mobile:

Server layer. PHP 8.2+ with OPcache enabled, NGINX instead of Apache, MariaDB or MySQL 8 with query cache, Redis as both object cache and page cache. This alone takes a typical "slow" WordPress site from TTFB 800ms down to 150ms.

WordPress layer. A minimal plugin set (see above), a custom theme that doesn't load jQuery on pages that don't need it, async/defer on non-critical scripts, and critical CSS inlined in the head.

Asset layer. Images via WebP conversion (30 to 60% smaller than JPEG), lazy-loading on everything below the fold, srcset for responsive images, and a CDN (Cloudflare or Bunny.net) for global distribution.

Front-end layer. No render-blocking fonts (use font-display: swap), limited number of font weights, SVG icons instead of icon fonts, and minify + compress on CSS and JS.

Monitoring. After launch we add performance monitoring (Cloudflare RUM or a tool like Sentry for errors). That way we know when something gets slow — not when a client calls.

On a typical WordPress site we take over, these changes lift PageSpeed from around 35–45 to 90+. For sites we build from scratch, 90+ is just the starting point at first delivery.

Headless WordPress and Next.js — when it makes sense

A trend of recent years: WordPress as CMS, Next.js (or Vue/Nuxt) as the front-end via the WordPress REST API or GraphQL. That's "headless WordPress". For some projects it's the right move. For most it's overhead.

When headless WordPress makes sense:

• A brand with multiple outputs. The same content has to feed website, app, kiosk display, external partners. WordPress is then the central content source, each output has its own front-end.
• High-interactivity needs. A fully SPA feel that PHP rendering can't match — think dashboards, configurators, product personalisation.
• Dev team already on React/Vue. Building a PHP front-end is then a step backwards.
• Performance demands beyond PageSpeed 90. Vercel Edge or Cloudflare Workers level, generated at build time.

When headless WordPress adds no value, and only cost:

• A corporate site or blog. A properly built classical WordPress site is faster than 80% of headless builds, with half the complexity.
• When SEO is critical and you don't fully control the SSR layer. Google indexes headless fine — but one config mistake and rankings take a hit.
• For a small editorial team without developer involvement. Preview, draft state and visual feedback are harder on headless than on classical WordPress.

We decide together on the strategy call which way fits. In practice we go classical WordPress with a custom theme 80% of the time, headless 20% — only where it genuinely earns its keep.

For entrepreneurs in Dordrecht, Breda, Roosendaal and across the Netherlands

Clients sit across the entire Netherlands — no travel barrier, the engagement runs remote. We've built WordPress sites for entrepreneurs in:

• Dordrecht — corporate sites, professional services, local entrepreneurs.
• Breda — B2B businesses, fashion, food, manufacturing.
• Roosendaal — logistics, transport, wholesale.
• Rotterdam — port businesses, food import, international services.
• The Hague (Den Haag) — government suppliers, law firms, premium services.
• Amsterdam — startups, agencies, content publishers, international brands.
• Utrecht — tech companies, SaaS businesses with a content layer.
• Eindhoven — tech companies, design studios, B2B.
• Tilburg, 's-Hertogenbosch, Helmond — Brabant manufacturing, SME.
• Groningen, Zwolle, Leeuwarden — northern entrepreneurs, regionally strong brands.
• Maastricht, Heerlen, Sittard — Limburg and cross-border content (NL/DE/FR).
• Leiden, Delft, Haarlem, Alkmaar — premium retail, knowledge institutions, professional services.

Whether you're in Dordrecht renewing a corporate site, in Breda putting a fashion brand online, or in Roosendaal digitising a transport company — having a WordPress website built with us works the same way. One point of contact, honest quote, fixed delivery date.

Pricing and timeline

Honest numbers. What it actually costs to have a serious WordPress site built, instead of a cheap template build you'll need to replace in a year.

• Starter (€1,500–3,500) — custom theme layer on a clean base, 5 to 10 pages, ACF for structure, baseline SEO, contact form. Live in 2 to 4 weeks. For entrepreneurs who want a real owned site fast, without the template look.
• Standard (€3,500–7,500) — fully custom theme, 10 to 25 pages, blog, NL/EN translation, CRM or mail-tool integrations, performance tuning, full schema.org. Live in 4 to 6 weeks.
• Custom (€7,500–15,000+) — sites with complex content structures, custom post types, members-only sections, external API integrations, or WooCommerce integration. Timeline by quote.

Fixed price up front, tied to a fixed delivery date. No scope-creep invoices mid-project. Hosting (from about €20/month at a serious Dutch host) and SSL are paid directly to the host. They don't show up on my invoice.

The process — from brief to live

1. Strategy call (free, 30 min). We talk through what the site needs to do, for whom, what content you have, which integrations are needed. By the end you know what it costs and how long it takes.
2. Concept document (1 week). Written scope with sitemap, content structure, technical choices, design direction and deliverables. You sign off before we start.
3. Design and build (weeks 2 to 5). Custom theme, content structure, integrations. Weekly demos on a staging environment — your feedback gets folded in directly.
4. Content and test (weeks 5 to 6). Content loaded, all pages verified, mobile and performance checked, schema markup validated, broken links scanned.
5. Go-live (week 6). DNS switch at a quiet moment, weekend monitoring, your new site is live. URL redirects are pre-arranged so your SEO carries over.

After go-live: optional monthly retainer for monitoring, security updates, small changes and plugin maintenance. Or you maintain the site yourself — both options work.

Having a WordPress website built doesn't have to be a template show or end up as plugin spaghetti. With a custom theme, a clean codebase, a minimal plugin set and hosting that fits the site, you get something that lasts years. Book a free strategy call — within 30 minutes you'll know whether WordPress is the right fit for your situation, and what it costs with us.