Slow after moving from GoDaddy to Hostinger

01

What GoDaddy was doing for you

GoDaddy's help centre says its Managed Hosting for WordPress plans include caching with a CDN and object caching built in. Depending on eligibility, the CDN is either a full-page cache CDN or a static asset cache. GoDaddy also blocks many third-party caching plugins, such as WP Super Cache and W3 Total Cache, because its hosting already caches.

GoDaddy's help centre says the Flush Cache option in your dashboard comes from a GoDaddy plugin. Third-party write-ups name it gd-system-plugin and place it in wp-content/mu-plugins.

So a site that came from GoDaddy may have no caching plugin at all. It didn't need one there.

02

What Hostinger uses instead

According to Hostinger's documentation:

• Hostinger's docs point to the LiteSpeed Cache plugin for caching.
• Object Cache is based on LiteSpeed Memcached. It's turned on from the WordPress Overview section of the Hostinger dashboard, and only on Business Web Hosting or higher plans (last checked November 2026).
• PHP version is set in hPanel under PHP Configuration.
• Web and cloud hosting data centres are in Europe, Asia, North America and South America, and you pick one at setup (last checked November 2026). Hostinger CDN is a separate option.

03

What to check after the move

1. 01

   Remove GoDaddy's leftovers. If gd-system-plugin or other GoDaddy files came across in wp-content/mu-plugins, they were written for GoDaddy's cache and CDN. Must-use plugins have no Deactivate link in WordPress. Once you've confirmed the site is off GoDaddy, take a backup first. Then rename the file or move it out of wp-content/mu-plugins, or ask GoDaddy support to help.

2. 02

   Install and configure LiteSpeed Cache. Then check a logged-out page load in the response headers to see whether the page is served from the cache.

3. 03

   Enable Object Cache if your plan includes it.

4. 04

   Check the PHP version in hPanel and compare it with what your plugins and theme support.

5. 05

   Check the data centre. Confirm the site sits in the region closest to most of your visitors. If it doesn't, Hostinger documents a way to move a web or cloud plan to another data centre from the Plan Details page.

6. 06

   Replace the CDN. GoDaddy's CDN was part of the old plan. If you relied on it, set up Hostinger CDN or another CDN and make sure it points at the new origin.

7. 07

   Check cron. Some managed hosts handle WordPress cron differently. Confirm scheduled tasks run without firing on every page load.

8. 08

   Check email and DNS. If the domain stayed at GoDaddy, make sure the DNS records point to Hostinger and nothing is still resolving to the old server.