25% discount on all new client orders. Talk to us
Sitefitters
Contact us Find a Fit
Learn / How-To Guides

How to Speed Up a Slow WordPress Website

A slow website costs you customers before they read a word. In this guide you will measure your site’s speed, fix the most common causes of slow WordPress pages and confirm the improvement.

Visitors on phones are impatient, and many leave if a page takes more than a few seconds to appear. Google also measures real-world page experience through Core Web Vitals. Most WordPress sites can get noticeably faster with a few practical changes and no rebuild.

⏱ 1 to 2 hours◎ Intermediate☰ 9 steps↻ Updated Oct 2026

What you need

  • WordPress administrator access
  • cPanel or hosting dashboard login
  • A recent backup of your site

Steps

1

Measure your speed first

Go to pagespeed.web.dev, enter your homepage address and run the test. Look at the mobile results first. The top section shows field data from real Chrome users over the past 28 days, when your site has enough traffic. The Core Web Vitals targets are Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1. Write down your results so you can compare later.

Tip: Test a few key pages too, such as a service page or product page, since each page loads differently.
2

Shrink and resize your images

Oversized photos are the most common cause of slow pages. Resize images to the largest size they actually display, often 1,600 to 2,000 pixels wide for a full-width banner, and compress them before uploading. WordPress supports WebP images, and AVIF on servers that allow it. Check Tools, then Site Health, then Info, then Media Handling. WordPress also lazy-loads images further down the page automatically.

3

Turn on page caching

Without caching, WordPress builds every page from scratch for every visitor. A page cache saves a ready-made copy and serves it instantly. Many hosts include server caching, so check your hosting dashboard first. Otherwise, install one caching plugin, such as WP Super Cache, W3 Total Cache or LiteSpeed Cache on LiteSpeed servers. Use the default settings, then test your site carefully.

Tip: Run only one caching plugin, because two can conflict and break your pages.
4

Update your PHP version

PHP is the language WordPress runs on, and newer versions are noticeably faster. WordPress recommends PHP 8.3 or newer. In cPanel, open Software, then MultiPHP Manager, check the box next to your domain, choose a newer version and click Apply. Back up first, then check your site right away. If something breaks, switch back and ask your developer to update the incompatible plugin.

5

Trim plugins and extra scripts

Every plugin, tracking code, chat widget, slider and web font adds weight. Go to Plugins and deactivate anything you no longer use, then delete it. Look for overlap, such as two plugins that both add social buttons or forms. Remove old tracking codes for services you stopped using. Retest after removing a big item so you can see what made a difference.

6

Turn on compression

Compression shrinks text files like HTML, CSS and JavaScript before they travel to the visitor’s browser. Many hosts enable it by default. In cPanel, open Software, then Optimize Website, choose Compress All Content and click Update Settings. PageSpeed Insights will flag it if compression is missing. If you do not see this tool, your host may handle compression another way.

7

Use a content delivery network

A content delivery network, or CDN, stores copies of your images, styles and scripts on servers around the world, so visitors download them from a location near them. This helps most when customers are spread across regions. Many hosts include a CDN, and several providers offer free starter plans. Most CDNs also add protection against traffic floods and attacks.

8

Clean up your database

Over time, the database collects old post revisions, spam comments and leftover data from deleted plugins. Empty the spam and trash folders under Comments, Posts and Pages. A database cleanup plugin can remove old revisions safely. To limit future revisions, a developer can add a WP_POST_REVISIONS setting to wp-config.php. Always back up before cleaning a database.

9

Retest and review your hosting

Run PageSpeed Insights again and compare with your first results. Lab scores update immediately, while real-user field data takes up to 28 days to catch up. If pages still take a long time to start loading even after these fixes, your hosting plan may be the bottleneck. A plan with more resources or server-level caching can make a large difference for busy sites.

Common Mistakes

  • Uploading photos straight from a phone or camera, often several megabytes each, without resizing them.
  • Installing several speed or caching plugins at once, which can conflict and break your layout.
  • Chasing a perfect 100 score on a lab test instead of improving how fast pages feel for real visitors.

FAQ

What is a good PageSpeed Insights score?

In the lab test, a score of 90 to 100 is rated good, 50 to 89 needs improvement and below 50 is poor. The score can vary from run to run. Pay more attention to the Core Web Vitals field data from real visitors, because that reflects what customers actually experience and is what Google uses.

Does website speed affect my Google rankings?

It can, but it is one factor among many. Google says good Core Web Vitals align with what its core ranking systems seek to reward, while helpful, relevant content matters more. A faster site still pays off directly, because visitors are more likely to stay, read and contact you. Think of speed as good customer service that also supports your search visibility.

Why is my mobile score so much lower than desktop?

PageSpeed Insights tests mobile by simulating a mid-range phone on a slower mobile connection, while the desktop test uses a fast wired connection. Large images, heavy scripts and big fonts hurt far more on that phone. Since most local searches happen on phones, focus on improving the mobile results first.