Just moved to a new hosting provider and your website feels slower? This happens more often than you’d think, and usually the problem isn’t the new server itself, but settings that were carried over or haven’t been properly configured yet. Think of DNS that hasn’t fully propagated, missing caching, differing PHP settings, or a database that wasn’t optimally transferred. In this article, we’ll walk you through the main causes and solutions step by step.
First check if the problem is really server-related
Before searching for technical causes, it’s useful to check whether the problem is actually server-related. Test the loading time with a separate tool instead of just your own browser, since that may still show old files from the cache. Also compare how the site performs from a different device or network. Sometimes the problem is local: an outdated DNS cache on your own computer or router can cause you to still (partially) connect to the old server, giving confusing slow or inconsistent results.
DNS and caching: the most common culprits
After a move, your domain’s DNS needs to point to the new server. This change isn’t rolled out everywhere in the world at the same time: providers and networks use different cache times (TTL) for DNS records. So it’s possible that visitors in one country are already on the new, fast server, while others are still (temporarily) following the old route. This can feel like an inconsistent or slower website, while in reality it’s just a matter of waiting.
Server-side caching also plays a role. Many hosting environments use caching at the server level to serve pages faster. Right after a move, that cache is usually still empty, which makes the first visits after migration feel slower than normal. Only after the cache has been built up will you see the actual speed level of the new environment.
Check DNS propagation
Use an online DNS check tool to see whether your domain already points to the new IP address worldwide.
Wait out the TTL
Give the DNS change the time specified in the TTL value before drawing further conclusions about speed.
Let the cache build up
Visit a few important pages yourself a couple of times, so that the server-side cache builds up before you start comparing.
If DNS or email isn’t working properly after the move, also read our explanation about domain names and DNS settings for more background.
PHP settings and caching on the new server
Every hosting environment has its own PHP configuration: memory limit, PHP version, and whether opcode caching such as OPcache is active. If the new server uses a different PHP version than the one your site was built on, this can cause slower loading or even error messages. Check in your control panel which PHP version is active and whether it matches what your site needs.
Caching plugins (for a CMS like WordPress) can also get confused after a move, for example because they still refer to old file locations or IP addresses. It’s wise to reconfigure caching plugins after a migration or temporarily disable them to test whether that makes a difference.
Database and files: transferred correctly?
A slow website after a move can also indicate a database that wasn’t fully or optimally transferred. Check whether all tables are present and whether the connection to the database runs smoothly, without delay or error messages in the log files. A database that connects via a detour (for example, an incorrectly configured hostname) can cause noticeable delay.
Also check whether all files have been fully transferred, including images, uploads, and any external scripts. Missing files often lead to repeated error messages in the background, which can unnecessarily extend a page’s loading time. A quick look at the error logs in your control panel often immediately shows whether something is going wrong when retrieving files or data.
Not sure if you’ve transferred everything correctly, or would rather have it done for you? Check out the options to switch to Tandata, where the migration is carefully guided. And if your email isn’t working well after the move, check the settings at business email hosting.
Frequently Asked Questions
How long does it take before DNS changes are fully propagated?
This depends on the TTL value set for the domain. A low TTL results in faster propagation, while a higher TTL can take longer before all networks pick up the change.
Why does my site sometimes load fast and sometimes slow after the move?
This is often because different networks and providers still show different DNS data. Once propagation is fully complete, this difference disappears on its own.
Can a wrong PHP version really affect speed?
Yes, an outdated or unsuitable PHP version can cause slower loading and sometimes even compatibility issues with plugins or themes.
Do I need to reconfigure caching plugins after a move?
Often yes. Caching plugins sometimes store server-specific data that’s no longer correct after a move, so a check or reset is advisable.
Conclusion
A slower website after a move is usually caused by DNS propagation, a still-empty cache, differences in PHP settings, or an incomplete transfer of files and database. Go through the steps in this article and in most cases the problem will be quickly found and resolved.