How to Test Website Speed Before You Switch Web Hosts

Quick answer: Test your site speed with free tools like PageSpeed Insights and GTmetrix on three different days and record time to first byte, load time and page size. A slow server response points to the host; a fast response with slow pages points to your images and plugins.↗ Share on X

Test your website speed before you switch hosts by running the same three checks on three different days, writing down the numbers, and comparing them with the same checks after the move. If you skip the "before" numbers, you cannot tell later whether the new host is faster, slower, or the same. This takes about 30 minutes and costs nothing.

Many people switch hosts hoping to fix a slow site, then find nothing changed. The slowness was in the images, plugins or theme, not in the server. A quick test tells you which one it is.

Why test before you change anything?

READ ALSOHow to pick a host that grows with your online store →5 Simple Checks to Know If Your Web Hosting Is Too Slow →9 Signs You Are Misunderstanding the Difference Between Shared and VPS Hosting →

A new host costs money, takes time, and carries a risk. Moving a site can break links, email and settings. So first prove the host is the problem.

You need two things:

1. A baseline. Your speed numbers today, written down.

2. A cause. Whether the slowness comes from the server or from your own site.

Without these, you may pay for a better plan and end up with the same slow pages.

Which free tools should you use?

You do not need paid software. These free tools are enough:

You can use two of them. The point is to use the same tools and settings before and after.

What numbers should you write down?

READ ALSOWhere Is Your Web Server? Check It and Fix Slow Load Times →Where Is Your Web Host's Server? Find It and Test Its Speed →Shared vs VPS Hosting: 8 Signs Your Site Has Outgrown Shared →

Open a simple note or spreadsheet. For each test, record:

1. Date and time of the test.

2. Page tested. Test your home page and one inner page, such as a product or blog post.

3. Time to first byte (TTFB). This is how long the server takes to start answering. It is the best number to judge the host itself. Many testing tools label it "server response time" or "waiting".

4. Largest Contentful Paint (LCP). This is when the main content, such as the big image or headline, shows up. It is closer to what visitors feel.

5. Total page size in megabytes.

6. Number of requests. How many separate files the page loads.

7. Test location. Pick the city closest to most of your visitors.

Google gives guidelines for LCP: under 2.5 seconds is considered good. Use those as a rough guide, not a rule that fits every site.

How do you tell if the host is the problem?

This is the key question. Use the time to first byte as your guide.

• Slow TTFB on every test and every day: the server is slow to respond. The host may be the cause. It could also be a heavy site or database, but the host is a suspect.
• Fast TTFB but slow LCP: the server is fine. The problem is on the page: big images, too many scripts, a heavy theme.
• Fast on some days and slow on others, usually in the evening: the server may be crowded, which is common on cheap shared plans.
• Slow only from far away: the host's location may be far from your visitors. A content delivery network (CDN) may solve it without a move.

A CDN is a service that keeps copies of your files in many cities. Visitors get them from a nearby copy. Many hosts offer one for free or for a small fee.

What should you test on three different days?

One test can mislead you. Speed changes with time of day and traffic. So do this:

1. Test in the morning, when traffic is usually low.

2. Test in the evening, when it is often busy.

3. Test on a weekend and on a weekday if you can.

4. Run each test three times in a row and use the middle result. The first run often loads slowly because nothing is saved yet.

After about three days you will see a pattern. Write the average of each number.

What can you fix before moving?

Many "slow host" problems are really site problems. Check these first. They are free and take little time.

1. Compress images. A single photo of several megabytes can slow the whole page. Resize to the size shown on the page and save in a modern format such as WebP.

2. Remove plugins you don't use. If you use WordPress, each plugin adds code to every page.

3. Turn on caching. A cache saves a ready-made copy of your page, so the server does less work each time. Many hosts and plugins have it built in.

4. Check your theme. Heavy themes with many animations load slowly.

5. Limit outside scripts. Chat widgets, fonts, ads and trackers each add a delay.

6. Update PHP. If your host lets you pick a newer PHP version, it can speed up WordPress. Back up first.

7. Clean the database. Old revisions and spam comments pile up.

After each change, test again and write down the new numbers. Then you know what worked.

What should you look for in a new host?

If your tests still point to the server, you may be ready to move. Before paying, check:

• Server location. Is there a data center close to your visitors?
• What the plan really includes. "Unlimited" often has fair-use limits. Read them.
• Renewal price. Many hosts show a low first-year price and charge more later. Ask what the second year costs.
• Free migration. Some hosts will move your site at no cost. Ask first.
• Backups. Are they daily? Can you restore them yourself?
• Support. Is there live chat or phone? Test it with a simple question before you buy.
• Money-back period. A trial lets you test speed on the new host before committing.

Ask the new host for a trial or a short first month if you can. Then run your same tests there.

How do you compare the new host fairly?

Moving your site is only half the job. To compare fairly:

1. Use the same tools, same pages, same test location as before.

2. Test at the same times of day.

3. Wait 24 to 48 hours after the move, so the caches and DNS settings have time to settle.

4. Compare your three key numbers: TTFB, LCP and page size.

5. Look at results over several days, not just once.

If your TTFB drops clearly and your pages feel faster, the move worked. If the numbers are close to the old ones, the host was not the main problem, and you can keep looking at your site's own weight.

What should you watch out for during the move?

A host change can break things if you rush it. Keep this short checklist handy:

1. Back up the whole site and its database before starting.

2. Lower your DNS time-to-live a day before the move, if your provider lets you, so the change spreads faster.

3. Keep the old host active for at least a week after the move, until you are sure everything works.

4. Check your email. If your email runs through the old host, plan the move for it too.

5. Test forms, checkout and login on the new host.

6. Check your SSL certificate, the padlock in the browser, on the new host.

7. Watch your search traffic for the next few weeks. A drop may point to broken links or downtime.

Your next step

Today, open PageSpeed Insights and GTmetrix, test your home page and one inner page, and write down TTFB, LCP and page size in a note. Do it again tomorrow evening and on the weekend. If the server response is slow on all three days, ask two hosts for a trial. If it is fast, fix images and plugins first. Don't pay for a new host until your own numbers say you should.

FAQ

What is time to first byte?

It is how long the server takes to start answering. It is the best number for judging the host itself.

How many speed tests should I run?

Test on at least three different days, three runs each, and use the middle result.

Can a CDN fix a slow site without changing hosts?

It can help visitors far from your server, since files load from a nearby copy. It will not fix heavy images or too many plugins.