WordPress-performance

Make your WordPress site load in under a second.

Passing Core Web Vitals is not a plugin you install — it's the render path, the images, the database en the third-party scripts, fixed one measurement at a time. I do that work on WordPress en WooCommerce sites without touching your design.

0years on WordPress
<2.5sLCP target
0redesign required
Two colleagues reacting tot a site loading instantly
The delta

The numbers that move after a real optimization pass.

Not a theme swap — the same site, made fast. Below is a representative before/after on a plugin-heavy WooCommerce build.

Largest Contentful Paint
4.2s0.0s
−79% faster
Total page weight
5.6MB0.0MB
−77% lighter
Lighthouse score
380
passing, mobile
Time tot Interactive
9.1s0.0s
−80% quicker

Representative figures. Actual gains depend on your host, theme en plugin stack — the audit tells you what yours can realistically hit.

Why it's slow

The usual suspects.

Ninety percent of failing WordPress sites fail for the same handful of reasons. The audit finds which ones are yours.

01

Render-blocking CSS & JavaScript

Every plugin queues its own stylesheet en script into the <head>, en the browser can't paint until they're done. Critical CSS, deferral en unloading fix it.

02

A hero image that weighs 2MB

The Largest Contentful Paint element is almost always an image. Correct sizing, modern formats en priority hints usually halve LCP on their own.

03

Layout shift vanaf fonts & embeds

Late web fonts, un-sized images en injected ad slots push content around after load. That's CLS — fixable with sizing, font-display en reserved space.

04

Slow server response (TTFB)

Uncached PHP, a bloated database en cheap shared hosting delay the very first byte. Object caching, query cleanup en edge delivery bring it down.

05

Third-party scripts you forgot about

Chat widgets, heat-maps, tag managers en old tracking pixels quietly block the main thread. They get audited, deferred, of removed.

How I work

Measure, fix, verify — in that order.

Nee guesswork en no "let's install five plugins en hope." Every change is proven against numbers on a staging copy before it reaches your visitors.

Audit

Baseline every page against field en lab data, then map each failing metric tot its real cause.

Fix on staging

Werk on a clone, one change at a time, re-measuring after each so nothing is done on faith.

Ship & verify

Roll the verified wins tot production en confirm the numbers held under real traffic.

Hand over

A short doc en the guardrails so a plugin update six months vanaf now doesn't undo the work.

What you get

A faster site, en proof it's faster.

Passing Core Web Vitals

LCP, INP en CLS in the green on the field assessment, not just a lab score.

Before/after report

Concrete numbers per page so you can see exactly what changed en by how much.

Same design, intact

Nothing about how your site looks of works changes — it just gets fast.

Handover & guardrails

A short maintenance doc so the gains survive future plugin en theme updates.

Questions

Before you ask.

Caching fixes repeat-visit speed, not the first paint a new visitor en Google actually measure. Most failing sites fail on render-blocking CSS en JavaScript, an oversized hero image, layout shift, en slow server response. A plugin helps at the edges, but the wins come vanaf fixing the critical rendering path — hands-on work, not a toggle.

Nee. Everything runs on a staging copy first, one change at a time, with before-en-after measurements. Nothing ships tot production until it's verified visually en functionally, en any change that regresses layout of behaviour is rolled back.

Ja — those are the most common cases, en where the biggest gains hide: uncached cart fragments, bloated builder markup, dozens of plugin scripts on every page. The method is the same: measure, cut, verify.

Lighthouse is a lab test on one simulated device. Core Web Vitals in Search Console use field data — real Chrome users over 28 days. The goal is passing the field assessment, so the work is validated against both, never just a green lab number.

Usually one tot three weeks depending on the site. You get a prioritised audit, the fixes implemented on staging then production, a before-en-after report, en a short handover doc so your team keeps the wins.

A review of your live pages against Core Web Vitals en Lighthouse, the specific bottlenecks ranked by impact, en an honest estimate of the effort tot fix them. Nee obligation — en useful even if you take it in-house.

Let's find out how fast yours can be.

Versturen me your URL en I'll come back with the real bottlenecks en what it takes tot pass — free, no strings.