WordPress can be fast. The reason most sites are not is a stack of small, fixable mistakes - not the platform itself. Here is the playbook we run on real projects to get Core Web Vitals into the green.
Hosting first, plugins second
Cheap shared hosting will sabotage every other optimisation. We move clients to a host with a real PHP runtime, object cache, and ideally edge caching - Kinsta, WP Engine, Rocket.net, or a tuned VPS. This single change often shaves 500ms off TTFB.
Fix the LCP image
Largest Contentful Paint is almost always a hero image. The fixes are unglamorous and decisive:
- Serve modern formats (WebP or AVIF).
- Set explicit width and height attributes to avoid layout shift.
- Use
fetchpriority="high"on the LCP image. - Preload it in the head.
- Resize - a 2400px image displayed at 800px is wasted bandwidth.
A correctly served LCP image on a decent host gets most marketing sites under 2.5s on its own.
Stop loading JavaScript you do not use
Audit the front page in the network tab. Every script that loads is a tax. Common offenders: full jQuery on a site that does not need it, unused page builder JS, chat widgets loaded synchronously, four analytics scripts where one would do. Defer or remove ruthlessly.
Inline critical CSS, defer the rest
Most themes load the entire stylesheet in the head, blocking render. Tools like Critical CSS plugins, or build-time generation, get the above-the-fold styles inline and defer the rest. The visual difference on first paint is dramatic.
Use a real cache
Page caching is the easiest performance win in WordPress. WP Rocket, LiteSpeed Cache, or the host-level cache. Add object caching with Redis if the host supports it. Logged-in performance is a separate problem - solve front-end first.
Watch CLS like a hawk
Cumulative Layout Shift is almost always: ad slots without dimensions, late-loading fonts, embeds without aspect ratios, or hero images without width and height. Each one is a five-minute fix. Together they make the difference between “feels janky” and “feels solid.”
INP: the new villain
Interaction to Next Paint replaced FID, and it is harsher. Heavy event listeners, blocking JavaScript, and oversized React or Vue widgets in WordPress themes all hurt INP. Audit with the Chrome DevTools performance tab on a real interaction, not just a load.
Measure on real users
Lighthouse is a useful lab tool, but Google ranks on real-user data via the Chrome User Experience Report. Install a real-user monitoring tool - PageSpeed Insights’ field data view, or a tool like SpeedCurve - and watch the trend. The lab score is the dashboard; the field score is the truth.
A WordPress site that hits green Core Web Vitals is not magic. It is a disciplined run through this list, and a willingness to remove the things that do not earn their weight.
Tags