Opens in a new tab

How to Speed Up WordPress: A 12-Step Checklist for 2026

WordPress
Alex Arce
on
October 17, 2026

Last reviewed November 2026.

Short answer

To speed up WordPress, test first, then fix in order: back up, update everything, move to PHP 8.3 or newer, check your hosting, turn on one page cache, shrink your photos, remove unused plugins and scripts, add a CDN, and clean the database. Aim for LCP of 2.5 seconds or less. Test again after each step.

A slow site can cost you visitors before they read a word. The fix is rarely one magic plugin. It is a short list of causes, and you can find yours with a simple test.

This guide is part of our website maintenance guide for small business.

This guide explains what “fast” means, how to test without being fooled, and 12 steps in a safe order. It also shows what you can do today and what to hand off.

In this guide

What fast means in 2026

Google measures how a page feels to real people with three numbers called Core Web Vitals. Per Google’s Core Web Vitals guide on web.dev, these are the “good” targets:

MetricWhat it measures in plain wordsGood
Largest Contentful Paint (LCP)How fast the biggest thing on screen shows up, often your hero photo or headline2.5 seconds or less
Interaction to Next Paint (INP)How fast the page reacts when someone taps a button or opens a menu200 milliseconds or less
Cumulative Layout Shift (CLS)How much the page jumps around while it loads0.1 or less

Two details matter. First, Google suggests measuring at the 75th percentile of page loads, split by mobile and desktop. That means a good result has to hold for most visitors, not only people on fast wifi. Second, INP is newer. Google says it became a stable Core Web Vital in 2024, so a guide that still talks about “FID” is out of date.

Does speed help you in Google? Google says it highly recommends good Core Web Vitals for success with Search. It does not promise that a good score will lift your rankings. Treat speed as part of a good site, and fix it mainly so visitors stay and call.

One more term: TTFB, or Time to First Byte, is how long your server takes to start answering. Google says most sites should aim for 0.8 seconds or less. It is not a Core Web Vital, but a slow server makes a good LCP very hard to reach.

How to test your WordPress speed

Before you change anything, write down where you start. Without a baseline you cannot tell which fix helped.

Lab data and field data are different

A PageSpeed Insights report shows two kinds of results, as Google’s PageSpeed Insights documentation explains:

  • Lab data is one test in a controlled setting. Google says it is useful for debugging issues. It gives the 0 to 100 Performance score: 90 or above is good, 50 to 89 needs improvement, and below 50 is poor.
  • Field data comes from real users over the previous 28-day collection period. Google says it is useful for capturing real-world user experience.

If your page has too little traffic, PageSpeed Insights falls back to data for the whole site. If that is thin too, it may show no real-user data at all. That is normal for a small site. Use lab data to find problems, and check on a real phone.

Lab scores also move from run to run. Run each test three times and use the middle result. Do not worry about a few points.

A 6-step baseline

  1. Pick three pages: your home page, your top service page and one gallery or blog page.
  2. Run each one through PageSpeed Insights and open the mobile tab first.
  3. Write down LCP, INP (if field data exists), CLS and the Performance score.
  4. Note the top items under “Diagnose performance issues.” They show where the time goes.
  5. In WordPress, open Tools > Site Health. It flags an old PHP version and plugins that need updates.
  6. Open the site on your own phone using mobile data, not office wifi. Tap the menu and the call button. Does anything lag or jump?

Want a quick outside look first? Our free Website Teardown includes a mobile speed reading. It is a quick screen, not a full audit, but it shows whether speed is a real problem before you spend an afternoon on it.

Why WordPress sites get slow

Match what you see in your test to the likely cause. Start with the first fix in that row before you try anything fancy.

What you seeLikely causeFirst fixWho usually handles it
Long wait before anything shows (high TTFB)Slow or crowded hosting, old PHP, no page cacheTurn on page caching, then check PHP version and hostingHost or developer
Poor LCP and “properly size images” warningsHuge photos, or a hero image that is lazy-loadedResize photos, use WebP or AVIF, never lazy-load the heroOwner with an image plugin, or developer
Poor INP, menus and buttons feel stickyHeavy JavaScript from plugins, builders, chat widgets and trackersRemove scripts you do not need, delay the restDeveloper
Poor CLS, text jumps while loadingImages, embeds or banners with no set sizeSet width and height, reserve space for bannersDeveloper
Admin area slow, site slows over timeBloated database, large autoloaded options, many revisionsBack up, then clean up and cap revisionsDeveloper or maintenance plan
Fast for you, slow far awayNo CDN, server far from visitorsAdd a CDNOwner or host

Notice that the table points to a different first fix for each symptom. That is why a test comes before a plugin. A cache will not shrink a 4 MB photo, and a photo tool will not fix a slow server.

The 12-step checklist

Work in this order. The early steps are safe and cheap. Test after each step so you know what helped.

1. Record a baseline and take a full backup

Save your test numbers. Then back up. WordPress.org says there are two parts to a backup, the database and the files, and you need both to fully restore a typical site. It advises backing up always before an upgrade. Confirm you can download the backup.

2. Update WordPress, your theme and your plugins

Updates carry security patches and can carry speed fixes. Use a staging copy first if your host offers one. On a busy site, update plugins one at a time and check the site after each. If you have not logged in for months, this step alone may change your numbers.

3. Move to a supported PHP version

PHP is the language WordPress runs on. The WordPress.org requirements page recommends PHP 8.3 or greater. It says older versions have reached end of life and may expose your site to security vulnerabilities.

Dates matter here. The PHP supported versions page lists security support until December 31, 2026 for PHP 8.2, December 31, 2027 for 8.3, and December 31, 2028 for 8.4. If your host still runs 8.2 or older, plan the move now. Most hosts let you switch in the control panel. Test on staging first, because an old plugin may break.

4. Check your hosting and server response

If TTFB is slow even with caching on, the server is the bottleneck. No plugin fully fixes a slow server. WordPress.org’s optimization guide notes that the techniques open to you depend on your hosting setup. Ask your host three questions:

  • Which PHP version are we on?
  • Is server-level page caching included?
  • Is a persistent object cache, such as Redis, available?

5. Turn on one page cache

Without a cache, WordPress builds each page from scratch for every visitor. A page cache saves a ready copy. Per WordPress.org’s optimization guide, caching plugins “will cache your WordPress posts and pages as static files.” Use your host’s cache or one plugin. Never run two, because they conflict and can show old or broken pages.

The same guide says a persistent object cache helps by saving trips to the database.

6. Resize photos and switch to WebP or AVIF

Photos can be the heaviest thing on a page. Do two things. First, resize each photo to about the largest size it shows on screen. A phone photo can be far wider than any screen needs. Second, save in a modern format such as WebP or AVIF.

WordPress 6.5 added AVIF support, as the WordPress core team announced. It also depends on your server. Check under Tools > Site Health > Info > Media Handling. If you serve AVIF, keep a WebP or JPEG fallback for older browsers.

7. Lazy-load below the fold, but never the hero image

Lazy loading means an image waits to load until the visitor scrolls near it. It is good for photos far down the page. It is bad for the first big image. Google’s guide to optimizing LCP says to “Never lazy-load your LCP image,” because it adds load delay. If your LCP got worse after you added a speed plugin, check this first.

8. Audit your plugins

WordPress.org’s advice is short: deactivate and delete any unnecessary plugins. The count matters less than what each one does. Sort every plugin into keep, replace or delete.

  • Delete anything inactive. It still sits on your server and still needs updates.
  • Replace plugins that do the same job twice, such as two SEO plugins or two form plugins.
  • Question plugins that load on every page but are used on one, like a slider or booking widget.
  • Keep the rest, and keep them updated.

9. Check your theme and page builder

A theme packed with sliders, animations and features you do not use adds code to every page. Heavy builders can do the same. Start by turning off unused theme features and builder modules. If the theme still drags after steps 1 to 8, a lighter theme or a rebuild can cost less than fighting it. Our website redesign guide explains how to tell a tune-up from a rebuild.

10. Cut third-party scripts that slow taps and clicks

Cutting scripts is a common fix for a poor INP, though heavy theme or builder code can cause it too. Google’s INP guide says slow responses can trace to long tasks on the main thread and slow event handlers. On a small business site, scripts that often add to that work are chat widgets, extra tracking tags, social feeds, video embeds and pop-up tools. If a script does not add clear value, remove it. For the rest, load them later. Test your forms and call tracking after each change.

11. Add a CDN

A CDN (content delivery network) is a group of servers in many places that keep copies of your files and serve each visitor from a close one. WordPress.org says using a CDN “can greatly reduce the load on your website.” Some hosts include one. If your customers are in Central PA, a CDN still takes load off your server, but a good host matters more.

12. Clean the database, after a backup

By default, WordPress saves a copy of each edit to a post or page. Over years, that adds up, along with spam comments and leftovers from deleted plugins. After a fresh backup:

  • Empty spam and trash comments.
  • Delete old revisions, then cap them. Adding define( ‘WP_POST_REVISIONS’, 3 ); to wp-config.php keeps three per post, per the WordPress.org wp-config docs.
  • Check autoloaded options. WordPress.org says to try to keep them under 800kb.
  • Remove tables from plugins you no longer use, only if you are sure what a table belongs to.

Then rerun your three-page test and compare it with your baseline.

StepEffortRiskBest for
1-2 Backup and updateLowLow with a backupEveryone, first
3 PHP versionLowMedium: old plugins can breakSites on 8.2 or older
4 HostingMediumLowHigh TTFB
5 Page cacheLowMedium: can serve stale pagesSlow first byte
6-7 Photos and lazy loadingLowLowPoor LCP
8-10 Plugins, theme, scriptsMediumMedium: can break formsPoor INP
11 CDNLowLowVisitors far from server
12 DatabaseMediumHigh without a backupSlow admin, older sites

Rather not handle updates, backups and security yourself? Our website management is $99 per month. See our website maintenance plans, or if you are in Central PA, our website maintenance in Carlisle, PA page.

A made-up example: the photo problem

This example is made up, with round numbers to show the math. It is not a client result.

Stopwatch, laptop and phone with a magnifying glass over a loading bar
Test on a phone first, so you know where the time goes.

Say a contractor’s home page has a gallery of 10 project photos. Each came straight from a phone at about 4 MB. That is about 40 MB of images on one page (10 × 4 MB). On a weak phone signal at a job site, that page will crawl.

Now resize each photo to the width it really shows at and save it as WebP. Say each file lands near 200 KB. Ten photos now weigh about 2 MB (10 × 0.2 MB). That is about one twentieth of the start, with no change to how the page looks.

BeforeAfter
Photos in gallery1010
Size of each (made up)4 MB0.2 MB
Total image weight40 MB2 MB
Loaded on first screenEverythingHero image only, rest lazy-loaded

Real files will differ. The method holds: resize first, change format second, lazy-load third.

What to do yourself and what to hand off

TaskMost owners can do itBetter with a host or developer
Run tests and record numbersYes
Backups and updatesYes, with a backup you can restoreOn busy sites or stores, test on staging first
Resize and convert photosYes, with an image plugin
Delete inactive pluginsYes
Change PHP versionSometimes, in the host panelYes, if old plugins may break
Delay or remove scriptsRarelyYes, since it can break forms and tracking
Database cleanup and autoload fixesRarelyYes
Theme or builder changeNoYes

If you would rather not touch any of this, speed is part of ongoing upkeep. Our website maintenance checklist for after launch covers the routine that keeps a site fast, and our website maintenance plans handle updates, backups and checks.

Test it on a real phone today

This takes about fifteen minutes and needs no tool.

  1. Turn off wifi on your phone so you use mobile data.
  2. Open your home page in a private tab. Count the seconds until you can read the headline.
  3. Tap the menu and the call button. Note any delay.
  4. Scroll down. Does text jump when images load?
  5. Open your top service page and your gallery. Repeat.
  6. Try it again somewhere with a weaker signal, such as a basement or a back road.
  7. Write down what felt slow. Match it to the decision table above.

If you run ads, the same test applies to the page people land on. See our landing page speed and mobile check.

Common mistakes

MistakeWhy it hurtsFix
Running two caching pluginsThey conflict and can serve old or broken pages.Use your host’s cache or one plugin.
Lazy-loading the hero imageGoogle says never lazy-load the LCP image.Lazy-load only images below the first screen.
Using a speed plugin to fix a slow serverA plugin cannot fix slow hosting.Fix hosting or PHP first.
Testing once on office wifiYou miss what phone visitors see.Test three times, on mobile data.
Cleaning the database with no backupOne wrong click can delete real content.Back up first and confirm you can restore.
Turning on every speed plugin optionCombining or delaying scripts can break menus and forms.Change one setting at a time and test your forms.
Testing only the home pageService pages and galleries can be heavier than the home page.Test three page types.
Fixing speed once and forgetting itNew plugins, photos and scripts creep back in.Make a quarterly speed check part of upkeep.

Frequently asked questions

Why is my WordPress site so slow?

Usually a few causes stack up: slow hosting, no page cache, oversized photos, heavy plugins or scripts, and an old PHP version. Run PageSpeed Insights on your phone view, then use the decision table in this guide to match the symptom to the cause.

A heavy stack of photos shrinking into a light stack
Resizing photos is often the biggest single weight loss for a page.

How do I check my WordPress site speed?

Run your key pages through PageSpeed Insights, open Tools > Site Health in WordPress, and then load the site on your own phone using mobile data. Test three pages, run each three times, and write the numbers down before you change anything.

What is a good PageSpeed score?

Google calls a lab Performance score of 90 or above good, 50 to 89 needs improvement, and below 50 poor. The Core Web Vitals matter more than the score: LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less.

Do I need a caching plugin?

You need page caching, but not always a plugin. Check whether your host already caches pages at the server level. Use your host’s cache or one caching plugin, never two, because two caches can conflict and show visitors old pages.

How many plugins is too many?

There is no safe number. One heavy plugin that loads scripts on every page can cost more than several light ones. Delete plugins you do not use, remove duplicates, and question any plugin that loads on every page but is used on one.

What PHP version should WordPress use in 2026?

WordPress recommends PHP 8.3 or greater. PHP 8.2 gets security fixes only until December 31, 2026, so a site on 8.2 or older should plan a move now. Test on a staging copy first, because an old plugin can break on a newer version.

Does site speed affect SEO?

Google highly recommends good Core Web Vitals for success in Search, but it does not promise a ranking boost for a good score. Treat speed as one part of a good site. The firmer reason to fix it is that slow pages can cost you visitors who would have called.

Can I speed up WordPress myself, or should I hire help?

You can do the safe steps yourself: tests, backups, updates, photo resizing and deleting unused plugins. Hand off PHP changes on a fragile site, script delays, theme problems and database work, because a wrong move there can break forms or tracking.

What to do first

If you only have one hour this week, do steps 1, 2 and 6: test, back up and update, then fix your biggest photos. Next week, check PHP and caching with your host.

Want a second set of eyes? We are a Carlisle, PA agency. Book a call and we will look at what is slowing your site and what to fix first. You can also start with the free Website Teardown. For the bigger picture of a site that brings in calls, read our small business web design guide.

Keep reading

Want help with this in Carlisle or Central PA?

Webfactory Media is a Carlisle, PA agency. See our website maintenance in Carlisle page, or call (888) 849-2397 and we will look at your site for free.

Alex Arce

I’m Alex Arce, founder and AI automation lead at Webfactory Media in Carlisle, PA, where I build AI-driven web design and marketing solutions. I’ve created 25+ custom automations, saving clients over 150 hours.