To speed up a WordPress website, start with the server and work outwards: fast hosting close to your visitors, page caching and a current PHP version. Then shrink your images, remove heavy plugins and cut third-party scripts. Those six fixes usually make more difference than the other fourteen combined, so do them first.
Key takeaways
- Measure before you change anything, so you know which fix helped.
- Hosting, caching and PHP version are the biggest levers, and often the cheapest.
- Images and plugins are where most slow small-business sites lose time.
- Minifying files and cleaning the database help, but less than people expect.
- Speed isn’t a one-off job. New plugins, images and scripts slow a site down again.
Why does WordPress speed matter?
Slow pages cost sales. Deloitte found that a 0.1-second improvement in mobile speed lifted retail conversions by 8.4% and travel conversions by 10.1% (web.dev case study). In Australia, mobile now makes up 48.6% of web traffic, slightly ahead of desktop (StatCounter). Mobile visitors on patchy 4G feel every extra second.
Google measures speed too. Its Core Web Vitals count a page as good when the main content loads within 2.5 seconds, the page responds to a tap within 200 milliseconds and the layout shifts no more than 0.1 (web.dev).
How do I measure my site’s speed first?
Run your home page and your busiest page through Google’s PageSpeed Insights. Note three numbers: Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). Test on mobile, because that’s where most sites fail.
Write the results down. Then make one change at a time and test again. If you change five things at once, you won’t know which one helped, or which one broke something.
The 20 fixes at a glance
We’ve ranked each fix by how much it typically helps a small-business WordPress site, based on our experience. Your results will vary with your theme, plugins and traffic.
| # | Fix | Impact | Effort |
|---|---|---|---|
| 1 | Faster hosting near your visitors | High | Low |
| 2 | Page caching | High | Low |
| 3 | Supported PHP version | High | Low |
| 4 | Resize and compress images | High | Medium |
| 5 | Remove heavy plugins | High | Medium |
| 6 | Cut third-party scripts | High | Medium |
| 7 | Load the hero image first | Medium | Low |
| 8 | Lighter theme or builder setup | Medium | High |
| 9 | Object caching | Medium | Low |
| 10 | Content delivery network | Medium | Low |
| 11 | Lazy-load lower images and videos | Medium | Low |
| 12 | Fewer web fonts | Medium | Medium |
| 13 | Defer non-essential JavaScript | Medium | Medium |
| 14 | Replace sliders with a static image | Medium | Low |
| 15 | Set image sizes to stop layout shift | Medium | Low |
| 16 | Fix redirect chains | Low | Low |
| 17 | Compression and browser caching | Low | Low |
| 18 | Clean up the database | Low | Low |
| 19 | Minify CSS and JavaScript | Low | Low |
| 20 | Re-test every month | Ongoing | Low |
Which fixes make the biggest difference?
1. Move to faster hosting near your visitors
Every page starts with the server. web.dev notes that a high Time to First Byte “can make achieving a 2.5 second LCP challenging, or even impossible” (web.dev).
Distance adds delay as well. One measurement put Sydney to Los Angeles at 136.6 milliseconds per round trip, against 9.7 milliseconds from Sydney to Melbourne (HATSnet). If your customers are Australian, host in Australia, on a plan with enough CPU and memory. Our guide to WordPress hosting in Australia covers what to look for.
2. Turn on page caching
Without caching, WordPress builds each page from scratch for every visitor. A page cache stores a finished copy and serves that instead. WordPress.org’s optimisation guide says caching plugins “cache your WordPress posts and pages as static files” (WordPress.org). Many hosts cache at the server level, which is faster still. Use one caching layer, not three that fight each other.
3. Run a supported PHP version
PHP is the language WordPress runs on, and WordPress.org notes that newer PHP versions “usually include better performance optimization”. Old versions also stop getting security fixes. PHP 8.2 loses security support on 31 December 2026 (PHP.net). Test on a staging copy first, because some old plugins break on newer PHP.
4. Resize and compress your images
A 4,000-pixel photo straight off a phone can weigh several megabytes. Resize images to the largest size they’ll display, then compress them. Modern formats help: WordPress has supported AVIF since version 6.5, and AVIF images “can be up to 50% smaller than JPEGs” at the same quality (Make WordPress Core). WebP is a safe, widely supported alternative.
5. Remove heavy or unused plugins
The number of plugins matters less than what they do. One poorly built plugin can slow every page. Deactivate and delete anything you don’t use, and look for plugins that load scripts site-wide when they’re only needed on one page. Contact form, slider and social feed plugins are common culprits.
6. Cut third-party scripts
Chat widgets, tracking pixels, review badges and embedded maps all load code from other companies’ servers. You can’t control how fast those servers are. List every script on your site, ask whether each one earns its place, and remove the rest.
What are the medium-impact fixes?
7. Load the hero image first
The big image at the top of a page is often the LCP element. web.dev warns: “Never lazy-load your LCP image.” Since WordPress 6.3, core adds a high fetch priority to the image most likely to be the LCP (Make WordPress Core). Themes and builders that set their own loading rules can override this, so check your hero image isn’t marked lazy.
8. Use a lighter theme or builder setup
Some multipurpose themes and page builders load large amounts of code on every page. Switch off builder features and widgets you don’t use. If the theme itself is the problem, it may be time to weigh up a website redesign vs refresh.
9. Add object caching
An object cache keeps the results of common database queries in memory. WordPress.org says a persistent object cache “helps speed up page load times”. It helps most on WooCommerce shops, membership sites and busy admin areas. Your host needs to support it.
10. Use a content delivery network
A content delivery network (CDN) stores copies of images, CSS and scripts on servers around the world. For a mainly Australian audience on Australian hosting, the gain is modest. It helps more if you have overseas visitors or traffic spikes.
11. Lazy-load lower images and videos
Images further down the page should wait until the visitor scrolls. WordPress does this by default. YouTube embeds are heavy, so swap them for a preview image that loads the player only when clicked.
12. Use fewer web fonts
Every font family and weight is another file. Two families in two or three weights is plenty. Host the fonts on your own server where your theme allows it.
13. Defer non-essential JavaScript
Scripts that run before the page shows delay everything. Deferring them lets the content appear first. Test carefully: deferring the wrong script can break menus, forms or checkouts.
14. Replace sliders with a static image
Sliders load several large images and extra code. One strong image with a clear headline usually loads faster and works better for visitors.
15. Set image sizes to stop layout shift
When images load without set dimensions, the page jumps. That hurts your CLS score and annoys readers. Make sure images, ads and embeds have width and height set. Clear, stable layouts also help visitors who rely on assistive technology, as our guide to website accessibility Australia explains.
Which small fixes are still worth doing?
16. Fix redirect chains
A visitor typing your address might be redirected from http to https, then to www, then to a new page. Each hop adds a delay. Make sure old addresses go straight to the final page in one step.
17. Turn on compression and browser caching
Compression shrinks text files before they’re sent. Browser caching lets returning visitors reuse files they already have. Most good hosts set both up at the server, so check before adding a plugin.
18. Clean up the database
Old post revisions, expired temporary data and spam comments build up over time. WordPress.org suggests limiting stored revisions and clearing out clutter. Back up before any clean-up.
19. Minify CSS and JavaScript
Minifying removes spaces and comments from code files. It helps a little. Combining files used to matter more, but modern connections handle many small files well, so don’t spend hours on it.
20. Re-test every month
Speed drifts. A new plugin, a large uploaded photo or a marketing script can undo your work. Re-run PageSpeed Insights monthly and after any big change.
When should I get help?
Fixes 1 to 3 are often a quick conversation with your host. Fixes 7, 8 and 13 can break things if done wrong, so test them on a staging copy or ask a developer. If your site is still slow after the top six fixes, the cause is usually the theme, a plugin conflict or the server itself.
Our website speed and improvement work covers diagnosis and fixes like these. To keep a site fast after the work is done, our website maintenance plans handle updates, checks and monthly reporting.
Frequently asked questions
Why is my WordPress site so slow?
The most common causes are slow or overloaded hosting, no page caching, large images and heavy plugins or page builders. Third-party scripts such as chat widgets and tracking pixels add more. Run PageSpeed Insights to see which parts of the page take the longest, then work through the top fixes above.
Do I need a caching plugin?
Only if your host doesn’t cache pages at the server. Server-level caching is usually faster and simpler. Ask your host first. If you do add a plugin, use one, and don’t stack it with another caching plugin, which can cause broken pages and hard-to-find errors.
How many plugins is too many?
There’s no magic number. Twenty light, well-built plugins can run faster than five heavy ones. What matters is what each plugin loads and when. Remove plugins you don’t use, and check whether any load code on every page when they’re only needed on one.
Will a faster site improve my Google rankings?
Speed is one of many signals Google uses, through its Core Web Vitals. It won’t lift weak content to the top, but a slow site can hold good content back. The bigger benefit is usually more enquiries and sales from visitors who don’t give up waiting.
Is a speed score of 100 necessary?
No. Aim to pass the Core Web Vitals thresholds on mobile for your key pages. Chasing a perfect lab score often means removing features customers use. A site that loads its main content in under 2.5 seconds and responds quickly is doing well.
Sources
- Milliseconds make millions, web.dev (Deloitte research, 2020)
- Desktop vs mobile vs tablet market share, Australia, StatCounter, October 2026
- Web Vitals, web.dev
- Optimize Largest Contentful Paint, web.dev
- Sydney to Los Angeles round-trip latency, HATSnet, October 2026
- Optimization, WordPress Advanced Administration Handbook, accessed November 2026
- Supported versions, PHP.net, accessed November 2026
- WordPress 6.5 adds AVIF support, Make WordPress Core, 23 February 2024
- Image performance enhancements in WordPress 6.3, Make WordPress Core, 13 July 2023