WordPress Slow on Shared Hosting

Caching plugins reduce how often PHP and the database need to run by serving pre-built pages. This helps significantly, but it does not eliminate the problem. Uncached requests, which include logged-in users, the checkout process on WooCommerce, search results, and any pages excluded from cache, still hit PHP and the database on a shared server with all its constraints.

More fundamentally, plugins cannot change the server configuration. They cannot increase PHP-FPM worker counts, add Redis, tune MySQL, improve I/O limits, or reduce the impact of neighbouring sites on your performance. These are server-level constraints that require a server-level solution.

The clearest indicator is time to first byte, which is how long the server takes to start sending a response. On a properly configured VPS, WordPress time to first byte should be under 200 milliseconds for most pages. On shared hosting, TTFB over 600 milliseconds is common, and over 1 second during busy periods is not unusual.

You can check TTFB using Google PageSpeed Insights, GTmetrix, or browser developer tools. If your TTFB is consistently high and you have already implemented basic caching, the problem is almost certainly the hosting environment rather than WordPress itself.

DigitalOcean and Hetzner are both excellent choices for most WordPress sites. DigitalOcean has a well-known interface, good documentation, and reliable performance. Hetzner offers better value for money at the same specifications and is a strong choice for UK and European audiences.

For most business WordPress sites, a Droplet or Hetzner VPS with 2 vCPUs and 4GB RAM running a LEMP stack or OpenLiteSpeed will comfortably outperform shared hosting at a lower monthly cost than premium shared hosting tiers.

With proper DNS management, downtime is minimal. We set up and fully test the site on the new server before making any DNS changes. We reduce the DNS TTL in advance so the cutover propagates quickly. For most sites, the transition period where some visitors may still see the old host is a few minutes at most, and we time the cutover to happen during a low-traffic period.

Managing a VPS does require more involvement than shared hosting, where the hosting company handles all server administration. However, we document everything we configure and, for clients who do not want to manage the server themselves, we offer ongoing server management retainers covering security updates, PHP updates, SSL renewal monitoring, and database maintenance.

Many clients find that after the initial setup, a VPS requires very little active management, particularly when automated updates and monitoring are in place.

We diagnose before we recommend. Some slow WordPress sites genuinely are caused by bloated plugins, unoptimised images, slow third-party scripts, or poor theme code rather than the hosting environment. Our diagnostic review identifies what is actually causing the slowness. If the problem is something that can be fixed without migrating, we will tell you honestly rather than selling you a migration you do not need.

In our experience, most sites above a basic level of WordPress optimisation are constrained by shared hosting, but we verify this before recommending action.

Migration cost covers VPS setup, server stack configuration, WordPress migration, SSL, firewall, and DNS cutover. It depends on the size and complexity of your site and whether WooCommerce or any specific integrations are involved. We provide a fixed-price quote after reviewing your current setup.

The ongoing VPS cost itself is typically comparable to or lower than a premium shared hosting plan, with significantly better performance.

A standard WordPress site migration from shared hosting to a new VPS typically takes 2 to 3 days from start to DNS cutover. WooCommerce stores or sites with complex setups generally take 3 to 5 days to migrate and test thoroughly.