How to increase page speed in WordPress: the fixes that matter

To increase page speed in WordPress, measure the page first. Oversized images, slow responses and scripts that delay rendering are common bottlenecks, but unstable layout and interaction delays also matter. Use Lighthouse to diagnose a repeatable lab run and real-visitor Core Web Vitals to understand the experience your audience receives. Prioritise the measured problem, then retest the page and its essential functions.

Stop chasing the number. Read the breakdown.

When most people run PageSpeed Insights they see a red 48, panic, and start ticking off warnings top to bottom. That's backwards. Lighthouse hands you a list of thirty "opportunities" with no honest sense of which ones matter, so you can spend hours preloading a font and deferring a stylesheet and watch the score barely twitch.

Lighthouse combines metric scores using published weights. In Chrome's documented Lighthouse 10 table, Total Blocking Time carries 30%, Largest Contentful Paint and Cumulative Layout Shift each carry 25%, and First Contentful Paint and Speed Index each carry 10%. Layout stability deserves attention alongside load speed. Check the version in your own report because scoring can change.

Read the metric breakdown before changing settings. Does the page load slowly, shift as it renders or block interaction? Trace the largest measured problem to its cause. A diagnostic warning is useful when fixing it improves the experience, not merely because it appears in a list.

What contributes to the lab score?

  • Total Blocking Time (TBT)30%
  • Largest Contentful Paint (LCP)25%
  • Cumulative Layout Shift (CLS)25%
  • First Contentful Paint (FCP)10%
  • Speed Index10%
Published Lighthouse 10 weights, checked 5 November 2026. The field Core Web Vitals are LCP, INP and CLS; TBT is a lab metric, not field INP. Chrome scoring documentation.

The three fixes that actually move it

On a typical WordPress site, in the order I'd do them:

  1. Images: almost always the single biggest win. Nine slow WordPress sites out of ten are slow because someone uploaded a 4000-pixel-wide, 2MB photo straight off a phone and dropped it into the hero. The browser downloads the whole thing, then shrinks it to fit. Fix: resize images to the size they're actually displayed at, serve them as WebP, and let everything below the fold lazy-load. WordPress lazy-loads by default now, but the hero image must not be lazy-loaded; that's the one thing you want to arrive first. This alone often drags LCP from four seconds to under two.
  2. Caching plus a delivery layer in front. A WordPress page is built fresh from the database on every visit (PHP, MySQL, the lot), which is slow. Page caching turns that into a flat HTML file served instantly. That's your biggest server-side win and it fixes a slow Time To First Byte. Put a content delivery network in front (Cloudflare's free tier is genuinely fine for a small business site) and your assets get served from an edge close to the visitor instead of one box. One good caching plugin set up properly does this. You don't need three.
  3. Kill the render-blocking scripts and fonts. This is where page builders and plugin sprawl bite. Every plugin that adds its own CSS and JavaScript to every page (the contact form, the slider, the social icons, the cookie banner) adds weight the browser must deal with before it can paint. Defer or delay the JavaScript that isn't needed for the first view, only load each plugin's assets on the pages that use them, and self-host your fonts with font-display: swap so text shows immediately in a fallback rather than sitting blank. This is what drags blocking time down.

Those are common starting points, not a guaranteed jump to a particular score. Let the measurements decide the order, reserve image and embed space to prevent shifts, and retest after each change. A faster report is useful when the site also works better for its visitors.

The fixes that don't move the needle (but everyone obsesses over)

Here's where I'll take a position the speed-plugin marketing won't: a stacked "all-in-one optimiser" with every checkbox ticked is usually a downgrade. Same logic as a cheap WiFi booster: it looks like the obvious fix and it quietly makes things worse. Combining and minifying every file, inlining critical CSS, "removing unused CSS": these are real techniques, but on a normal WordPress site they're where people lose a weekend and break their layout for a two-point gain.

The cookie banner nobody weighs

Here's a cost that hides in plain sight: the cookie-consent banner. It gets waved through every pagespeed conversation because it feels like a legal box to tick, not a performance choice, so nobody counts its weight. But a heavyweight third-party consent platform loads its own JavaScript on every single page before the visitor does anything, and it lands right in the critical path where it drags your blocking time.

A lightweight consent interface may reduce script weight, but its size does not establish compliance. Google Consent Mode changes tag behaviour using the consent states your site supplies; it does not itself collect a valid choice or decide which rules apply. Assess how choices are collected, stored, updated and enforced across every tag. Test default, accept, reject and later-change paths before replacing a consent platform. Google explains the technical roles.

Lab score vs the score Google actually uses

Lighthouse is a lab test under specified conditions. Google says Core Web Vitals are used by its ranking systems, while a good score does not guarantee a high position. Field LCP, INP and CLS describe real visits; a lab score helps diagnose one run. Check both, using the Search page-experience guidance rather than treating either as the whole ranking system.

So treat the Lighthouse number as a workshop tool, not the goal. The goal is green field vitals from your real audience. If your lab score is mediocre but Search Console says your vitals pass, you're done. Go and write content instead.

Test like an Australian visitor, not like a developer

Most WordPress sites I'm handed test fine on the owner's machine and badly in the wild, for one reason: the owner is on a fast connection and a powerful laptop, and their customers aren't. A real slice of Australian traffic is on a mid-tier phone, on mobile data or a busy NBN connection at dinnertime, possibly a long way from the nearest data centre. That's the device and the line to optimise for. So read the mobile tab and the field-data panel in PageSpeed Insights, not just the lab gauge, and open your own site on your phone off WiFi and count the seconds until you can read the headline. Fix for the slowest realistic visitor and everyone faster comes along for the ride.

What I'd actually do, start to finish

If it were my site: compress and right-size the hero and the heaviest images first, and make sure the hero isn't lazy-loaded. Install one reputable caching plugin, turn on page caching, and put Cloudflare's free tier in front. Then go through the plugins, stop the ones that don't belong on a page from loading there, and self-host the fonts. Re-test on the mobile tab, watch the field data over the next couple of weeks, and stop the moment it's green. That's the whole job: an afternoon's work in the right order, not a renovation. PageSpeed is one piece of the picture; our guide on how to show up in AI search covers how speed, content and rankings fit together, and once the site's fast it's worth getting your spare domains pointed at the main site the right way. Keep any redirect chain short while you are there, because each extra hop costs a round trip before the page starts loading, and our guide on canonical tags versus 301 redirects covers when a redirect is the wrong tool altogether.

Done all that and your WordPress site still drags? That's usually a theme or page builder doing far too much, or hosting that's slow before a single image loads. Worth a proper look rather than another plugin. That is the rescue work on our WordPress developer in Sydney page. We'll read your real Lighthouse and field data, tell you straight which fixes will help yours, and sort it without selling you gear you don't need. Send us your site's address and we'll tell you where the time is going.

Where this comes from

The primary sources behind the above, so you can check any of it yourself rather than take our word for it:

Frequently asked questions

How do I increase page speed in WordPress?

Measure first, then address the largest causes of slow rendering, blocked interaction and layout shifts. Common fixes include correctly sized images, appropriate page caching and fewer unnecessary scripts. Retest important functions and compare real-visitor LCP, INP and CLS as well as the lab report.

How do I fix "ensure text remains visible during webfont load" in WordPress?

Add font-display swap so the browser shows text in a fallback font while your webfont loads. If the font is enqueued by your theme, a performance plugin (or a small CSS override with font-display: swap in the @font-face rule) fixes it; for Google Fonts, load them with display=swap in the URL, or self-host the two weights you use. The warning is worth clearing because it is render-blocking text, not a cosmetic point.

Does a perfect 100 Lighthouse score matter for WordPress SEO?

A perfect lab score is not a ranking guarantee. Google uses Core Web Vitals among many signals, and real visits can differ from a simulated run. Improve the experience for your audience and use the lab report to diagnose specific problems, rather than treating 100 as the business goal.

Will a caching plugin fix my WordPress speed on its own?

It helps a lot, but not on its own. Page caching turns a slow database-driven page into a flat file, the single biggest server-side win. But it does nothing for oversized images or render-blocking scripts in the browser, and stacking a second optimisation plugin on top usually causes more conflicts than gains. One good caching plugin, configured properly, plus image and script fixes, not three plugins fighting each other.

Why is my WordPress site slow on mobile but fine on desktop?

Because Lighthouse and most real Australian visitors test on a throttled mobile connection, and a phone has far less processing power than your laptop. Heavy page builders, big hero images and a pile of JavaScript that your desktop shrugs off will choke a mid-range phone on a patchy mobile or NBN connection. Fix for the slowest realistic device, not the machine you build on.

Should I switch hosting to make WordPress faster?

Only after caching, images and scripts are sorted, and only if the server response time (Time To First Byte) is genuinely slow. Cheap shared hosting that takes over a second just to start sending the page is worth leaving. But moving host while the real problem is a 2MB hero image and a bloated page builder just moves the slow site to a new address. If you want the three fixes done rather than explained, that is what our hosting and care plans are for.