Performance 1 min read

How we cut a WordPress site LCP from 4.2s to 0.9s

A 40-product shop, a shared host on another continent and 38 plugins. The exact order of the fixes and what each was worth in milliseconds.

The starting point

Field data said 4.2 seconds at the 75th percentile. Lab data said 2.1. The gap was the whole story: the server was fine when idle and fell apart under real traffic.

What we changed, in order

  1. Moved to NVMe and enabled server-level caching.
  2. Converted 180 hero images to AVIF.
  3. Deferred three third-party scripts.

What did nothing

Minifying CSS saved 4 KB and zero milliseconds. Preloading a font that was already cached did the same.

The fastest request is the one you never make.

curl -w '%{time_starttransfer}' -o /dev/null -s https://example.com

Contact us