Skip to content
Your Tech Read
Your Tech Read
Web & Cloud Hosting

How to Speed Up a Slow WordPress Site Before You Upgrade Hosting

In this article 7 sections
  1. Why your hosting may not be the problem
  2. Step 1: Measure before you fix anything
  3. The fixes, in order of impact
  4. Quick checklist
  5. When it really is time to upgrade hosting
  6. FAQ
  7. Final word

Why your hosting may not be the problem

Most slow WordPress sites are slow because of what runs on them, not where they are hosted. Heavy images, no caching, too many plugins and a bloated theme can make even an expensive server feel sluggish.

That is good news. The fixes in this guide are free or cheap, and most take an afternoon. Do them first, and one of two things will happen:

  • Your site becomes fast enough, and you save the cost of a bigger plan.
  • Your site is still slow after fixing the basics. Now you know hosting really is the bottleneck, and an upgrade will actually help.

Either way, you stop guessing. Upgrading hosting without fixing these problems is like buying a faster car and leaving the handbrake on.

Before you change anything, take a full backup of your site. If something breaks, you can restore it in minutes.

Step 1: Measure before you fix anything

You can’t improve what you don’t measure. Test your site first, so you know where the problem is and can see what each fix changes.

  1. Go to PageSpeed Insights (pagespeed.web.dev) and enter your homepage URL.
  2. Test your most important page too, such as a popular blog post or product page.
  3. Look at the mobile results first. That is what Google mainly uses, and it is usually the slower one.
  4. Write down your scores, so you can compare them after each fix.

Focus on Google’s three Core Web Vitals. According to web.dev, these are the “good” targets:

Metric What it measures Good target
Largest Contentful Paint (LCP) How fast the main content appears 2.5 seconds or less
Interaction to Next Paint (INP) How quickly the page responds when someone taps or clicks 200 milliseconds or less
Cumulative Layout Shift (CLS) How much the page jumps around while loading 0.1 or less

Also note the server response time (shown as “Time to First Byte” or “Reduce initial server response time”). If that alone is slow, even on a simple page, hosting may be part of the problem. If it is fast but the page still loads slowly, the problem is almost certainly on your site.

The fixes, in order of impact

Work through these from top to bottom. The first three alone fix most slow WordPress sites. Re-test with PageSpeed Insights after each change.

1. Turn on page caching

Without caching, WordPress rebuilds every page from scratch for every visitor, running PHP and database queries each time. A cache saves a ready-made copy of each page and serves that instead, which is far faster.

  • If your host uses LiteSpeed servers (Hostinger and many others do), install the free LiteSpeed Cache It works at server level and is very effective.
  • If your host has its own caching (SiteGround, Kinsta, WP Engine and similar), turn on their built-in tool rather than adding another plugin.
  • Otherwise, use a well-known caching plugin such as WP Super Cache or W3 Total Cache, or a paid option like WP Rocket.

Use only one caching plugin. Two caching plugins fighting each other can make your site slower or break it.

2. Shrink and modernise your images

Images are usually the biggest part of a page. A single 4 MB photo straight from a phone or camera can slow a page more than everything else combined.

  • Resize before uploading. A featured image rarely needs to be wider than about 1200–1600 pixels.
  • Use WebP instead of large JPGs or PNGs. WebP files are much smaller at the same quality.
  • Compress automatically with a plugin such as ShortPixel, Imagify or the image optimisation built into LiteSpeed Cache, which can also convert existing images to WebP.
  • Make sure lazy loading is on, so images further down the page only load when the reader scrolls to them. WordPress does this by default for most images.

3. Remove plugins you don’t need

Every active plugin can add code, database queries, scripts and styles to your pages. Many sites run plugins they forgot about.

  • Go to Plugins and deactivate anything you no longer use, then delete it.
  • Watch for heavy plugins that load on every page: sliders, social share widgets, page builders on pages that don’t use them, related-post plugins and “all-in-one” toolkits.
  • Replace several small plugins with one that does the job well.

A site with 10 well-chosen plugins is usually faster than one with 40 random ones. Fewer plugins also means fewer security risks.

4. Use a lightweight theme

Some multipurpose themes and page builders load large amounts of CSS and JavaScript on every page, even when you use a fraction of their features. If your theme is heavy, consider switching to a lightweight one, such as a modern block theme or a lean theme like GeneratePress, Kadence or Astra.

Test a theme change on a staging copy first, since it can change your layout.

5. Update PHP and WordPress

Newer versions of PHP run WordPress noticeably faster and more securely. WordPress.org recommends PHP 8.3 or greater. You can usually change the PHP version in a couple of clicks in your hosting control panel.

Update WordPress, your theme and plugins first, take a backup, then switch PHP and check that your site still works.

6. Clean up your database

Over time, your database fills with post revisions, spam comments, expired temporary data (transients) and leftovers from deleted plugins. A cleanup can make queries faster, especially on older sites.

Many caching plugins, including LiteSpeed Cache, include a database cleanup tool. Back up first, then remove revisions, spam and trashed items, and expired transients.

7. Use a CDN

A content delivery network (CDN) stores copies of your images, CSS and JavaScript on servers around the world, so visitors download them from somewhere nearby. If your readers are spread across countries, a CDN can make a big difference.

Cloudflare has a free plan, and many hosts include a CDN or offer one in a click.

8. Cut heavy scripts and embeds

Third-party code is a common hidden cause of slow pages and poor INP scores.

  • Remove tracking scripts and pixels you don’t actually use.
  • Load chat widgets, videos and social feeds only where they are needed, not on every page.
  • Replace embedded YouTube videos with a lightweight “click to play” version.
  • Limit custom web fonts to one or two families, and host them locally if you can.

Quick checklist

Use this as a one-page summary. Start at the top: these give the biggest gains for the least effort.

Fix Effort Impact Cost
Turn on page caching Low High Free
Resize, compress and convert images to WebP Low High Free to low
Remove unused plugins Low Medium to high Free
Update PHP to 8.3+ Low Medium Free
Clean up the database Low Low to medium Free
Add a CDN Low Medium (high for global readers) Free to low
Cut heavy scripts and embeds Medium Medium Free
Switch to a lightweight theme High High Free to low

Re-run PageSpeed Insights after each fix, and compare against the scores you wrote down at the start.

When it really is time to upgrade hosting

If you have worked through the fixes and your site is still slow, hosting may truly be the limit. These are the signs:

  • Slow server response even with caching on. Time to First Byte stays high on simple, cached pages.
  • Slowdowns at busy times. The site is fine at night but crawls when traffic peaks.
  • Resource limit warnings. Your host emails you about CPU, memory or “entry process” limits, or your control panel shows you hitting them.
  • Errors under load, such as “503 Service Unavailable” or “508 Resource Limit Reached”.
  • Dynamic pages are slow. Online stores, membership sites and forums can’t be fully cached, so they need more server power.

If these match, upgrading makes sense. Usually the next step is a higher shared plan, cloud hosting or a VPS. To compare your options, read shared hosting vs VPS: when should you upgrade?, managed vs unmanaged VPS and Hostinger vs SiteGround.

The fixes in this guide still pay off after you move. A well-optimised site on better hosting will be faster than either change on its own.

Related guides: WordPress Troubleshooting: How to Fix the Most Common Errors

Want to go further? These guides help you measure and protect your site:

FAQ

Why is my WordPress site suddenly slow?

The usual causes are a new or recently updated plugin, a large image upload, a traffic spike, or a problem on your host’s side. First, check whether you changed anything recently. Then run a PageSpeed test and compare it with your last result.

Which caching plugin is best for WordPress?

The best one is the one that matches your server. If your host runs LiteSpeed, use LiteSpeed Cache. If your host has built-in caching, use that. Otherwise, WP Super Cache (free) or WP Rocket (paid) are reliable choices. Use only one caching plugin.

Do too many plugins slow down WordPress?

It depends more on which plugins than on how many. One badly built plugin can slow a site more than ten lightweight ones. Remove anything you don’t use, and test heavy plugins one at a time.

What is a good PageSpeed score?

Aim for 90 or higher on mobile, but don’t obsess over the number. Passing Core Web Vitals and a site that feels fast to real visitors matter more than a perfect 100.

Will a CDN fix a slow WordPress site?

A CDN helps visitors far from your server and takes load off your hosting. It won’t fix heavy pages, an overloaded server or too many plugins, so do those fixes first.

How much does it cost to speed up WordPress?

Often nothing. Caching, image compression, plugin cleanup, a PHP update and Cloudflare’s free plan all have free options. Paid tools like WP Rocket or premium image optimisers save time, but they’re optional.

Final word

A slow WordPress site is rarely just a hosting problem. Measure first. Then turn on caching, compress your images and remove plugins you don’t need. Those three fixes alone solve most speed problems, and they cost little or nothing.

If you’ve done the work and the server is still the bottleneck, upgrade with confidence. You’ll know you are paying for real extra power, not covering up problems a plugin or an image resize could have fixed.

Leave a comment

Your email address will not be published. Required fields are marked *