GUIDE
Slow WordPress is rarely one villain. It is usually uncached pages, oversized images, a bloated database, too many plugins and a chatty front end. Fix those in order and Core Web Vitals follow.
Every extra second of load time costs conversions. Google uses speed as a ranking signal, and mobile visitors leave quickly when nothing useful appears. You do not need a rewrite to improve most sites — you need measurement, then disciplined changes that do not break the design.
Work on a staging copy when you can. Take a backup before caching or optimisation plugins touch production. Change one major layer at a time so you know what helped. Resist the urge to install five “speed booster” plugins at once; they overlap, conflict, and make rollbacks painful.
Prioritise the templates that earn money or leads: home, key landing pages, product pages and the blog posts that already rank. A perfect score on an unused archive page helps nobody if checkout still crawls.
Open PageSpeed Insights with your real URL on mobile and desktop. Note Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS), plus the opportunity list. Save a GTmetrix or WebPageTest run as a second opinion. Write down the numbers — without a baseline you cannot tell whether you improved anything.
Look at Time to First Byte (TTFB) as well. If the server takes ages to respond, theme tweaks will not save you; hosting or uncached dynamic pages are the bottleneck. WooCommerce cart and account pages are often slow by nature — measure a typical marketing page and a product page separately.
Anonymous visitors should receive a cached HTML page, not a fresh PHP bootstrap on every hit. Use your host’s native page cache when it is solid, or a well-supported caching plugin configured for your stack. Exclude carts, checkouts and personalised pages so ecommerce does not serve the wrong content.
Object caching (Redis or Memcached) helps busy dynamic sites once page cache is in place. Clear caches after plugin updates and major content edits. Two caching plugins fighting each other is a classic way to create mysterious breakage — pick one approach and document it.
Images are still the heaviest asset on most WordPress sites. Before upload, resize to the largest size you actually display. Compress JPEGs and PNGs. Serve modern formats such as WebP or AVIF where the toolchain supports them. Lazy-load below-the-fold images so the LCP image can win the network.
Check the LCP element in PageSpeed — if it is a hero image, optimise that file first. Swap giant PNG screenshots for compressed alternatives. Remove decorative full-width videos that autoplay on mobile unless they are essential to the offer.
Revisions, spam comments, expired transients and leftover options from deleted plugins inflate the database and slow admin and front-end queries. Use a maintained cleanup tool carefully, or clean known tables manually if you know what you are doing. Always backup first.
Deactivate and delete plugins you do not use. Each plugin can add queries, scripts and HTTP requests. Page builders, related-posts widgets and heavy analytics suites are frequent offenders. Prefer one good plugin over three mediocre ones that overlap. Delete unused themes except a default fallback.
In the admin, open the browser network panel on a slow front-end page and sort by size and time. You will usually find a handful of third-party scripts (tag managers, heatmaps, chat) that dwarf your theme CSS. Delay or remove what marketing does not actually use. The same audit often reveals duplicate jQuery copies or a slider library loaded site-wide for a single homepage module.
Speed optimisation starts from €199: full performance audit, caching, images, database and code work, CDN and font tuning where needed, a before/after report, and a guaranteed 30%+ faster load time — or your money back. The work is non-destructive and covered by a 30-day guarantee.
from €199
Get speed optimisation →WordPress themes and plugins often dump CSS and JS into the critical path. Defer non-critical scripts, delay third-party tags (chat widgets, embedded maps, ad scripts) until interaction or idle time, and avoid loading a slider library on pages that never use it.
Critical CSS tools and “remove unused CSS” features can help, but they also break designs when over-eager. Test every template: home, post, product, checkout. If a layout collapses, undo that optimisation immediately. Professional passes treat front-end fixes as controlled changes with verification, not a single checkbox.
Combine CSS and minify only when your toolchain is stable. On modern HTTP/2 hosts, dozens of tiny files hurt less than they used to; broken minification that strips a required selector hurts more. Prefer “defer non-critical” over “concatenate everything” unless you have measured a real win.
A content delivery network serves static assets from locations closer to your visitors and often helps with image formats and HTTP/2 or HTTP/3. Point media and theme assets through the CDN once DNS and SSL are correct. Purge the CDN when you deploy visual changes.
Fonts affect both LCP and CLS. Limit families and weights, subset characters when you can, self-host fonts instead of chaining multiple third-party requests, and use sensible font-display behaviour so text appears without jumping. Icon fonts that load an entire library for three icons are worth replacing with SVG.
Re-run the same benchmarks on the same URLs. Compare LCP, INP, CLS and fully loaded time to your baseline. If TTFB is still poor after caching, talk to the host or plan a migration — shared servers with noisy neighbours and old PHP versions have a ceiling no plugin can break.
Keep PHP on a supported version your theme and plugins allow. Enable compression (Brotli or gzip) and browser caching headers at the server or CDN. For WooCommerce, consider dedicated object cache and a host that understands persistent carts. Turn off excessive heartbeat polling and heavy admin-ajax chatter on the front end when plugins allow it — those background calls quietly ruin INP on content pages.
Deeper rebuilds — template refactors, query fixes, custom checkout performance — are quoted after an audit when a simple pass is not enough. That is normal for large catalogues and ageing page-builder sites; it is not a failure of caching. Know when you have reached the ceiling of configuration tweaks.
Bring in help when:
A full speed optimisation pass starts from €199. It includes a performance audit (PageSpeed / GTmetrix), caching setup, image compression with modern formats, database cleanup, render-blocking CSS/JS fixes, CDN and font tuning where useful, and a clear before/after report. The improvement target is a guaranteed 30%+ faster load time, with a 30-day guarantee on the work. Design and functionality stay intact — the optimisation is non-destructive and tested.
If the site is down entirely rather than slow, start with WordPress white screen of death: 7 fixes. If slowness arrived overnight with redirects or Safe Browsing warnings, read WordPress site hacked: what to do before you chase performance plugins. All guides are listed on the Guides hub.
Keep Core Web Vitals green — speed checks and performance fixes continue every month.
Daily backups · Security monitoring · Priority support · Monthly report
Plans from €29/mo — most clients pick Pro at €59/mo