WordPress powers approximately 43% of all websites worldwide. In the Netherlands, market share is similar. Almost every agency, freelancer or SMB has dealt with WordPress hosting at some point. And yet things go wrong surprisingly often, not because of WordPress itself, but because of a hosting choice that doesn't fit the situation.
This article describes what to look for when choosing WordPress hosting for a business website in the Netherlands.
Datacenter location
The physical location of your server determines loading time for your visitors. A server in Amsterdam delivers a response time of 5 to 20 milliseconds for Dutch visitors. A server in Germany, the UK or the US adds more delay, noticeable in page rendering and Core Web Vitals.
Google uses loading speed as a ranking factor. A WordPress site that loads quickly for Dutch visitors consistently scores better in Dutch search results than the same site on a server in Frankfurt. The difference isn't huge, but it's there.
Beyond speed, there's the GDPR angle. When visitors fill in personal data (contact form, newsletter, webshop), your server processes that data. A server in the Netherlands or the EU falls under European law. A server in the US (also) falls under the CLOUD Act. For most businesses, the Netherlands or another EU country is the sensible choice.
PHP version and server stack
WordPress runs on PHP. The version of PHP your provider supports directly affects speed and security. PHP 8.2 and 8.3 are significantly faster than PHP 7.x. Older PHP versions no longer receive security updates: PHP 7.4 has been end-of-life for years.
Check with your provider which PHP versions are available and whether you can switch between them yourself. Some cheap hosting packages default to PHP 7.x because they don't keep their infrastructure up to date. That's a problem, not just for performance but also for security.
Other server stack elements that matter:
- Object caching: Redis or Memcached speeds up WordPress significantly by caching database queries. Not all hosting packages offer this by default.
- Web server: Nginx generally performs better than Apache for WordPress under load.
- MariaDB/MySQL version: A recent database version speeds up queries and supports modern WordPress features.
- HTTP/2 or HTTP/3: Modern HTTP protocol for faster page rendering.
Technical foundation: what your provider should offer
Backups: how, how often and where to?
WordPress gets attacked regularly. Vulnerabilities in plugins (the most common attack vector), compromised admin passwords, malware injections. The question isn't whether something will go wrong, but when. And at that moment, you want a recent backup ready.
What a business WordPress site needs at minimum:
- Daily backups, automated
- Backup retention of at least 14 days
- Off-site storage: backups on the same server as your site get taken along in a hack
- Tested restoration process: a backup you can't restore from is worthless
Some providers offer backups as an option, not as standard. Check this. And test your backup restoration at least once a year.
Managing updates: automatic or manual?
WordPress core updates, plugin updates and theme updates are the first line of defense against attacks. Most exploits used in the wild target known vulnerabilities in outdated plugins. A WordPress installation that hasn't had a plugin update in three months is an attractive target.
There are three approaches:
Fully manual: You or your web manager pushes updates. Requires discipline and a fixed routine. Works if you actually do it.
Automatic for security updates: WordPress has the option to automatically install security releases. That's a reasonable compromise for most sites.
Managed WordPress hosting: The provider handles updates, tests them and rolls them out. Some providers (like Kinsta, WP Engine or Dutch providers like Savvii) offer this as part of their package. You pay more, but you don't have to think about it.
Managed WordPress hosting always includes a staging environment where updates are tested first. If a plugin update breaks your specific setup, you want to discover that on staging, not in production.
SSL and security
SSL is standard nowadays. Every serious provider includes free Let's Encrypt certificates. If a provider offers SSL as a paid extra, that's an outdated business model.
What else contributes to WordPress hosting security:
- Server-level firewall that blocks known attack patterns
- Malware scanning and removal (with managed packages)
- DDoS mitigation
- Isolation between customers on shared hosting: if another customer's site gets hacked, you don't want your site infected along with it
- Two-factor authentication for admin access
Support: who do you call when things go wrong?
On an average day, you barely notice your hosting provider. Support only becomes visible when something is wrong. And then quality counts.
Check with your provider:
- Is 24/7 phone support available, or tickets only?
- How fast do they respond on average to a P1 incident (site down)?
- Is Dutch language support available?
- Do they have WordPress-specific knowledge, or is it generic hosting support?
Dutch hosting providers like Savvii, Antagonist, Combell and Signet specifically target the Dutch market and offer Dutch language support. That sounds like a detail, but when you're in the middle of an incident, communication in your own language isn't a luxury.
WordPress hosting types: what to expect
Shared hosting vs. dedicated WordPress environment
Cheap WordPress hosting often runs on shared servers. Dozens or hundreds of websites share the same machine. That works for a static portfolio site, but it has consequences when a neighbouring site draws heavy traffic or has a security problem.
For a business website, or certainly for a webshop, an environment with guaranteed resources makes more sense. That can be a managed VPS or a managed WordPress environment at a provider that isolates sites at container level.
The price difference is real: a good managed WordPress environment costs 20 to 60 euros per month more than the cheapest shared hosting. But if your website needs to be available, fast and secure, that's not a debate. It's a business decision.
Summary: the five most common mistakes
In practice, we see the same patterns recurring at business WordPress sites:
- Server is in the US because the provider was cheap: slow loading times for Dutch visitors and GDPR risks
- PHP 7.x still running because nobody updated it
- Backups exist, but have never been tested for restoration
- Plugin updates get postponed because "it's working fine": until it isn't
- Support turns out to work tickets only during an incident, with an 8-hour response time
These mistakes are avoidable. They don't require big investments, but they do require conscious choices when selecting your hosting provider.
Looking for reliable WordPress hosting in the Netherlands? Explore our WordPress & Drupal hosting.