Direct answer
Improve your WordPress website speed by measuring first, then fixing things in this order: hosting and PHP, page caching, images, plugins and scripts. Test with PageSpeed Insights, aim for the three Core Web Vitals targets, and change one thing at a time so you know what worked. Most small sites need only two or three real fixes, not twenty.
Why does website speed matter for SEO?
Speed is not a vanity metric. Google’s own research shows that as page load time increases from 1 second to 3 seconds, the probability of bounce increases by 32 percent. Push that to 5 seconds, and the bounce probability jumps to 90 percent, per wppoland.com. A one-second delay in page load time reduces conversions by 7 percent, increases bounce rate by 11 percent, and decreases page views by 11 percent, per seoatlantic.com. Just a 100-millisecond lag in load time can drop your conversion rate by 7 percent, per thrivethemes.com. If your site takes longer than three seconds to appear, Google tells us mobile users are 32 percent more likely to bounce before they even see your headline, per thrivethemes.com.
Speed also feeds into Google’s page experience signals through Core Web Vitals, so a slow site can hold back your search visibility, although speed alone will not outrank better content, per effektivweb.com. Core Web Vitals became a confirmed Google ranking signal in 2021, per wppoland.com. Sites that pass all three thresholds, LCP under 2.5 seconds, CLS below 0.1, and INP under 200 ms, get the benefit of that signal in mobile search results, per wppoland.com. Core Web Vitals are not the primary SEO driver. Google says so itself: they are tie-breakers, not the main ranking factor, per schoolswp.com. That means speed will not save weak content, but it will stop good content from losing visitors it should have kept.
The good news is that a slow WordPress site usually has two or three real causes, not twenty, per effektivweb.com. Start by testing with real-visitor data, not just a lab score. Then fix the server, the hero image and the scripts that stall clicks, in that order, and leave the small tweaks for last, per effektivweb.com.
How do you measure your site speed first?
Never start optimizing without a baseline. You need data, not guesses, per wppoland.com. Run your homepage and one key page through Google’s PageSpeed Insights, then open the Core Web Vitals report in Google Search Console, per effektivweb.com. PageSpeed Insights shows a simulated lab result and, when Google has enough data, results from real visitors, per effektivweb.com.
PageSpeed Insights gives you both lab data (Lighthouse) and field data (CrUX), per wppoland.com. Field data comes from real Chrome users visiting your site over the past 28 days, from the Chrome User Experience Report, per nayandhumal.com. This is what Google uses for Core Web Vitals. Lab data comes from a simulated test run on demand, like a Lighthouse test, per nayandhumal.com. Check mobile results first, per nayandhumal.com, because most of your visitors are on phones.
Google judges Core Web Vitals on field data at the 75th percentile, which means at least three in four visits need to be good, per effektivweb.com. The three targets are: Largest Contentful Paint (LCP) within 2.5 seconds, Interaction to Next Paint (INP) within 200 milliseconds, and Cumulative Layout Shift (CLS) under 0.1, per effektivweb.com. INP replaced First Input Delay on 12 March 2024, so any guide still treating FID as a Core Web Vital is out of date, per effektivweb.com.
Record your baselines before you change anything: TTFB, LCP, CLS, INP, total page weight, number of requests, per wppoland.com. Write them down. After each fix, test again and compare. That is how you know what worked, instead of guessing.
| Metric | What it measures | Good target | Poor |
|---|---|---|---|
| LCP | How fast the main content appears | 2.5 seconds or less | Over 4 seconds |
| INP | How quickly the page responds to clicks and taps | 200 milliseconds or less | Over 500 milliseconds |
| CLS | How much the page jumps around as it loads | Under 0.1 | Over 0.25 |
Only 43 percent of WordPress origins pass all three Core Web Vitals on mobile, according to Chrome User Experience Report data from late 2025, per wppoland.com. In August 2026, 48.7 percent of WordPress sites passed all three on mobile, according to the HTTP Archive’s Core Web Vitals Technology Report, per sisudigital.fi. You do not need to be perfect. You need to be in the half that passes, and the fixes below will get most small sites there.
Fix 1: Hosting and PHP
If your server responds slowly, no frontend trick can compensate, per wppoland.com. Time to First Byte (TTFB) should be under 200 ms for cached pages and under 600 ms for dynamic responses, per wppoland.com. Cheap shared hosting is the most common root cause of slow WordPress sites, per netnav.io. You cannot cache your way out of bad hosting. If your server takes a second to respond before sending a single byte, no plugin will save you, per creativeground.com.au.
Check your PHP version first. Tools, then Site Health, in WordPress shows it, per netnav.io. WordPress.org recommends PHP 8.3 or greater, plus MySQL 8.0 or greater or MariaDB 10.11 or greater, per wppoland.com. Use a version that is still supported. Newer versions are usually faster as well as more secure, per netnav.io. This site runs PHP 8.5, which is current, so the PHP fix is already done here. If your host still runs PHP 7.4, ask them to update it. That one change can be the biggest single speed gain on an old site.
If the server is slow on every page even with caching, consider better hosting, per netnav.io. Managed WordPress hosting typically includes server caching and a CDN, per netnav.io. You do not need the most expensive plan. You need a host whose server is near your visitors and whose resources are not shared with hundreds of other sites.
Fix 2: Turn on page caching
Caching is the single highest-impact change you can make on an already-running site, per cynet.com.my. Caching stores pre-built versions of your pages so the server does not have to rebuild them for every visitor, per seoatlantic.com. Proper caching can reduce page load times by 60 to 80 percent, per seoatlantic.com. Without caching, WordPress builds every page from scratch for every visitor: it runs PHP, queries the database, and assembles the HTML, per mobilizecloud.com.
Page caching saves the finished HTML of each page, so the next visitor gets it instantly instead of WordPress rebuilding it with PHP and database queries, per blog.hostlelo.com. This is the big win, and the part that needs a LiteSpeed server or QUIC.cloud, per blog.hostlelo.com. On LiteSpeed servers, LiteSpeed Cache is free and hard to beat, per creativeground.com.au. On Apache or Nginx, WP Rocket remains the best all-rounder in 2026, per creativeground.com.au.
Pick one caching plugin only. Running two creates conflicts that make sites slower, per creativeground.com.au. This site runs LiteSpeed Cache on a LiteSpeed server, which is why its pages load from cache. If your site runs on LiteSpeed hosting, use LiteSpeed Cache and keep its settings moderate: switch the cache on, prove it works by looking for the cache hit header, apply a moderate preset, and add image and code optimisations one at a time, testing after each, per blog.hostlelo.com. Do not pick the most aggressive preset on day one. One wrong setting can break a menu or empty a cart, and you will not know which setting caused it.
Fix 3: Fix your images
Images are typically the largest assets on any WordPress page, accounting for 50 to 80 percent of total page weight, per seoatlantic.com. Images are usually 60 to 80 percent of a page’s total size. Compressing them is the biggest single optimisation most sites need, per cynet.com.my. A 4,000-pixel photo squeezed into a 600-pixel slot still downloads in full, per effektivweb.com.
| Image fix | What to do | Why it helps |
|---|---|---|
| Resize before uploading | Upload at the size the image displays at, never wider | A 6,000-pixel photo straight from a camera is a common cause of slow pages, per netnav.io |
| Compress | Use lossy compression at 80 to 85 percent quality | The visual difference is imperceptible, but the file size reduction is dramatic, per seoatlantic.com |
| Convert to WebP | Use WebP or AVIF instead of JPEG or PNG | These modern formats are 25 to 50 percent smaller than JPEG or PNG at equivalent quality, per seoatlantic.com |
| Lazy load below the fold | Let WordPress lazy load images further down the page | WordPress 5.5 and later includes native lazy loading for images, per seoatlantic.com |
| Never lazy load the hero | Give the main image priority instead | Never lazy-load the main image at the top of the page, per sisudigital.fi |
Resize images to display dimensions. Never upload a 4000-pixel image when it displays at 800 pixels, per seoatlantic.com. Compress before uploading using TinyPNG or Squoosh, per cynet.com.my. Convert to WebP format, which is 30 to 50 percent smaller than JPEG at the same quality, per cynet.com.my. And never lazy-load the LCP image. Give it fetchpriority=”high” instead, per sisudigital.fi. The hero image is the largest content on the page, so delaying it delays the whole page.
For the full image guide, including alt text and how to choose the right size, read our guide on how to optimise images for SEO on WordPress. It covers the same fixes from the search side, and the two guides work together.
Fix 4: Audit your plugins
A WordPress site with 30 plugins loads slower than one with 8, regardless of how good the hosting is, per cynet.com.my. The number of plugins matters less than what they do. One badly written plugin can slow a site more than ten light ones, and a plugin you stopped using months ago still loads its code if it is switched on, per effektivweb.com. One poorly built plugin that loads scripts on every page or runs heavy database queries can slow a site more than twenty light ones, per mobilizecloud.com.
List every plugin and note what it is for. Deactivate and delete anything nobody can explain, per mobilizecloud.com. Deactivate and delete anything you no longer use. Unused plugins are also a security risk, per netnav.io. Use a diagnostic plugin like Query Monitor on a staging site to see which plugins add the most database queries and load time, per mobilizecloud.com. Query Monitor shows which plugins are slowing your pages so you are cutting based on data, not guesswork, per creativeground.com.au.
Do not pile on speed plugins to fix a plugin problem. A site with fifteen speed plugins is slower than a site with none, because each one loads its own code. One caching plugin, one image optimisation plugin, and the plugins your site actually needs. That is the whole list.
Fix 5: Tame the theme, scripts and database
Third-party scripts, such as chat widgets, ad pixels and tag managers, often cost more than anything on your own server, per netnav.io. Every plugin and script has a cost. Remove what you do not use and delay what is not essential, per netnav.io. Delay or defer non-essential JavaScript, per nayandhumal.com. A chat widget that loads on every page, a social feed embedded in the footer, and a video player that auto-loads will each add a second or more to your load time. Ask whether each one earns its place on every page, or whether it belongs on one page only.
Use a lightweight theme and avoid heavy page builders for posts, per nayandhumal.com. A theme that loads dozens of CSS and JavaScript files on every page will slow every page, whatever else you do. If your theme is heavy, switching to a light one is the single biggest speed gain available, bigger than any plugin. This site runs the Blogus theme, which is light enough for a blog, so no theme change is needed here.
Clean the database once a month. Old post revisions, spam comments, expired transients and trashed items pile up, and WordPress queries them on every page load. LiteSpeed Cache has a database cleanup tool built in. Run it, then test. Do not install a separate database plugin for a job your caching plugin already does.
What order should you fix things in?
Fix the server first and the page second. Time to First Byte comes before every other loading metric, so no image or script fix can make up for a slow server, per sisudigital.fi. Measure first, then fix things in this order: hosting and PHP version, page and object caching, a CDN, images, fonts, JavaScript and plugins, and the database, per sisudigital.fi.
| Step | Fix | Time | Impact |
|---|---|---|---|
| 1 | Measure with PageSpeed Insights and Search Console | 15 minutes | Tells you what to fix |
| 2 | Update PHP and check hosting | 30 minutes | High, fixes TTFB |
| 3 | Set up page caching with one plugin | 1 hour | High, cuts load time 40 to 60 percent |
| 4 | Resize, compress and convert images to WebP | 1 hour | High, biggest single page weight cut |
| 5 | Remove unused plugins and delay scripts | 30 minutes | Medium, fixes INP |
| 6 | Clean the database | 15 minutes | Low to medium |
The fastest path is: move to quality hosting, enable page caching with a single caching plugin, convert images to WebP and resize them before upload, then remove unused plugins, per creativeground.com.au. Change one thing at a time and test after each change, per blog.hostlelo.com. If you change five things at once and the site gets faster, you will not know which one did it. If it gets slower, you will not know which one broke it.
For the metric-by-metric version of this work, read our guide on how to improve Core Web Vitals on WordPress. It covers LCP, INP and CLS one at a time, with the specific fix for each. This guide covers the order to fix things in. Together, they cover the whole job. And because most of your visitors are on phones, read our guide on why having a mobile website is critical for SEO, which explains why mobile speed matters more than desktop speed.
Frequently asked questions
How fast should my WordPress site be?
Aim for the three Core Web Vitals targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint within 200 milliseconds, and Cumulative Layout Shift under 0.1, per effektivweb.com. Google judges them on field data at the 75th percentile, which means at least three in four visits need to be good, per effektivweb.com.
What is the single biggest speed fix for WordPress?
Page caching. Proper caching can reduce page load times by 60 to 80 percent, per seoatlantic.com. On LiteSpeed servers, LiteSpeed Cache is free and hard to beat, per creativeground.com.au. Pick one caching plugin only, because running two creates conflicts, per creativeground.com.au.
Do I need a new host to make my site faster?
Not always. If the server is slow on every page even with caching, consider better hosting, per netnav.io. Cheap shared hosting is the most common root cause of slow WordPress sites, per netnav.io. But check PHP, caching and images first, because those fixes are free and they solve most slow sites.
Why are my images slowing the site down?
Because they are the heaviest part of the page. Images are typically the largest assets on any WordPress page, accounting for 50 to 80 percent of total page weight, per seoatlantic.com. Resize before uploading, compress at 80 to 85 percent quality, and convert to WebP, per seoatlantic.com.
How many plugins is too many?
The number matters less than what they do, per effektivweb.com. A WordPress site with 30 plugins loads slower than one with 8, regardless of how good the hosting is, per cynet.com.my. List every plugin, delete anything nobody can explain, and use Query Monitor to find the slow ones, per mobilizecloud.com.
How do I check my site speed?
Run your homepage and one key page through Google’s PageSpeed Insights, then open the Core Web Vitals report in Google Search Console, per effektivweb.com. PageSpeed Insights shows a simulated lab result and, when Google has enough data, results from real visitors, per effektivweb.com. Good internal linking for SEO also helps speed indirectly, because a clear structure means fewer wasted crawls and faster discovery of your pages.
Conclusion
Improving WordPress website speed is a job in the right order, not a pile of plugins. Measure first with PageSpeed Insights, so you fix the actual bottleneck, per netnav.io. Then fix hosting and PHP, turn on page caching with one plugin, resize and compress your images, delete the plugins you do not use, and delay the scripts that are not essential. Test after each change and write down the numbers, so you know what worked. Most small sites need only two or three real fixes, and those fixes will move the site into the half of WordPress sites that pass all three Core Web Vitals on mobile. That is the whole job, and it is worth doing before you spend money on anything else.

