Search Console shows a red “Poor URLs” warning under Core Web Vitals. PageSpeed Insights gives your home page a score in the 30s. You know speed matters for rankings and leads, but the reports are full of terms like LCP, INP and CLS, and it’s not clear what to fix first.
This guide makes Core Web Vitals optimization practical. You’ll learn what each metric measures, how to find the real cause of a poor score and the fixes that make the biggest difference on typical small business sites, especially WordPress.
Quick answer: Core Web Vitals optimization means improving three metrics: LCP (loading, aim for 2.5 seconds or less), INP (responsiveness, 200 milliseconds or less) and CLS (visual stability, 0.1 or less). Speed up your server and hero image for LCP, cut heavy JavaScript for INP, and reserve space for images, ads and fonts for CLS.
The Three Metrics and Their Targets
Google’s Core Web Vitals guide sets these “good” thresholds, measured at the 75th percentile of page loads on mobile and desktop:
| Metric | Measures | Good | What usually hurts it |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content loads | 2.5 s or less | Slow hosting, huge hero images, render-blocking files |
| INP (Interaction to Next Paint) | How fast the page responds to taps and clicks | 200 ms or less | Heavy JavaScript, bloated plugins, third-party scripts |
| CLS (Cumulative Layout Shift) | How much the layout jumps around | 0.1 or less | Images without sizes, ads, late-loading fonts and banners |
The 75th percentile part matters. Your page needs to be good for most real visitors, including those on slower phones and networks, not just on your office Wi-Fi.
Step 1: Find Where the Problems Are
Don’t guess. Start with real user data.
- Search Console Core Web Vitals report. Shows groups of URLs with poor or “needs improvement” scores, split by mobile and desktop. Fix templates, not single pages.
- PageSpeed Insights. Test one URL from each problem group. The top section shows real user data when enough exists; the lower section is a lab test with specific suggestions.
- Your own phone. Load the page on mobile data and tap around. You’ll often feel the problem before you find it in a report.
Most small business sites have only a few templates: home, service page, blog post and contact. Fixing one template often fixes dozens of URLs at once.
Step 2: Optimize LCP (Loading)
LCP is usually the hero image or main heading at the top of the page. Google’s LCP optimization guide breaks it into four parts: time to first byte, resource load delay, resource load duration and element render delay. Each needs a different fix.
Fix a slow server (time to first byte):
- Use good hosting, not the cheapest shared plan
- Turn on page caching so pages aren’t rebuilt for every visitor
- Use a CDN to serve files from locations close to your visitors
Fix a slow hero image (load delay and duration):
- Compress it and serve WebP or AVIF at the size it’s displayed
- Never lazy-load the LCP image; Google says that always adds delay
- Give the hero image a high fetch priority (the fetchpriority attribute set to high) so the browser loads it first
- Avoid background sliders and videos above the fold
Fix render delay:
- Reduce render-blocking CSS and JavaScript in the page head
- Load web fonts efficiently and limit how many font weights you use
- Remove plugins that add scripts to every page but are only needed on one
Step 3: Optimize INP (Responsiveness)
INP measures the delay between a tap or click and the page visually responding. Poor INP almost always comes from too much JavaScript running on the main thread.
Common fixes:
- Remove or replace heavy plugins, sliders and page builder add-ons
- Delay non-essential third-party scripts like chat widgets, heatmaps and extra tracking tags
- Break up long JavaScript tasks so the browser can respond between them
- Keep menus, accordions and forms lightweight
I cover this metric in depth in my guide on how to improve INP score.
Step 4: Optimize CLS (Visual Stability)
CLS measures unexpected layout movement, like a button jumping down just as you try to tap it. Google’s CLS guide lists the most common causes and fixes:
- Images and videos without dimensions: always set width and height, or use CSS aspect-ratio, so space is reserved
- Ads, embeds and iframes: reserve space with a minimum height
- Content injected at the top: cookie banners, promo bars and notices pushing content down
- Web fonts: use a close fallback font so text doesn’t reflow when the custom font loads
- Animations: animate with transforms instead of properties that move the layout
Google also notes that making pages eligible for the back/forward cache helps, because returning visitors see the page restored instantly without shifts.
Which Core Web Vitals Fix to Do First
You rarely have time to fix everything at once. Use this order:
- Mobile before desktop. Most local customers visit on phones, and mobile scores are usually worse.
- Templates with the most traffic. A fix to the service page template helps every service page. Check Search Console to see which pages bring the most visits.
- The metric marked “Poor”. Fix any metric in the poor range before improving one that “needs improvement”.
- Cheap fixes first. Caching, image compression and removing an unused plugin take minutes. Changing a theme takes weeks.
- Pages that bring leads. A slow contact or booking page costs more than a slow old blog post.
Write down the before scores for each template, so you can show what changed after each fix.
Core Web Vitals for Next.js and Headless Sites
Next.js sites start faster than most theme-based sites, but they can still fail Core Web Vitals. The framework has built-in tools for each metric:
- Images: the Image component serves resized, modern formats and needs a width and height, which prevents layout shift.
- Fonts: next/font hosts fonts with your site and helps avoid text jumping when a font loads.
- Third-party scripts: the Script component has a lazyOnload strategy that loads scripts “during browser idle time”. The Next.js docs suggest it for chat plugins and social media widgets.
The usual problems on Next.js sites are too much client-side JavaScript, heavy animation libraries on every page and large hero images that aren’t marked as a priority. If you’re considering this setup, my guide to headless WordPress with Next.js explains how it works. For images in particular, see my Next.js image optimization guide.
Core Web Vitals Optimization for WordPress
Most small business sites I work on run WordPress, and the same issues come up again and again: Page builders are a common cause, and my comparison of Elementor vs Gutenberg shows the trade-off.
| Problem | Fix |
|---|---|
| Heavy page builder theme | Switch to a lighter theme, or rebuild key templates |
| 30+ plugins | Remove unused ones and replace heavy ones with lighter options |
| No caching | Add a caching plugin or host-level caching |
| Uncompressed images | Use an image optimization plugin that serves WebP or AVIF |
| Hero slider on the home page | Replace with one static, optimized image |
| Many tracking scripts | Load them through one tag manager and remove duplicates |
Your theme choice sets the baseline. My guide to the best WordPress theme for small business compares lightweight options.
Step 5: Verify and Monitor
Lab tools show improvements immediately, but Search Console uses real user data collected over time. After fixing a template:
- Re-test the page in PageSpeed Insights
- In Search Console, open the issue and click “Validate fix”
- Expect the field data to take a few weeks to fully update
- Re-check after any theme change, new plugin or redesign
Core Web Vitals are one part of site health. My technical SEO checklist covers the rest.
Frequently Asked Questions
What are good Core Web Vitals scores?
Google’s thresholds are LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less. They’re measured at the 75th percentile of real page loads, so most of your visitors need a good experience, not just the fastest ones.
Do Core Web Vitals affect SEO rankings?
They’re part of how Google evaluates page experience, but relevant, helpful content still matters more. Think of good Core Web Vitals as a tiebreaker and a conversion booster. Faster, more stable pages also keep more visitors, which means more calls and form submissions.
Why is my PageSpeed score different from Search Console?
PageSpeed Insights runs a lab test on one load with a simulated device, while Search Console uses real user data collected over about 28 days. Lab scores change right away after fixes; real user data catches up over several weeks. Focus on the real user data for decisions.
What is the fastest way to improve Core Web Vitals on WordPress?
Add page caching, compress and resize images, stop lazy-loading the hero image, remove unused plugins and delay non-essential third-party scripts. These steps alone often move a typical WordPress site from poor to good on LCP and noticeably improve INP.
How long does Core Web Vitals optimization take?
Simple fixes like caching, image compression and plugin clean-up can be done in a day or two. Deeper work, like replacing a heavy theme or rebuilding templates, can take a few weeks. Then allow several weeks for Search Console’s real user data to reflect the changes.
Which Core Web Vital should I fix first?
Fix the metric that’s in the “Poor” range on mobile for your highest-traffic template. For most small business sites, that’s LCP, often caused by slow hosting or a large hero image. If LCP is good but INP is poor, focus on reducing JavaScript, especially third-party scripts and heavy plugins.
Does a CDN improve Core Web Vitals?
It usually helps LCP, because a CDN serves files from a server close to each visitor, which cuts loading time. It does little for INP, which depends on JavaScript running in the browser, or for CLS, which depends on how the page is built. Use a CDN together with caching, image optimization and fewer scripts.
Final Thoughts
Core Web Vitals optimization is less about chasing a perfect score and more about fixing what slows real visitors down. Find the problem templates in Search Console, fix LCP with better hosting and a lighter hero image, cut JavaScript for INP and reserve space to stop layout shifts.
If you’d like it done for you, my website speed optimization service starts at $79 with a before-and-after PageSpeed report, or you can send me a message for a quick speed review.





Comments
Be the first to share your thoughts or ask a question.
Leave a comment
Your email will not be published. Comments appear after review.