WordPress speed optimisation — also called WordPress performance optimization — is the systematic process of reducing page load time and lifting Core Web Vitals scores so your site ranks higher in Google, converts more visitors and lowers paid-traffic costs. I benchmark baseline performance with Google PageSpeed Insights, Lighthouse, and WebPageTest, then fix every identified bottleneck — caching, image delivery, code minification, database overhead and plugin bloat — until LCP is under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. Most sites reach Lighthouse 90+ within one to two weeks.
Who it's for
What's included
Why does my site feel slow when PageSpeed says it's fine?
PageSpeed Insights runs a lab test: one simulated phone, one location, an empty cache. Google ranks on field data from real Chrome users, scored at the 75th percentile of page loads. So a site can pass the lab test while logged-in customers, cart pages and older phones still wait several seconds.
My audit measures both, on the templates that make you money: homepage, main landing pages, product, cart and checkout, logged out and logged in. I record server response time (TTFB) on uncached requests and trace the PHP and database work behind the slowest pages. Google's thresholds for a good experience are LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1 (web.dev).
What slows a WordPress site down the most?
Usually the server, before anything you can see. If WordPress needs two seconds to build a page, compressing images barely registers. Next come oversized images and fonts, then third-party scripts such as chat widgets and ad pixels, then plugins running heavy queries on every request. I fix them in that order, biggest gain first.
- Server response: page and object caching, a current PHP version, and rewriting slow queries in the theme or plugins. A CDN such as Cloudflare helps visitors far from your server, but it can't speed up a slow origin.
- Images and fonts: correct dimensions, responsive sizes, WebP or AVIF, lazy loading below the fold, and the hero image loaded first. Most sites ship more font files than the design uses.
- Third-party scripts: I go through each tag with whoever owns it, then delay it, switch it to click-to-load, or keep it off checkout. Tracking your reports depend on stays.
- Plugins and the database: one plugin with a bad query hurts more than thirty light ones, so I check what each one does per request. Anything I remove is backed up and tested on staging first.
When is a rebuild better than more speed optimisation?
When the slowness is built into the site: an unsupported theme, one page builder stacked on another, or years of plugins added to patch symptoms. At that point each extra fix costs more and gains less, and a focused rebuild on a lighter theme usually works out cheaper within a year or two.
The audit shows which route pays back best: tuning, a hosting move, refactoring the theme, or a rebuild. A rebuild keeps your content and design and moves them onto a custom theme with ACF fields and custom blocks. That took a UK fashion store from 6.1 seconds to 1.4 seconds on mobile. On an ad-heavy news site, I fixed Core Web Vitals without cutting ad revenue.
How the process works
Audit & baseline
I benchmark your site with Google PageSpeed Insights, Lighthouse, and WebPageTest — measuring LCP, INP, CLS, TTFB and total blocking time — then document every bottleneck before touching a single setting.
Quick wins
Caching, image optimisation, CDN, and plugin configuration fixes that deliver the biggest gains first — usually delivering measurable PageSpeed improvement within the first two days on staging.
Deep optimisation
Code-level, database and render-path tuning: JavaScript deferral, CSS inlining, database index review, and query cache — all done on a staging copy so the live site is never at risk.
Verify & hand over
I re-test on both desktop and mobile, confirm LCP, INP and CLS are in the green, document every change, and give you a before/after report you can share with stakeholders.
Common questions
No. I work on a staging copy and test every change thoroughly before anything goes live. Your design and content stay exactly as they are — only the under-the-hood performance changes. A full WPVivid backup is taken before any optimisation work begins, so rollback is instant if needed.
Most sites are fully optimised within one to two weeks. Quick wins — caching, image conversion to WebP, plugin deactivation — typically land within the first two to three days on staging. Database and code-level optimisation follows in a second pass, and the final re-test confirms Core Web Vitals in the green before we go live.
I target Lighthouse 90+ on both desktop and mobile, and Core Web Vitals in the green (LCP under 2.5s, INP under 200ms, CLS under 0.1) — but the achievable ceiling depends on your hosting infrastructure, third-party scripts (Google Analytics, Facebook Pixel, live chat), and theme complexity. I share a clear before/after report with verified PageSpeed Insights screenshots for every engagement. If your hosting is the hard limit, I'll tell you honestly and can handle the migration to faster infrastructure as part of the same project.
Yes — Core Web Vitals (LCP, INP, and CLS) are a confirmed Google ranking signal under the Page Experience update, weighted in the algorithm alongside content quality and backlinks. Faster pages also lower bounce rates and improve conversion rates: Google's research shows a 1-second delay in mobile page load time reduces conversions by up to 20%. For WooCommerce stores, checkout page LCP improvements routinely produce measurable revenue uplifts. Speed work also compounds with a well-built custom theme — lighter theme code means caching and CDN can do their job without fighting page-builder overhead.
Not always. I optimise what you have first — enabling Redis or Memcached object caching, upgrading PHP to 8.2/8.3, configuring WP Rocket or W3 Total Cache, and setting up Cloudflare CDN. If your host's infrastructure is the real bottleneck (shared hosting, old LiteSpeed or Apache without HTTP/2, no object cache support), I'll tell you directly and can handle a zero-downtime migration to a better host. Switching to managed WordPress hosting like Kinsta, WP Engine, or Cloudways often delivers an additional 30–50% load time improvement beyond plugin-level optimisation alone.