When to Move Off Shared Hosting (and When Not To)

The reputation, and the reality

Shared hosting has a poor reputation, earned honestly: neighbours on the same machine can slow you down, and a badly run provider oversells. But most sites move too early, and pay more for a problem they did not have.

The signs it is genuinely time

• Response time you cannot fix. You have optimised the site and the first

byte still takes a second or more at quiet times. That is the server, and it is the one problem front-end work cannot solve.

• A neighbour's problem becomes yours. Your site goes down because someone

else's did, or your mail is blocked because another tenant on the address sent spam. You are being judged for a reputation you did not build.

• You need something shared hosting does not offer. A particular software

version, a background process, a scheduled job that runs for longer than the provider allows, or a resource limit you keep hitting.

• You cannot get an answer. Support that cannot explain an outage is a

problem in itself, because you cannot plan around what you cannot understand.

The signs it is not

• Your site is slow but small. A slow small site is almost always an

unoptimised image or an unminified script. Moving host makes it fast for a week, until the same files make the new server slow too.

• You want to feel more professional. That is not a technical reason, and it

is the most expensive one.

• You read that shared hosting is bad. It is bad for some sites. It is

entirely adequate for a brochure site, a small shop, or a blog with steady traffic.

• You have not measured anything. Without a number for response time and

traffic, a move is a guess, and guesses about infrastructure are expensive.

If you do move

Plan it as a cutover, not a leap:

1. Build the new site on the new host and test it by address before changing

anything public.

1. Lower the DNS record's time-to-live a day ahead, so the change propagates

quickly when you make it.

1. Move the files and the database, then verify the content is identical.
2. Set up mail and the certificates on the new host before the switch.
3. Change DNS once. Do not move back and forth, because each change is a fresh

period of uncertainty for search engines and for readers.

The honest summary

Move when you can name the problem and it is the server. Stay when the problem is the site. A slower, cheaper host you understand beats a faster one you do not, and the work of a move is better spent on the page the reader is waiting for.