If your WordPress site takes more than a few seconds to show anything on a phone, it's costing you money. Visitors who tap away before the page loads never see your offer, never fill in the form and never ring. Paid traffic makes it worse, because you pay for the click and still lose the visitor. Speed also feeds into Google's page experience signals through Core Web Vitals, so a slow site can hold back your search visibility, although speed alone won't outrank better content.
The good news is that a slow WordPress site usually has two or three real causes, not twenty. Start by testing with real-visitor data, not just a lab score. Then fix the server, the hero image and the scripts that stall clicks, in that order, and leave the small tweaks for last. This guide walks through each step, so you can work through it yourself or hand the checklist to your developer. If speed still slips back after every update, the last section covers when moving off WordPress makes sense.
Why is my WordPress site so slow?
Most slow WordPress sites share the same handful of causes: weak hosting, oversized images, too many plugins, heavy page builders, third-party scripts and no caching. WordPress rarely slows down on its own. The trouble is usually what's been added on top of it, and where it's hosted.
Plugins deserve a closer look because they pile up quietly. A contact form, a slider, an SEO tool, a popup builder and a booking calendar each seem harmless alone. Together they can add dozens of CSS and JavaScript files and extra database queries to every page. The number of plugins matters less than what each one does. One badly written plugin can slow a site more than ten light ones, and a plugin you stopped using months ago still loads its code if it's switched on.
Why WordPress can feel slower than other platforms
WordPress builds each page when someone asks for it. PHP code runs, the database answers a stack of queries, and the server assembles the page before sending it. A static site skips all that and hands over a finished file.
Every plugin and theme adds code to that process. Google's own guidance on server response time singles out WordPress as an example, noting that performance depends on the number and quality of plugins and on the theme. It also explains why two WordPress sites can behave nothing alike.
5 common causes of a slow WordPress site
These are the ones to check first:
- Hosting. A shared server with too little memory slows every page, whatever else you do.
- Images. A 4,000-pixel photo squeezed into a 600-pixel slot still downloads in full.
- Plugins and page builders that load their CSS and JavaScript on pages that don't need them.
- Third-party scripts such as chat widgets, ad pixels and tag managers.
- No caching, so the server rebuilds every page for every visitor.
Before you change anything, find out which of these applies to your site.
How to check your WordPress website speed
Run your homepage and one key page through Google's PageSpeed Insights, then open the Core Web Vitals report in Google Search Console. Test on mobile first. PageSpeed Insights shows a simulated lab result and, when Google has enough data, results from real visitors.
4 tools to test your page speed
Each tool answers a different question. This table shows where each one helps and where it falls short:
| Tool | Best for | Limit |
|---|---|---|
| PageSpeed Insights | A free first check with mobile and desktop results | You can't choose the test location or device |
| GTmetrix | A waterfall chart showing which file loads when | Some locations and options need a paid plan |
| Google Search Console | Core Web Vitals across groups of similar pages | It shows where the problem is, not why |
| Chrome DevTools | Digging into one slow click or page | Technical, and it reflects your own device |
Start with PageSpeed Insights. If it flags a problem, the GTmetrix waterfall usually shows the file behind it. These strengths and limits follow WP Rocket's comparison of Core Web Vitals tools. Where a tool lets you pick a test location, choose one near your customers.
Field data vs lab data
Lab data comes from a simulated test. Field data comes from real visitors on real phones and networks. Google judges Core Web Vitals on field data at the 75th percentile, which means at least three in four visits need to be good.
That's why a site can score 95 in the lab and still fail. The 0-to-100 Lighthouse score and the Core Web Vitals assessment are different things. Your own laptop is a poor test too, because your browser has already stored most of the site.
Core Web Vitals targets for a good speed score
Google sets three Core Web Vitals targets: Largest Contentful Paint (LCP) within 2.5 seconds, Interaction to Next Paint (INP) within 200 milliseconds, and Cumulative Layout Shift (CLS) under 0.1. INP replaced First Input Delay on 12 March 2024, so any guide still treating FID as current is out of date.
Time to first byte (TTFB) isn't a Core Web Vital, but it sets the pace for everything after it. Google's rough guide is 0.8 seconds or less. Some guides quote 200 milliseconds, which isn't Google's published figure.
Speed affects sales, not only rankings. A Google-commissioned Deloitte study found that a 0.1 second gain across four mobile speed metrics lifted retail conversion rates by 8.4%. Speed is one input to how speed affects search visibility, and it won't rescue weak content.
8 ways to speed up your WordPress website
The fixes below are listed in the order worth tackling them. Google's guidance puts hosting first, and the hero image is the next big lever. The small tidy-ups come last because they rarely move the scores.
1. Choose faster hosting
Hosting sets the ceiling. If the server is slow to respond, no plugin can fully make up for it.
Hosting types and 4 questions to ask before you buy
On shared hosting, many sites compete for one server's resources. A VPS or cloud plan gives you a dedicated slice. Managed WordPress hosting adds caching, updates and backups handled by the host. Before you buy, ask four things:
- Which PHP version does the plan run, and is it current?
- Does the host cache full pages at the server level?
- Is the storage SSD or NVMe?
- Can you choose where the server sits?
Why server location matters in Melbourne and Australia
Distance adds delay. When Cloudflare began serving Australian traffic from Sydney in 2012, it reported ping times falling from over 160 milliseconds to under 40. A Melbourne business with Australian customers gains from a host with servers in Sydney or Melbourne, not the other side of the Pacific.
The same logic applies to a CDN. Cloudflare lists data centres in Auckland, Brisbane, Melbourne, Perth and Sydney, so Australian visitors can get cached files from nearby. To check your own site, run a test from an Australian location and compare the TTFB against that 0.8 second guide.
The trade-off is cost. Better hosting costs more than a budget plan, and it's worth paying for only if the test shows the server is the bottleneck.
2. Set up caching and a CDN
Page caching saves a finished copy of each page, so WordPress doesn't rebuild it for every visit. Use one page cache only, either at the host or through a plugin such as LiteSpeed Cache, WP Rocket or WP Super Cache. Two caches fighting each other cause odd bugs.
Object caching with Redis or Memcached stores database answers. It matters more for busy, dynamic sites like stores than for a small brochure site. A CDN keeps copies of your images, CSS and JavaScript near visitors. It won't fix a slow server or heavy scripts, though.
3. Optimise your images
Resize each image to the size it's actually shown, compress it, and use a modern format such as WebP. Oversized images are among the most common causes of slow loading.
The hero image needs special care. WordPress lazy-loads images by default, which delays them until they're needed. Since version 5.9 it skips the first content image, and since 6.3 it adds a high-priority hint to the first large image. WordPress's performance team found that hint typically improves LCP by 5 to 10%.
Themes and page builders often undo this. Ask a developer to check the page source and confirm the hero image isn't lazy-loaded and is marked high priority (the attribute is called fetchpriority). The site looks fine either way, which is why the mistake goes unnoticed.
4. Cut heavy plugins and page builders
Delete plugins you don't use. For the ones you keep, the free Query Monitor plugin shows which ones add slow database queries. Page builders such as Elementor and Divi start with more code than a lightweight or block theme, though a well-tuned builder site can still pass.
Removing a plugin can also remove a feature the business relies on, so check with whoever owns the site. Work on a staging copy, and take a backup first.
5. Reduce third-party scripts
Chat widgets, tag managers, ad pixels and social embeds each call outside servers. List what runs on your site and drop anything nobody uses. Keep the scripts that earn money. A chat widget, for example, can load only after a visitor interacts with the page.
6. Fix layout shifts
Layout shift happens when content jumps while the page loads. Give every image set dimensions, reserve space for banners and embeds, and load fonts from your own site. Cookie banners and ads can still cause shifts you only partly control.
7. Clean up your database
Post revisions, spam comments and expired temporary data pile up over time. A database clean-up plugin or your host's tools can clear them, and WordPress can cap future revisions. Don't expect this to rescue a slow site by itself. Back up first.
8. Speed up a WooCommerce store
Cart and checkout pages are personal to each shopper, so they can't be fully cached. Exclude them from the page cache, use object caching, and switch off cart scripts on pages that don't sell anything. Store owners weighing a rebuild can look at ecommerce website design built without a CMS.
How to reduce total blocking time in WordPress
Total blocking time (TBT) adds up every moment scripts tie up the browser for more than 50 milliseconds, so it can't respond to a click. To cut it, remove scripts you don't need, delay the non-essential ones and drop heavy plugins. Google suggests staying under 200 milliseconds on average mobile hardware.
TBT is a lab measure. Real responsiveness is INP, and Google's TBT guidance calls TBT a reasonable stand-in for INP in the lab, not a substitute for it. So fix TBT in testing, then confirm INP in Search Console.
Run the page through PageSpeed Insights. The report lists the scripts using the most time. Remove the ones you don't need. Delay the rest until a visitor interacts, which caching plugins like WP Rocket and script managers like Perfmatters can do page by page. Check page builder widgets too, since sliders and accordions often carry heavy JavaScript.
Test your menu, contact form and checkout afterwards. Delaying JavaScript can break all three.
What order should you fix things in?
Back up the site and work on a staging copy first. Record your PageSpeed Insights and Search Console numbers, then change one thing at a time and retest with the same tool and settings.
For most sites the order matches the list above: hosting and PHP, one page cache and a CDN, images with the hero image first, then plugins and page builders, third-party scripts, layout shifts and the database. A site that only fails on layout shift doesn't need to start with hosting. Search Console's real-visitor data updates slowly, so give it a few weeks before judging a fix.
Then keep checking. A monthly test, plus one after any plugin, theme or tracking change, catches slippage early. One new tag can undo a month of work.
How much does WordPress speed optimisation cost in Australia?
Prices vary widely. As of November 2026, one Australian provider publishes one-off speed packages from AU$199 for a small site to AU$399 for a WooCommerce store. That provider puts typical Australian developer rates at AU$80 to $150 an hour. Agencies and larger sites cost more. Check current prices before you budget.
Doing it yourself costs time and carries the risk of breaking something. A good quote should name the pages tested, show before-and-after Core Web Vitals, include a backup and a way to roll back, and say whether monitoring is included. Be wary of a guaranteed score. A 90-plus PageSpeed score doesn't mean you pass Core Web Vitals.
Getting speed help in Melbourne
If you'd rather hand this off, look for a Melbourne WordPress developer or hosting provider who will quote against the checklist above: real-visitor data first, fixes in order, a backup and a rollback plan. Ask to see before-and-after results from sites they've worked on.
Signs it's time to move off WordPress
Optimising has hit its ceiling when scores slip back after every plugin update, when you pay to fix the same problems twice, or when the site needs a builder and a pile of plugins just to stay usable. At that point a rebuild may cost less than another round of patches.
You have two main routes. One is a lighter WordPress build with a block theme and fewer plugins. The other is a site with no CMS to maintain, and we migrate WordPress sites to EffektAI for exactly that. EffektAI works that way: there are no plugins to patch, and a Lighthouse check runs on every deploy. Our comparison of EffektAI and WordPress sets out the trade-offs, and the no-CMS websites built on EffektAI page shows how they're built. Small teams can also look at websites for small businesses.
WordPress is still the right call when editors depend on its plugin ecosystem or when you need WooCommerce depth. Most slow sites don't need to leave. They need the fixes above, in order.
FAQs
Quick answers to the questions we hear most about WordPress speed.
Why is my WordPress site fast for me but slow for customers?
Your browser has already stored much of your site, so repeat visits feel quick. Customers on slower phones, networks or locations see the uncached version. Judge speed from real-visitor data in PageSpeed Insights or Search Console, not from your own laptop.
Which Core Web Vital should I fix first?
Fix the one that's failing in real-visitor data. If more than one fails, start with LCP, since a slow server delays everything that loads after it.
Can a caching plugin fix Core Web Vitals on its own?
No. Caching helps server response and often LCP, but images, scripts, fonts and layout shifts also affect the scores. WP Rocket's own Core Web Vitals guide says the same, so plan on caching plus the other fixes.
Does a 90 or higher PageSpeed score mean I pass Core Web Vitals?
Not necessarily. The score comes from a lab test, while the Core Web Vitals assessment uses real-visitor data when Google has it. A site can score well in the lab and still fail in the field.
How often should I test my website speed?
Monthly works for most sites. Test again after any plugin, theme or tracking change, because those are the usual causes of a sudden slowdown.
Still slowing down after every update?
If you've fixed what you can and the site still slows down with every update, it may be time to move on from WordPress. We migrate WordPress sites to EffektAI, so there are no plugins left to patch. Get in touch and we'll talk through whether a move makes sense for your site.