If Google Search Console is flagging your pages as “Poor” or “Needs improvement,” you are not stuck. Core Web Vitals look technical, but most WordPress sites that fail them fail for the same handful of reasons. I have been building and fixing WordPress sites since 2008, and these five fixes are the ones I reach for first on client sites because they move the numbers fastest.
This guide is written for business owners and marketing managers, especially at medical and dental practices, credit unions and professional service firms, whose website is supposed to bring in calls, bookings and applications. For each fix I will explain what it does, which metric it improves, and when it makes sense to hand it to a professional instead.
What Core Web Vitals measure, and the scores you need
Core Web Vitals are three measurements Google uses to judge how a page feels to a real visitor: how fast the main content appears, how quickly the page responds when someone taps or clicks, and how much the layout jumps around while it loads.
| Metric | What it measures | Good score |
|---|---|---|
| LCP (Largest Contentful Paint) | How long the biggest image or block of text takes to appear | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How quickly the page reacts to a click, tap or keypress | Under 200 milliseconds |
| CLS (Cumulative Layout Shift) | How much content moves around while the page loads | Below 0.1 |
Those thresholds come from Google Search Central. Google measures them from real Chrome visitors, and a page is judged on its 75th percentile, which means at least three out of four visits need to hit the good mark. Interaction to Next Paint replaced First Input Delay as the responsiveness metric in March 2024, so any guide still talking about FID is out of date.
How to check your Core Web Vitals before you change anything
- PageSpeed Insights. Enter the address of one page. The section at the top, “Discover what your real users are experiencing,” is real-visitor data from the last 28 days, and that is what Google uses. The performance score below it is a lab test, which is great for finding the cause of a problem.
- The Core Web Vitals report in Google Search Console. It groups similar pages as Good, Needs improvement or Poor, separately for mobile and desktop, so you can see whether one template is dragging down dozens of pages at once.
Start with mobile. Most visitors are on phones, and mobile is where pages usually fail. Write down which metric is failing, because each fix below targets a specific one.
5 ways to improve Core Web Vitals on a WordPress site
1. Stop YouTube embeds from loading until someone presses play
A standard YouTube embed loads the full video player, a stack of scripts and connections to several Google servers the moment the page opens, whether or not anyone watches. On a page with two or three videos, that is often the single biggest drag on load time and responsiveness.
The fix is called a facade. The page shows the video thumbnail with a play button and only loads the real player when someone clicks it. Visitors see the same thing they saw before. The page just stops paying for the video up front.
- Turn on the YouTube preview or iframe lazy-load option in a performance plugin such as Perfmatters or WP Rocket. Both replace the embed with a thumbnail until it is clicked.
- If your developer prefers a lightweight approach, Paul Irish’s Lite YouTube Embed does the same job with a small script and no plugin.
- If the video sits at the very top of the page, make sure its thumbnail is a properly sized image so it does not become a slow LCP element itself.
Improves: LCP and INP.
2. Load fewer fonts, and host them yourself
Every font family and every weight is a separate file the browser has to download before your text looks right. Themes and page builders make it very easy to end up with three families and eight weights without noticing. Text that waits on a font delays LCP, and text that swaps from a fallback font to your brand font late can shift the layout.
- Keep it to two families and only the weights you actually use, often regular, bold and one more.
- Serve the font files from your own server instead of calling Google Fonts on every page view. Divi has a setting for this in recent versions, and plugins such as OMGF handle it for most other themes.
- Use WOFF2 files with
font-display: swapso text appears immediately in a fallback font. - Preload the one font used in your main heading so the most visible text renders first.
Improves: LCP and CLS.
3. Make your hero image the first thing that loads
On most business sites the LCP element is the large image at the top of the page: a hero photo, a banner or the first slide of a slider. If that image is oversized, lazy-loaded or waiting on a slider script, LCP suffers no matter what else you fix.
- Size the image to how it actually displays. A hero shown at 1,600 pixels wide does not need a 5,000-pixel original from the photographer.
- Convert it to WebP and compress it. I aim for under 150 KB for a hero image.
- Do not lazy-load it. Lazy loading is helpful for images further down the page and harmful for the first one. WordPress tries to skip lazy loading on the first image, but some themes and plugins override that.
- Give it priority with
fetchpriority="high", which tells the browser to download it before anything else. Recent versions of WordPress add this automatically to the likely hero image, but page builders do not always pass it through. - Replace a slider with one strong image. Sliders delay the first image and very few visitors click past the first slide.
If you have a whole media library to clean up, my guide on how to bulk optimize images for faster web pages walks through doing it in batches instead of one at a time.
Improves: LCP.
4. Reserve space so nothing jumps while the page loads
Layout shift is the moment you go to tap a button and the page moves under your finger. It almost always comes from something that arrives late and pushes content down.
- Images and video embeds without dimensions. Give every image a width and height, or an aspect ratio, so the browser saves room for it before it arrives.
- Cookie banners, announcement bars and chat bubbles that slide in at the top. Overlay them at the bottom of the screen instead of pushing the page down.
- Fonts that swap late. Fix 2 takes care of most of this.
- Review widgets, booking calendars and ads. Place them in a container with a set minimum height so the space is held while they load.
Improves: CLS.
5. Cut the JavaScript you do not need, and delay the rest
INP measures how quickly the page responds. When a visitor taps your menu or a form field and nothing happens for a beat, the browser is usually busy running JavaScript: plugins, tracking pixels, chat tools, review widgets and heatmaps, all competing at once.
- Remove plugins you no longer use, then check what each remaining plugin loads on the front end of the site.
- Load scripts only where they are needed. A booking widget does not need to load on every blog post. The script manager in Perfmatters can switch scripts off page by page.
- Delay third-party scripts such as chat, heatmaps and social feeds until the visitor scrolls or interacts. Most performance plugins have a delay JavaScript option. Test every form, booking button and tracking tag afterward.
- On Divi sites, review the Performance settings in Theme Options so each page loads only the CSS and JavaScript it uses.
If you would rather keep your plugin count low, here is how I speed up a WordPress website without plugins. For Divi users, my Divi 5 review covers how the new version changes performance.
Improves: INP, and often LCP.
The fix underneath all five: every change above assumes your server answers quickly. If the time to first byte is slow, every metric starts behind. Good hosting with server caching and a CDN fixes that, and it is often the cheapest speed improvement available. I wrote about why I moved client sites in my Rocket.net hosting review.
How long until Google shows the improvement?
The Search Console report is built from real visitor data over a 28-day window, so changes do not show up overnight. Once you fix a group of pages, start validation in the report and Google will track those pages for the next 28 days. The lab test in PageSpeed Insights shows a difference right away, which is a good way to confirm a change worked while the real-visitor data catches up. Google’s web.dev team keeps an up-to-date list of the most effective ways to improve Core Web Vitals if you want the developer-level detail.
Do Core Web Vitals affect SEO?
Yes, but they are not a shortcut to the top of Google. Google says good Core Web Vitals line up with what its ranking systems reward and recommends that site owners achieve them, but it does not publish how much weight they carry, and a fast page with thin content will not outrank a slower page that answers the question better. Where speed pays off most is after the click: fewer people leave before the page loads, and more of them fill out the form or book the appointment. That is why I treat speed as part of SEO that brings in leads, not as a separate checklist.
When to fix it yourself, and when to get help
Fixes 2 through 4 are reasonable to tackle yourself if you are comfortable inside WordPress, and the tools above will get you most of the way. Fixes 1 and 5 are where sites break: delaying the wrong script can stop a contact form, a booking calendar or your conversion tracking without any visible error. If your website brings in patients, members or clients every day, test changes on a staging copy before they go live.
If you would rather hand it off, this is part of my WordPress website management. I test your real pages, fix what is failing on a staging copy, check every form and tracking tag, and keep watching the report afterward. You work with me directly from start to finish, so you always know what changed and why. If you are not sure where your site stands, a marketing and SEO audit is a good first step, or you can send me a message and I will take a look.
Frequently asked questions about Core Web Vitals
How do I pass the Core Web Vitals assessment?
A page passes when at least 75% of real visits over the last 28 days score good on all three metrics: Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift below 0.1. Find the failing metric in PageSpeed Insights, apply the matching fix, then give the real-visitor data 28 days to catch up.
What is a good Core Web Vitals score?
There is no single combined score. Each metric is graded on its own as good, needs improvement or poor, and you want good on all three. The 0 to 100 performance score in PageSpeed Insights is a lab score, which is useful for finding problems but is not the Core Web Vitals assessment.
What is a good LCP score?
2.5 seconds or less. Between 2.5 and 4 seconds needs improvement, and anything over 4 seconds is poor.
What are the three Core Web Vitals?
Largest Contentful Paint (how fast the main content loads), Interaction to Next Paint (how quickly the page responds when someone clicks or taps) and Cumulative Layout Shift (how much the layout moves while it loads).
Why does my site pass in PageSpeed Insights but fail in Search Console?
The performance score in PageSpeed Insights comes from one simulated test. Search Console uses 28 days of real visitors on their own phones and connections, which are often slower than the test. Go by the real-visitor section at the top of PageSpeed Insights, because that is what Google uses.
Can a Divi website pass Core Web Vitals?
Yes. Divi sites pass when the theme's performance settings are on, images and fonts are handled carefully, and third-party scripts are kept under control. In my experience the theme is rarely the only problem; it is usually the combination of plugins, embeds and oversized images layered on top of it.
Heather Valencia founded Ravenous Raven Design in 2008 and has built and optimized WordPress websites ever since. She works one-on-one with every client on web design, SEO and Google Ads.
0 Comments