Quick answer: The fastest wins for WordPress speed are: (1) good hosting with modern PHP (8.3+), (2) page caching, (3) optimised images in WebP or AVIF at the right size, (4) a lightweight theme, (5) fewer, better plugins, and (6) a CDN. Measure first with Google PageSpeed Insights and Search Console’s Core Web Vitals report, then fix the biggest issue, not everything at once. Targets: LCP under 2.5 s, INP under 200 ms and CLS under 0.1.
Why speed matters
Slow pages lose visitors — people leave before the page even loads — and speed is part of the page experience signals Google considers. Fast sites also feel more trustworthy and convert better, whether you sell products or show ads.
Step 0: Measure before you change anything
| Metric | What it measures | Good target |
|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content appears | Under 2.5 seconds |
| INP (Interaction to Next Paint) | How fast the page responds to clicks and taps | Under 200 ms |
| CLS (Cumulative Layout Shift) | How much the layout jumps | Under 0.1 |
Test your most important pages in PageSpeed Insights on mobile, and check real-user data in Search Console’s Core Web Vitals report. Write down your starting scores.
14 ways to speed up WordPress
1. Use good hosting
Cheap, crowded servers make everything slow. Hosting with fast CPUs, server-level caching and modern PHP is the foundation. See how to choose hosting.
2. Run PHP 8.3 or newer
Newer PHP versions run WordPress noticeably faster. Check Tools → Site Health and update PHP in your hosting panel (test on staging first).
3. Turn on page caching
Caching stores ready-made pages so the server doesn’t rebuild them for every visitor. It’s usually the single biggest improvement. Follow our WordPress caching setup guide.
4. Optimise images
Resize images to the size they’re displayed, compress them and serve WebP or AVIF. A 4 MB photo can often become 150 KB with no visible difference.
5. Lazy-load images below the fold
WordPress lazy-loads images by default. Make sure your main above-the-fold image is not lazy-loaded, so it appears fast (it’s often your LCP element).
6. Use a lightweight theme
Some themes load huge amounts of CSS and JavaScript. Fast themes keep pages light — see best free themes.
7. Remove unnecessary plugins
Every plugin can add scripts and database queries. Delete what you don’t use and replace heavy plugins with lighter ones.
8. Use a CDN
A content delivery network serves files from servers near your visitors, speeding up global traffic.
9. Reduce render-blocking CSS and JavaScript
Defer non-critical scripts and remove unused CSS. Many caching and performance plugins can do this — test carefully, as it can break layouts.
10. Limit third-party scripts
Chat widgets, heavy analytics, social embeds and too many ad tags slow pages. Keep only what earns its place.
11. Host fonts locally and load fewer weights
Use one or two font families and only the weights you need, hosted on your own server.
12. Clean the database
Remove old post revisions, spam comments and expired transients. Back up first.
13. Avoid layout shifts
Set width and height on images and ad slots so content doesn’t jump while loading — this improves CLS.
14. Keep everything updated
WordPress core regularly includes performance improvements, and so do good plugins and themes.
Priority order for most sites
| Priority | Fix | Effort | Impact |
|---|---|---|---|
| 1 | Caching | Low | High |
| 2 | Image optimisation | Low | High |
| 3 | Hosting / PHP version | Medium | High |
| 4 | Remove heavy plugins and scripts | Medium | Medium–high |
| 5 | CDN | Low | Medium |
| 6 | CSS/JS optimisation | Medium | Medium |
A real-world example
Imagine a small bakery site with a 4 MB hero photo, six plugins (two of them unused), no caching and an old PHP version. A typical improvement path looks like this: resize and convert the hero photo to WebP (often the biggest single LCP gain), turn on page caching, delete the unused plugins, and ask the host to switch to PHP 8.3. None of these steps need code, and together they usually turn a slow, frustrating page into one that feels instant. Measure again after each change so you know what helped.
Speed for WooCommerce and membership sites
Stores and membership sites are harder to speed up because cart, checkout and account pages are personal to each visitor and can’t be fully cached. Focus on fast hosting with good PHP performance, object caching (such as Redis, if your host offers it), lean product images and fewer plugins on checkout pages. See our WordPress ecommerce guide.
Common mistakes
- Installing several caching plugins at once — they conflict.
- Chasing a perfect 100 score instead of real-user Core Web Vitals.
- Lazy-loading the hero image, which hurts LCP.
- Optimising on the live site without a backup.
Frequently asked questions
How fast should a WordPress site load?
Aim for the main content to appear within 2.5 seconds on mobile (LCP), with quick responses to taps.
Does the theme affect speed?
Yes, a lot. Lightweight themes load far less code.
Do I need a paid speed plugin?
Not always. Server caching plus a good free plugin and optimised images often get you most of the way.
Why is my admin dashboard slow?
Usually heavy plugins, slow hosting or an old PHP version.
Final thoughts
Measure, fix the biggest problem, measure again. Caching, images and hosting solve most speed problems — start there.
A real-world speed makeover
A local bakery’s WordPress site took nearly seven seconds to show its homepage on mobile. The owner followed the steps in this guide over one afternoon. She turned on her host’s built-in page caching, which made the biggest single difference. She resized the homepage photos from 4,000 pixels wide to 1,600 and converted them to WebP, cutting the page weight from 9 MB to under 1.5 MB. She removed a slider plugin and replaced it with one strong image, and she deleted three plugins she no longer used. Finally, she asked her host to upgrade PHP to a current supported version. The homepage now loads in under two seconds on mobile, and more visitors reach the online order page.
None of these steps required a developer. The lesson is to start with the changes that have the biggest effect — caching, images and hosting — before worrying about small technical tweaks.
Speed and security often go together
Several speed improvements also make your site safer. Running a current, supported PHP version is faster and receives security patches, which mattered greatly when the October 2026 PHP2Shell vulnerabilities were disclosed. Removing unused plugins reduces both page weight and the number of things attackers can target. Good hosting usually brings faster servers and faster security patching. Treat speed work as part of your site’s overall health rather than a one-off project.
How often should you test speed?
Test your homepage and two or three important pages every three months, and after any major change such as a new theme, plugin or host. Record the results so you can spot when something slows the site down.
WordPressPrime.com is an independent guide and is not affiliated with the WordPress Foundation, WordPress.org or Automattic. Always back up your website before making changes, and check official sources for the latest details.
