---
title: "How to Speed Up a WordPress Site (2026 Guide)"
description: "Speed up a WordPress site in order: measure, cache, fix images, drop unused CSS and scripts, delay widgets and check the server. With our real numbers."
source: https://wpos.ai/blog/how-to-speed-up-a-wordpress-site/
updated: 2026-11-07
---

[Black Friday](https://wpos.ai/black-friday/): 15,000 free credits + 50% off ends Nov 30

# How to Speed Up a WordPress Site: 6 Fixes, With Real Numbers

Most slow WordPress sites have the same few causes: pages that aren't cached, heavy images, and CSS and scripts that load on every page whether they're used or not. Here is how to find yours and fix them in order, with the numbers from speeding up wpos.ai this month.

- Page speed

- Step by step

- 2026

## The short answer

**Measure first, then fix the biggest cause: usually caching, images, or files that load on every page.** In order:

- Test a few key pages in PageSpeed Insights and note what slows each one.
- Make sure pages are cached, for long enough.
- Compress images, serve WebP, and don't lazy-load the main image.
- Stop CSS and scripts loading on pages that don't use them.
- Load chat widgets, video players and trackers after the page appears.
- Host your fonts, reserve space for anything that loads late, and check the server.

The examples come from our own site, wpos.ai, measured between 3 and 6 November 2026. Plugin details were checked in the WordPress.org directory on 7 November 2026.

## Measure before you change anything

Test your home page and two or three of your busiest pages in [PageSpeed Insights](https://pagespeed.web.dev/), on mobile. The top section shows real visitors' data from Chrome when your site has enough traffic; the lab test below it shows what slows the page in a single load.

Google's Core Web Vitals are passed when, for 75% of visits:

- **Largest Contentful Paint (LCP)**, when the main content appears, is 2.5 seconds or less;
- **Interaction to Next Paint (INP)**, how quickly the page responds to a tap or click, is 200 milliseconds or less;
- **Cumulative Layout Shift (CLS)**, how much the page jumps while it loads, is 0.1 or less.

Search Console's Core Web Vitals report shows the same for the whole site. Write the numbers down, so you can tell what each fix did.

## 1. Cache pages, for long enough

Without a page cache, WordPress builds every page from scratch for every visitor. Managed WordPress hosts usually cache pages for you; otherwise a caching plugin does it. On 7 November 2026, [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/) (1,000,000+ active installs), [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/) (900,000+) and, for LiteSpeed servers, [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/) (7,000,000+) were all tested with the current WordPress release.

Then check two things: how long pages stay cached, and that the cache is cleared when you edit a page. **On wpos.ai,** pages were cached for only 10 minutes. From our analytics we estimated that only 43% of real page views in the 30 days to 3 November found a cached page; everyone else waited for the server. We now cache pages for a day and blog posts for a week, clear the cache after every site-wide change, and reload the top pages straight after, so the first visitor doesn't wait. The same data says about 9 in 10 page views should now be cached.

## 2. Fix your images

- Resize images to the largest size they're shown at; a 4,000-pixel photo in a 600-pixel slot wastes most of its weight.
- Serve WebP, which WordPress has supported since version 5.8, or AVIF, supported since 6.5. Plugins such as [EWWW Image Optimizer](https://wordpress.org/plugins/ewww-image-optimizer/) or [Imagify](https://wordpress.org/plugins/imagify/) can convert the images you already have; the WordPress performance team's [Modern Image Formats](https://wordpress.org/plugins/webp-uploads/) converts new uploads.
- Let WordPress lazy-load the images further down the page. It adds `loading="lazy"` by itself, and since version 6.3 it skips the likely main image and gives it `fetchpriority="high"` instead.
- **Don't let other code undo that.** On wpos.ai, an old speed tweak of our own added `loading="lazy"` to every image without a loading attribute, including the homepage video poster that WordPress had marked high priority. We now mark the main images `loading="eager"`. Search your theme, plugins and snippets for `loading="lazy"` if PageSpeed Insights flags a lazy-loaded main image.

## 3. Stop loading CSS and scripts everywhere

Themes, page builders and plugins often load their files on every page, whether that page uses them or not. PageSpeed Insights flags them as unused CSS and JavaScript, and as render-blocking requests. Remove the plugins you don't need, then stop the rest loading where they aren't used, with a plugin such as [Asset CleanUp](https://wordpress.org/plugins/wp-asset-clean-up/) or a few lines of code that dequeue them.

**On wpos.ai** we found two stylesheets loading on every page: a 261 KB utility stylesheet and a 23 KB one for wireframes. Not one of the utility file's 5,526 classes was used in any of our 118 widgets or 203 pages and posts. Switching both off removed about 284 KB of render-blocking CSS from every page (about 43 KB over the network, compressed), and before-and-after screenshots of the home and pricing pages, on desktop and phone, were pixel-identical. Always compare screenshots before you trust a fix like this.

## 4. Load chat widgets, video players and trackers later

Third-party scripts such as analytics, chat widgets, booking tools and video players are often the heaviest thing on a page. Load them after the page appears, or on the first click, and wait for consent where your cookie banner asks for it. We now start our own analytics after the page first appears, and load only the parts we use.

Video players are also a common cause of layout shift. **On wpos.ai** the homepage video player shifted the page as it loaded, for a desktop CLS of 0.29 in our tests. Replacing it with a click-to-load preview, a correctly sized poster image that loads the player only when someone clicks it, brought that to 0.002.

## 5. Fonts, animations and layout shift

- Host your fonts on your own domain instead of loading them from a font service, and load only the weights you use. In block themes, WordPress's Font Library (Styles → Typography in the Site Editor) installs Google Fonts on your own site.
- Use `font-display: swap` so text shows straight away, and pick fallback fonts of a similar size so the swap doesn't move the layout.
- Give images, embeds and ads a width and height, or a fixed aspect ratio, so their space is reserved before they load.
- **Don't animate the main headline in.** On wpos.ai, a word-by-word reveal effect kept hero headlines hidden for 2 to 5.5 seconds after the page loaded, which also delays the moment the main content counts as shown. Headlines on the first screen now appear at once, and the effect only runs further down the page.

## 6. Check the server

- Time a page the cache hasn't stored yet: add a new query string to the address, such as `?test=123`, and check the time to first byte in your browser's developer tools (Network tab). PageSpeed Insights flags a slow server response too.
- Run a current PHP version; Tools → Site Health → Info → Server shows which one you're on.
- A persistent object cache such as Redis or Memcached helps busy and logged-in pages, but only if it works. **On wpos.ai,** a plugin kept trying to connect to a Redis server our host doesn't run, and waited out three one-second timeouts on every uncached page. Once it was fixed, uncached pages went from about 3.3 seconds to 0.4 to 0.6.
- To find a slow plugin, [Query Monitor](https://wordpress.org/plugins/query-monitor/) shows slow database queries and which plugin made them; or deactivate plugins one at a time on a staging copy.

## What it added up to on wpos.ai

| Change | Before | After |
| --- | --- | --- |
| How long pages stay cached | 10 minutes: about 43% of real page views found a cached page (estimate) | 1 day for pages, 7 days for posts: about 9 in 10 (estimate) |
| Building an uncached page | About 3.3 seconds | 0.4 to 0.6 seconds |
| Homepage layout shift (desktop CLS) | 0.29 | 0.002 |
| Unused CSS on every page | 284 KB, render-blocking | Removed, with no visible change |
| Hero headline visible | 2 to 5.5 seconds after load | At once |

In a lab test on a fast connection on 6 November, the main content of our home page, pricing page, a blog post and a case study appeared within 0.6 to 1.2 seconds, on desktop and phone. Real-visitor numbers move more slowly: in October, 75% of visits saw the main content within 4.1 seconds; in the week to 6 November, desktop visits were at 2.5 to 3.0 seconds, from a small sample. We will keep measuring.

## Where WPOS fits

**Speed work is a good job to hand WPOS.** Its agent works inside wp-admin on the sites you already run, on any host. It can test pages in a real browser, find files that load everywhere, convert and resize images, switch off what isn't used, and compare before-and-after screenshots before it reports done. The problems above were found by the WPOS agent working on this site, and it made most of the fixes itself. A prompt to start with:

> “Find what makes our home and pricing pages slow on mobile, fix the biggest causes without changing how the pages look, and show me the before-and-after numbers and screenshots.”

WPOS is our product, so weigh this section accordingly; you can [try it free for 30 days](https://app.wpos.ai/signup?ref_page=how-to-speed-up-a-wordpress-site&ref_cta=body-cta) with 5,000 credits, a live site plus a staging sandbox, and no card.

## Frequently Asked Questions

**Why is my WordPress site so slow?**

Usually one of a few things: pages that aren't cached, large images, CSS and scripts that load on every page, third-party widgets, or a slow server or plugin. PageSpeed Insights shows which of these applies to each page.

**What is a good page speed for WordPress?**

Aim to pass Google's Core Web Vitals rather than chase a score: the main content within 2.5 seconds, responses to taps and clicks within 200 milliseconds, and a layout shift of 0.1 or less, for 75% of visits.

**Do I need a caching plugin?**

Not if your host already caches pages, as most managed WordPress hosts do; two page caches can conflict. Otherwise WP Super Cache, W3 Total Cache or, on LiteSpeed servers, LiteSpeed Cache will do it.

**Do too many plugins slow WordPress down?**

What each plugin loads matters more than how many you have. One plugin that adds scripts to every page can cost more than ten that don't. Test by deactivating them one at a time on a staging copy.

**Should I lazy-load all images?**

No. Lazy-load the images further down the page, but load the main image at the top straight away. WordPress does this by itself since version 6.3, unless a theme or plugin overrides it.

**How do I speed up WordPress without a plugin?**

Use your host's page cache, resize and compress images before you upload them, remove plugins you don't need, and run a current PHP version. Stopping unused files from loading takes a few lines of code in a child theme or a code snippet.

**Black Friday**ends Nov 30

## Start free with 15,000 credits.

Three times the usual 5,000, no card needed. Then 50% off your site licences for 2 months with FRIDAY50.

## Let an agent find what slows your sites down.

WPOS puts an AI agent inside wp-admin on the sites you already run, on any host, and it checks its own work. Free for 30 days: 5,000 credits, a live site plus a sandbox, no card.

[Claim 15,000 credits](https://app.wpos.ai/signup?ref_page=how-to-speed-up-a-wordpress-site&ref_cta=prefooter-cta): Start free
