Step 0: measure before you change anything
Run your homepage and your most important inner page (a product page, a service page, your checkout if you run a store) through Google PageSpeed Insights. Test the mobile result, because that is the score Google uses and the device most of your visitors hold. You are reading three numbers, the Core Web Vitals:
| Signal | What it measures | Good score |
|---|---|---|
| Largest Contentful Paint (LCP) | How fast the main content appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds to taps and clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the page jumps around while loading | 0.1 or less |
Write your starting scores down. They tell you which fix matters: a bad LCP usually means server speed or a heavy hero image, a bad INP means too much JavaScript, and a bad CLS means images and embeds loading without reserved space. They also prove the work worked when you retest at the end. If your site feels slow but you do not know why yet, our diagnosis guide on why your WordPress site is so slow walks the causes before you touch a setting.
Fix 1: fix the hosting first
No plugin can outrun a slow server. If your time to first byte is poor on cheap, overloaded shared hosting, every fix below is fighting with one hand tied. Signs hosting is your bottleneck: the dashboard itself is slow, speed scores swing wildly between tests, and your site slows down whenever traffic rises. The honest options are a better plan at your current host, or a move to managed WordPress hosting. This is the one fix that costs real money, and it is also the one that caps every other fix, which is why it goes first.
Fix 2: turn on page caching
Without caching, WordPress rebuilds every page from PHP and database queries for every single visitor. Page caching stores the finished page and serves the stored copy, which is usually the single biggest speed gain available on a WordPress site. Use one caching method only: your host's built in cache if it has one, the free LiteSpeed Cache plugin on LiteSpeed servers, or a premium all in one like WP Rocket on other hosts. Never stack two page caches. Never cache the cart, checkout, or account pages on a store.
Fix 3: update PHP
WordPress runs on PHP, and newer PHP versions are simply faster. Sites still running PHP 7.4 get a free performance jump moving to a supported PHP 8 version, often the easiest win on this whole list. Check your version under Tools, Site Health, Info, Server. Update through your hosting panel, test the site right after, and keep one eye on older plugins, which are the usual reason an update breaks something.
Fix 4: resize and convert your images
Images are the heaviest part of most pages, and the most common cause of a bad LCP. Three habits fix nearly all of it. Resize before upload: a photo displayed at 800 pixels wide should not be uploaded at 4,000. Convert to WebP, which is roughly a third smaller than the same JPEG at the same quality. And lazy load below the fold images, while keeping your hero image eager, since the hero is usually your LCP element and lazy loading it makes the score worse.
Fix 5: audit your plugins
Plugin count alone does not slow a site, but heavy plugins do: page builders with a dozen add on packs, sliders, social feed widgets, and anything that loads scripts on every page whether the page uses it or not. The free Query Monitor plugin shows which plugins add the most queries and load time to a page. Delete what you no longer use, replace heavy tools with lighter ones, and remember that a deactivated plugin still sitting in your install is clutter, not speed.
Fix 6: clean the database
Years of post revisions, spam comments, expired transients, and leftover tables from deleted plugins bloat the database that every page load queries. A cleanup tool such as WP-Optimize removes the junk safely. Limit future revisions by adding define( 'WP_POST_REVISIONS', 10 ); to wp-config.php. Back up before any database work, always.
Fix 7: add a CDN
A content delivery network serves your images, CSS, and JavaScript from a server near each visitor instead of one server in one city. If your audience is in more than one country, a CDN is the cheapest global speed upgrade there is. Cloudflare's free plan is enough for most small sites, and many hosts include a CDN in the plan you already pay for.
Fix 8: trim CSS, JavaScript, and fonts
Minify your CSS and JavaScript, delay scripts the page does not need to be interactive, and generate critical CSS so the visible part of the page paints first. Most caching plugins handle all three. Fonts deserve their own look: load two weights, not six, and host Google Fonts locally if your theme allows it, because every external font request is a delay your visitor pays for.
Fixes 9 to 12: the finishing list
Fix 9: enable GZIP or Brotli compression so text files travel smaller. Most hosts and caching plugins switch this on with one setting. Fix 10: reserve space for images and embeds with width and height attributes, which is what kills layout shift and fixes CLS. Fix 11: disable pingbacks, trackbacks, and hotlinking, small leaks that add requests and steal bandwidth. Fix 12: keep everything updated, because stale core, theme, and plugin versions are slower and less safe than current ones, and updates are part of speed whether they feel like it or not.
WooCommerce stores: three extra fixes
Stores carry weight blogs never have. Tame the cart fragments AJAX call, which WooCommerce fires on every page to update the cart count and which drags simple content pages down with it. Keep checkout plugins to the minimum, because every added field script loads at the exact moment a customer is deciding. And test a real product page and the checkout in your speed runs, not just the homepage: a fast homepage with a four second checkout is a fast way to lose money.
What not to waste money on
Skip the booster plugins that promise one click miracles and mostly install ads. Skip paying for a premium theme to fix speed when your current theme is not the measured problem. And skip chasing a 100 score: the goal is fast enough that visitors stay and Google is satisfied, which for most business sites means green Core Web Vitals on the pages that make money, not a perfect number on a test page nobody visits.
When to hand it to someone else
If you have worked through hosting, caching, and images and the scores still will not move, the remaining causes are usually code level: a theme or plugin doing something expensive that needs a developer's eye. Our WordPress speed optimization service does this work in the same order as this guide, measured before and after, and our WordPress care plans keep the gains from quietly rotting away. Fix the order, and the speed follows.
Frequently asked questions about WordPress speed
How long does it take to speed up a WordPress site?
The first four fixes in this guide, hosting, caching, PHP, and images, take an afternoon and usually deliver most of the gain. A full pass including plugin and database work is one to two days of careful work, with testing after every change so you know which change did what.
What is a good page load time for a WordPress site?
Aim for the Core Web Vitals thresholds: LCP at or under 2.5 seconds, INP at or under 200 milliseconds, and CLS at or under 0.1, measured on mobile at the 75th percentile of real visits. In plain terms, a business site that feels fast loads its main content in about two seconds or less.
Will a caching plugin alone fix my slow site?
Caching is usually the biggest single gain, but it cannot fix a slow server, giant images, or a heavy plugin. If the bottleneck is hosting or media weight, caching hides some of it and the rest still shows. Measure first, then fix in order.
Does the number of plugins slow WordPress down?
Not by itself. One badly built plugin that loads scripts everywhere can cost more than thirty light ones. Judge plugins by what they load on your pages, which Query Monitor shows you, not by the count.
How much does professional WordPress speed optimization cost?
It depends on the site's size and what the measurements find. Simple sites with the usual bottlenecks are a fixed fee job, and our own speed packages start at $45 for a basic pass. Stores and custom builds are quoted after a speed audit, because the honest price follows the diagnosis, not a guess.
Free PDF download: WordPress Speed Optimization Checklist
The 12 fixes in order of impact, with a scores table to record your before and after Core Web Vitals.
Download the PDFWant your site fast without spending your weekend on it?
Our WordPress speed optimization service works in the same order as this guide: measured first, the biggest bottleneck fixed first, and the Core Web Vitals proven better at the end. Hosting, caching, images, plugins, and database, handled by the team that has built and run WordPress sites since 2018 across more than 120 projects.
Related: WordPress speed optimization service · Why is my WordPress site so slow? · WordPress maintenance cost · What a WordPress care plan includes
