Free Website AuditSee exactly what is holding your site back from ranking and converting. Claim yours

Free Website AuditClaim yours

WordPress Speed Optimization Checklist: 30 Checks Before You Pay Anyone

Thirty WordPress speed checks in six phases, each with a pass mark, and how to tell when it is time to hire help.
Digital Roots Media logo mark

By Michael C., SEO Strategist

On this page
Illustration of an airliner on a runway next to a clipboard with a ticked preflight checklist
Pilots do not skip the preflight. A faster WordPress site starts with the same habit.

This WordPress speed optimization checklist gives you 30 checks in six phases: measure, server, caching, images, CSS, JavaScript and fonts, then plugins and the database. Each check has a pass mark, so you know when to move on. Work through them in order, change one thing at a time and retest. You can try the first three phases without a developer; the last part of this guide explains the signs that a problem needs professional help, so you only pay for what you cannot fix yourself.

The pass marks come from Google’s own Core Web Vitals thresholds and WordPress’s own documentation, not from a plugin vendor. Print this page or keep it open next to your dashboard while you work.

Key takeaways

  • Measure before and after every change, on mobile, with PageSpeed Insights.
  • The three pass marks: server response 0.8 seconds or less, LCP 2.5 seconds or less, INP 200 ms or less.
  • Server and caching checks come first, because everything else waits on the server’s first response.
  • Back up and use a staging copy for anything beyond a settings change.
  • If the server is still slow after caching, or the fix needs a rebuild, that is the point to get help.
Free proposal
Want help putting this into action?

Share your website. We will send a free audit and a fixed-price plan built around your goals.

How to use this checklist

A cockpit panel with six numbered instruments: measure, server, caching, images, CSS JS and fonts, and plugins and data
Six phases with five checks each. Do them in order: early phases unlock the later ones.

Run the phases in order. In our view, there is little point shrinking images while the server takes three seconds to answer. After each check, retest the same pages and write down the result. That log is what tells you which fixes worked, and it is what a developer will ask for if you do end up hiring one.

A circuit around a plane with four stops: measure, fix one thing, retest and write it down
Change one thing per circuit. Two changes at once make it impossible to tell which one helped.

Phase 1: measure (checks 1 to 5)

Phase 1: measurePass mark: you have a written baseline
  1. Test your homepage and two key pages in PageSpeed Insights on mobile.
  2. Write down the field data (real visitors over the last 28 days) and the lab score for each page.
  3. Note Time to First Byte. Google calls 0.8 seconds or less good.
  4. Note LCP, INP and CLS against the Core Web Vitals thresholds: 2.5 seconds, 200 milliseconds and 0.1.
  5. Test logged out, in a private window, so you see what visitors see.
Three cockpit dials: TTFB 0.8 seconds or less, LCP 2.5 seconds or less and INP 200 milliseconds or less
The three numbers to record first. Each points to a different part of this checklist.

If field data says the site passes but the lab score is low, your real visitors are doing better than the test device. If field data is missing, PageSpeed Insights has too few real Chrome visits to report, and the lab test is your guide.

Phase 2: server (checks 6 to 10)

Phase 2: serverPass mark: TTFB 0.8 seconds or less on a cached page
  1. Run PHP 8.3 or newer, as WordPress recommends. Check under Tools, Site Health, Info, Server, and test the upgrade on staging.
  2. Check the WordPress memory limit in Site Health. WordPress itself only asks for 40 MB on a single site; Elementor, for example, asks for at least 256 MB.
  3. Make sure your server is in or near the country where most of your customers are.
  4. Check your hosting plan’s resource usage for limits being hit at busy times.
  5. Confirm HTTPS works with no redirect chains (http to https to www and back).

Our guide on why a WordPress site is slow explains each server cause in more depth, including when moving host is the right call.

Phase 3: caching (checks 11 to 15)

Phase 3: cachingPass mark: repeat visits served from cache, TTFB down
  1. Turn on exactly one page cache: your host’s or one plugin, never two.
  2. Exclude cart, checkout, account and other personalised pages from the page cache.
  3. Turn on cache preloading so the first visitor after a change does not get a slow page.
  4. Ask your host about a persistent object cache, which cuts trips to the database.
  5. Use a CDN if your visitors are far from your server.

Not sure which caching plugin fits your host? Our LiteSpeed Cache vs WP Rocket comparison explains why the web server is the first question. One more note from WordPress’s wp-config documentation: the WP_CACHE line does nothing on its own without the advanced-cache.php file a caching plugin installs, so do not add it by hand and expect a change.

Phase 4: images (checks 16 to 20)

Phase 4: imagesPass mark: LCP 2.5 seconds or less on mobile
  1. Find the LCP element in PageSpeed Insights. It may be the hero image.
  2. Make sure the hero is never lazy loaded. Google’s advice: never lazy-load your LCP image.
  3. Use a normal image for the hero, not a CSS background or slider, so the browser finds it early.
  4. As a rule of thumb, resize images to about twice their display width before upload and serve WebP or AVIF.
  5. Lazy load images further down the page, and set width and height so the layout does not jump.

LCP has several moving parts. Our guide to fixing WordPress LCP breaks it into four parts and shows which WordPress setting controls each.

Phase 5: CSS, JavaScript and fonts (checks 21 to 25)

Phase 5: CSS, JavaScript and fontsPass mark: INP 200 ms or less, no layout breakage
  1. Remove CSS and JavaScript that pages do not use, or let your caching plugin remove unused CSS.
  2. Defer or delay non-critical JavaScript, then check menus, forms and sliders on a phone.
  3. Use one or two font families and only the weights you need, self-hosted as WOFF2.
  4. Set font-display to swap or optional so text appears straight away.
  5. List every third-party script (chat, pixels, maps, video) and load the ones you keep on click or later.

If taps feel slow, read our Interaction to Next Paint guide. Built with Elementor? Our guide to a slow Elementor site lists the builder’s own performance settings, and Google’s DOM size guide explains why Lighthouse flags pages over 1,400 nodes.

Phase 6: plugins and database (checks 26 to 30)

Phase 6: plugins and databasePass mark: no plugin dominates the slowest queries
  1. Install Query Monitor on staging and find the slowest queries and the plugins behind them.
  2. Delete plugins and themes you no longer use, not just deactivate them.
  3. Check Site Health for autoloaded options. From WordPress 6.6 it warns above 800 KB.
  4. Limit post revisions with WP_POST_REVISIONS in wp-config.php and clear old spam and transients, after a backup.
  5. Move WP-Cron to a real server cron on busy sites, with DISABLE_WP_CRON set to true.
A cargo hold full of boxes, some highlighted, next to a panel reading 800 KB Site Health warning line
Autoloaded options are cargo WordPress carries on every request. Site Health warns above 800 KB.

Autoloaded options are settings WordPress loads on every single request, whether the page needs them or not. A plugin you deleted may have left some behind. Check them in Site Health before blaming your host.

A departures board for scheduled tasks: WP-Cron runs when visitors arrive, server cron runs on a fixed schedule
WP-Cron rides on visitor page loads. A server cron runs scheduled tasks on time instead.

WordPress’s own handbook explains that WP-Cron checks for due tasks on page loads, so busy sites do the check constantly and quiet sites run tasks late. A server cron fixes both. Ask your host how to set one up.

What passing looks like: our own numbers

We rebuilt our own service pages on a lighter layout in 2026. In our November 2026 audit, mobile PageSpeed Insights scores had moved from 59 to 60 up to 88 to 89, with LCP at about 2.6 seconds. One older page still on the previous layout scored 55 with an LCP of 13.4 seconds. Those are our pages, not a promise for yours, but they show the size of change a lighter page build can make.

Animation of an airliner rolling down a runway and lifting off as a counter climbs from 0 to 30 checks done
Thirty checks, then takeoff. Retest after the last one and compare with your phase 1 baseline.

When to hire help

You can do a lot of this checklist yourself. Some problems, though, cost more in time and risk than paying someone. These are the signs:

A control tower with three orange signal lights: TTFB still slow after caching, layout needs rebuilding, store or members area
Three signs a speed problem has moved beyond settings and needs a developer.
Signs a speed problem needs professional help (our view)
What you see Why it needs help Who we would call
TTFB over 0.8 s even with a page cache Slow code, database or hosting limits Developer or a better host
Passing lab scores but failing field data Real visitors hit pages or devices the test misses Speed specialist
DOM size warnings across the site The theme or layout needs rebuilding WordPress developer
Store, booking or members area is slow Cart and account pages stay out of the page cache Developer plus object cache
Settings break menus, forms or checkout Scripts need careful exclusions Speed specialist

When you do hire, share your phase 1 baseline and your change log. A good specialist will measure the same pages, explain what they will change and show you before and after numbers. Be wary of anyone who promises a perfect score or a ranking jump: Google says there is no single signal, and that a perfect score just for SEO may not be the best use of your time.

Done the checklist and still slow?

We take your baseline, find the bottleneck that settings cannot fix and fix it properly: hosting, caching, images, scripts, plugins or the page build itself.

See our WordPress speed optimization service →

Speed also slips over time as plugins update and new content goes up. Our maintenance plans, from $199 a month, include ongoing care, and our WordPress maintenance checklist shows what to keep checking.

Frequently asked questions

How do I optimize WordPress website speed step by step?

Measure first in PageSpeed Insights on mobile. Then fix the server (PHP version, memory, hosting), turn on one page cache, fix the hero image and image sizes, trim CSS, JavaScript and fonts, and finally audit plugins and the database. Change one thing at a time and retest, so you know which fix made the difference.

Which checks make the biggest difference to WordPress speed?

Our short list is three: a working page cache, a hero image that is properly sized and never lazy loaded, and fewer third-party scripts. Better hosting can matter more when Time to First Byte is slow. We would leave plugin and database clean-ups until later, unless one plugin clearly stands out in Query Monitor. Your own before and after numbers will show which fix helped.

How often should I run a WordPress speed checklist?

Run the full checklist once, then repeat the measuring phase every month and after any big change: a new plugin, a theme update, a redesign or a new tracking script. Field data covers 28 days, so a monthly check catches slow drift before it shows up as a failing Core Web Vitals report.

Can I speed up WordPress without plugins?

Partly. Hosting, PHP version, image sizes before upload, fewer fonts, fewer third-party scripts and deleting unused plugins need no extra plugin at all. Page caching needs either your host’s built-in cache or one caching plugin. Some hosts include page caching, so check before installing one.

Is a 100 PageSpeed score necessary?

No. What matters is passing Core Web Vitals for real visitors: LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less. Chasing the last few lab points can mean removing useful features. We would call a site that passes its field data with a score in the high 80s in good shape.

Free website audit
Not sure where your website stands?

We will review your website and show you exactly what is holding it back.

Search visibility review
Rankings and traffic, page by page
Pages that underperform
The URLs that should bring in more
Content and speed issues
What is holding pages back
What to fix first
A clear list in priority order

Final thoughts

A WordPress speed optimization checklist works the way a preflight does: the same checks, in the same order, every time, with a clear pass mark for each. Do the first phases yourself and keep a log. If the server is still slow after caching or the fix needs a rebuild, our WordPress speed optimization service picks up where you left off, our maintenance plans keep the site fast, and our website as a service plan covers hosting, caching and care in one monthly fee.

Independent reviews
Recognized on the platforms clients trust
GoodFirms Top Web Designing Company badge
Clutch Top Webflow Development Phoenix 2026 badge
UpCity Top Digital Agency featured badge
BusinessFirms verified agency badge
Digital Roots Media logo mark
Written by

SEO Strategist at Digital Roots Media, 8+ years in SEO. Michael plans SEO strategy for the businesses we work with and leads this blog, working with the DRM SEO team to track every confirmed Google update and turn it into clear next steps.

Keep Reading

Related Articles

More on this topic from our team.

Illustration of a theatre stage with red curtains half open and a framed picture arriving late under a gold spotlight
Web Development

How to Fix WordPress LCP (Largest Contentful Paint), Cause by Cause

How to find what is slowing Largest Contentful Paint on a WordPress site and fix each cause, from caching to the hero image.
Illustration of a teal chess rook labelled LiteSpeed Cache facing a rust knight labelled WP Rocket on a chess board
Web Development

LiteSpeed Cache vs WP Rocket: Which One Makes WordPress Faster?

LiteSpeed Cache or WP Rocket? Your web server decides most of it; here are the features, prices, settings and a fair way to test both.
Illustration of a hiker on a mountain trail carrying a backpack piled high with boxes labelled CSS, icons, fonts and add-ons
Web Development

Elementor Slow? How to Speed Up an Elementor Website Without Rebuilding It

Why Elementor sites get slow and the settings, font, add-on and layout fixes that speed one up without a rebuild.

Free Website Audit

Rather Have Experts Do It for You?

Reading is a great start. Share your website and email, and our team will show you what is holding it back, with a free audit and a fixed-price proposal. No obligation.

We never share your details. No spam.