A practical Core Web Vitals plan for enterprise WordPress
Most slow WordPress sites share the same five causes. Here is the order we fix them in, and how we stop the site from getting slow again.
By Seahawk Engineering Team 2 min read
Core Web Vitals reports tend to arrive as a wall of red. Largest Contentful Paint is slow, layout shifts on load, and interactions feel sluggish. The temptation is to install another optimization plugin. On enterprise sites that usually makes things worse.
After auditing a lot of large WordPress installs, we see the same causes over and over. This is the order we tackle them in.
1. Cache the page before you optimize the page
If logged-out visitors are hitting PHP on every request, nothing else matters yet. Time to first byte eats most of your LCP budget before the browser has seen a single tag.
Put full-page caching at the edge (Cloudflare, or your managed host’s CDN), and tie cache purges to publishing events so editors never see stale content. For logged-in traffic and uncacheable requests, add a persistent object cache such as Redis.
2. Find the LCP element and make it boring
On most templates the LCP element is a hero image or a headline. Make sure it:
- is in the initial HTML, not injected by JavaScript or a slider plugin
- has explicit
widthandheightattributes - is not lazy-loaded, and has
fetchpriority="high"if it is an image - is served in a modern format at the size it is displayed
That one element often accounts for most of the LCP gap.
3. Reserve space for everything
Layout shift on WordPress sites usually comes from images without dimensions, ads and embeds without reserved slots, cookie banners that push content down, and web fonts swapping in with different metrics. Each has a direct fix: set dimensions, reserve slots with CSS, overlay banners instead of inserting them, and use a metric-matched fallback font.
4. Audit JavaScript by plugin, not by file
Interaction delays come from main-thread work. Group your scripts by the plugin that loads them and ask whether each plugin needs to run on every page. Sliders, social feeds, and form plugins are common offenders that load everywhere but are used on two templates.
5. Set a budget and enforce it
Fixing performance once is easy. Keeping it fixed is the hard part. We set a budget for page weight, JavaScript, and LCP at the start of each project, then check it automatically on every pull request. A regression fails the build, the same way a broken test would.
What to expect
On most of the sites we audit, the first two steps deliver the majority of the gain. If your team wants a second opinion on a Core Web Vitals report, talk to one of our engineers.