Google Search Console Series: Core Web Vitals — What the Scores Mean and How to Fix Them

Core Web Vitals is Google’s set of page experience signals — real-world performance metrics that measure how fast and responsive your pages feel to actual users. Since 2021, they’re a confirmed Google ranking factor. Here’s what each metric means, how to read the Search Console report, and how your WordPress setup affects them.

The three Core Web Vitals

LCP — Largest Contentful Paint

LCP measures how long it takes for the largest visible element on the page to load — usually a hero image, a featured image, or a large block of text. It’s the metric most users associate with “how fast did the page load.”

• Good: under 2.5 seconds
• Needs improvement: 2.5–4 seconds
• Poor: over 4 seconds

Common causes of slow LCP on WordPress: unoptimised hero images, render-blocking JavaScript, slow server response time (TTFB), and heavy SEO plugins adding frontend bloat. This last one is particularly relevant — popular SEO plugins like Yoast can add 30KB+ of JavaScript to every page. The RankAlSEO plugin adds approximately 4KB, which directly helps LCP.

INP — Interaction to Next Paint

INP replaced FID (First Input Delay) in March 2024. It measures how quickly your page responds to user interactions — clicks, taps, keyboard inputs — throughout the entire page lifecycle, not just on first load.

• Good: under 200ms
• Needs improvement: 200–500ms
• Poor: over 500ms

Common causes of poor INP on WordPress: excessive JavaScript execution, heavy page builders (Elementor, Divi), JavaScript-based sliders and popups, and chat widgets loading on every page.

CLS — Cumulative Layout Shift

CLS measures how much the page layout shifts unexpectedly while loading. You’ve experienced this when you go to click a button and it suddenly moves because an image or ad loaded above it. CLS scores the total amount of unexpected movement on the page.

• Good: under 0.1
• Needs improvement: 0.1–0.25
• Poor: over 0.25

Common causes of high CLS on WordPress: images without defined width and height attributes, ads loading above content, web fonts causing text reflow, and embeds (YouTube, Twitter) that resize after loading.

How to read the Core Web Vitals report

In Google Search Console → Experience → Core Web Vitals, you’ll see separate reports for Mobile and Desktop. Click into each:

• Good URLs: Pages passing all three metrics — these are fine, monitor for regressions
• Needs improvement: Pages that aren’t failing but are close — fix these before they slip to Poor
• Poor URLs: Pages failing one or more metrics — these are hurting your rankings, fix first

Click any URL group to see which specific pages are affected and which metric is failing.

How to diagnose a specific page

Google Search Console shows aggregated field data (real user data from Chrome). For page-level diagnosis use:

• PageSpeed Insights (pagespeed.web.dev) — enter any URL to get a full breakdown of what’s causing issues and specific recommendations
• RankAlSEO Speed Checker tool (rankalseo.com/tools/speed-checker.html) — free tool that runs a PageSpeed analysis on any URL
• Chrome DevTools → Performance tab — for deep diagnosis of JavaScript and rendering issues

Fixing Core Web Vitals on WordPress

To improve LCP

• Optimise and compress images (use WebP format)
• Add loading="eager" and fetchpriority="high" to the hero image
• Use a fast hosting provider with good TTFB
• Use a CDN (Cloudflare, BunnyCDN)
• Replace heavy SEO plugins with the lightweight RankAlSEO plugin
• Minimise render-blocking CSS and JS

To improve INP

• Audit your installed plugins — each plugin that loads JavaScript on the frontend adds execution cost
• Defer non-critical JavaScript
• Remove unused page builder scripts on pages that don’t use them
• Avoid loading chat widgets and heavy embeds on every page

To improve CLS

• Add width and height attributes to all images (WordPress does this automatically since 5.7)
• Reserve space for ads and embeds with CSS aspect-ratio
• Preload fonts and use font-display: swap
• Avoid inserting content above existing content after load

Why the RankAlSEO plugin helps Core Web Vitals

Most SEO plugins are some of the worst offenders for page speed. The RankAlSEO plugin was built with this in mind:

• ~4KB frontend footprint — vs Yoast’s 30KB+ and RankMath’s 20KB+
• No frontend JavaScript for basic features — schema and meta are output as static HTML
• No admin bar bloat that leaks to the frontend
• Minimal CSS on public pages

This means installing the RankAlSEO plugin has a negligible impact on your Core Web Vitals — unlike switching from a lighter plugin to a heavier one, which can visibly hurt your LCP scores.

Action steps

1. Go to Search Console → Experience → Core Web Vitals → Mobile report
2. Note how many URLs are in each category (Good/Needs improvement/Poor)
3. Click into Poor URLs and identify which metric is failing (LCP, INP, or CLS)
4. Run those URLs through RankAlSEO Speed Checker for specific recommendations
5. Fix the highest-impact issue first (usually LCP on mobile)

Next in this series: HTTPS — what Google checks about your site’s security and what errors mean.