WordPress slow after moving host? Start here

01

1. Caching didn't come with you

Many hosts do page caching at server level, such as SiteGround's SG Optimizer or LiteSpeed Cache on LiteSpeed servers. When you move, that cache layer stays behind with the old host. The caching plugin might still be installed but do nothing on the new server.

• Check which web server the new host runs (Nginx, Apache or LiteSpeed) and use a caching plugin that works with it.
• Deactivate caching plugins built for the old host.
• Load a page twice in a private window and check the response headers for a cache hit.

02

2. PHP version and settings

The new server might run an older PHP version, or a newer one some plugins don't handle well.

• Check the PHP version in the host's control panel and under Tools > Site Health in WordPress.
• Compare memory_limit and max_execution_time with the old host.
• Make sure OPcache is enabled.

03

3. DNS and CDN

• If you used Cloudflare or another CDN, confirm it points to the new server's IP, not the old one.
• Check that DNS has fully moved. Some visitors may still reach the old server for a while.
• Watch for duplicate caching, where both the CDN and a plugin minify or combine files, which can break or slow pages.

04

4. Object cache and database

• If the old host provided Redis or Memcached and the new one doesn't, a plugin may be trying to connect to a cache that doesn't exist, on every request.
• Large autoloaded options in wp_options slow every page. Migrations sometimes bring transients and logs along with them.
• Check that the database is on the same server or close to it.

05

5. Server location

If your visitors are in South Africa and the new server is in the US or Europe, every request has to travel further. A CDN helps with images and static files, but uncached pages and wp-admin still go to the origin server.

06

6. Leftovers from the migration

• Hard-coded URLs pointing at the old domain or a temporary URL
• Migration plugins still active
• Cron jobs running twice, or WP-Cron firing on every page load
• Images or files requested from the old server

07

How to narrow it down

Test the same page before and after changes, logged out. Look at Time to First Byte. If TTFB is slow, the problem is on the server: caching, PHP or the database. If TTFB is fine but the page is still slow, look at the front end, starting with image sizes and scripts.

08

Guides for specific moves

• SiteGround to CloudwaysSlow after moving from SiteGround to CloudwaysMoved from SiteGround to Cloudways and the site got slower? SiteGround's caching stays behind. Here's what to switch off, what to set up with Breeze, Varnish and Redis, and how to check it.
• GoDaddy to HostingerSlow after moving from GoDaddy to HostingerMoved WordPress from GoDaddy to Hostinger and it slowed down? GoDaddy's caching and system plugin don't come with you. Here's how to set up LiteSpeed Cache and what to clean up.
• Afrihost or xneelo to HostingerSlow after moving from Afrihost or xneelo to HostingerMoved a South African WordPress site from Afrihost or xneelo to Hostinger? Server location matters. Here's how local hosting compares with offshore servers, and what to check after the move.