Understanding Core Web Vitals and Page Experience

Your Website Speed Is Now a Ranking Factor — Here’s Exactly What Google Measures

In May 2021, Google officially made page experience a ranking signal. By 2026, it’s no longer optional — it’s table stakes. If your Core Web Vitals scores are poor, you’re hemorrhaging rankings to competitors who took 20 minutes to optimize theirs.

Here’s the reality: 53% of mobile users abandon a site that takes longer than 3 seconds to load (Google/SOASTA Research). That’s not a future prediction — that’s happening to your website right now, every single day.

At V12 AI, we audit Core Web Vitals for every client site we touch. The businesses that fix these metrics see measurable ranking improvements within weeks, not months. This guide breaks down exactly what each metric means, how to measure yours, and what to fix first.

What Are Core Web Vitals?

Core Web Vitals are three specific metrics Google uses to evaluate the real-world user experience of your website:

1. Largest Contentful Paint (LCP) — How fast does your main content load?
2. Interaction to Next Paint (INP) — How quickly does your site respond when users interact?
3. Cumulative Layout Shift (CLS) — Does your page jump around while loading?

These aren’t arbitrary metrics. Google derived them from studying billions of user sessions to identify the factors that most directly correlate with user satisfaction. When someone says “this site feels slow” or “this site feels janky,” they’re describing poor Core Web Vitals — they just don’t know the technical names.

Why These Three Metrics Matter More Than Page Speed Score

A common mistake we see with New Hampshire businesses is obsessing over their overall PageSpeed Insights score while ignoring the individual Core Web Vitals. Your score could be 85 and still have a failing LCP. Google doesn’t rank you based on a single number — it evaluates each vital independently.

LCP: Largest Contentful Paint — The Speed Test That Actually Matters

LCP measures how long it takes for the largest visible element on your page to fully render. This is usually your hero image, a video thumbnail, or a large block of text.

Google’s thresholds:

• Good: Under 2.5 seconds
• Needs Improvement: 2.5–4.0 seconds
• Poor: Over 4.0 seconds

What kills LCP scores:

• Unoptimized images (the #1 culprit we see in NH business sites)
• Slow server response times (cheap hosting often means shared servers with 200+ other sites)
• Render-blocking JavaScript and CSS
• Client-side rendering without server-side fallback

How to Fix LCP Issues

Image optimization is your biggest win. Convert images to WebP format — it reduces file sizes by 25-34% compared to JPEG with no visible quality loss. Implement lazy loading for below-the-fold images, and use explicit width and height attributes.

Upgrade your hosting. If you’re on a $5/month shared hosting plan, your server response time (TTFB) is likely 800ms+ before the browser even starts rendering. A managed WordPress host or VPS typically delivers TTFB under 200ms. We’ve covered this in detail in our web hosting guide for business owners.

Preload critical assets. Add <link rel="preload"> tags for your hero image and critical fonts. This tells the browser to fetch them immediately instead of waiting to discover them in the CSS.

INP: Interaction to Next Paint — The Responsiveness Metric

INP replaced First Input Delay (FID) in March 2024 as a Core Web Vital. While FID only measured the first interaction, INP measures responsiveness throughout the entire page visit — a much better indicator of real-world user experience.

Google’s thresholds:

• Good: Under 200 milliseconds
• Needs Improvement: 200–500 milliseconds
• Poor: Over 500 milliseconds

INP captures every click, tap, and keyboard interaction during a session, then reports the worst one (with some outlier exclusion). If your site feels “laggy” when users click buttons or fill out forms, INP is catching that.

Common INP Killers

Heavy JavaScript execution is the primary offender. Every script running on your page competes for the browser’s main thread. When a user clicks a button while JavaScript is executing, their click gets queued — and that delay is what INP measures.

Third-party scripts are the silent killers. Analytics trackers, chat widgets, social media embeds, advertising pixels — each one adds main thread work. We regularly audit client sites and find 15-25 third-party scripts loading on a single page. A study by Akamai found that each additional third-party script increases page load time by an average of 34.1ms.

To improve INP:

• Audit and remove unused JavaScript (most WordPress sites have 40-60% unused JS)
• Defer non-critical scripts with async or defer attributes
• Break up long tasks — any JavaScript task over 50ms blocks the main thread
• Use web workers for heavy computation
• Minimize DOM size (under 1,500 nodes is ideal)

CLS: Cumulative Layout Shift — Stop Your Page From Jumping Around

CLS measures visual stability. Ever tried to click a button on a website, and then the page shifts and you click an ad instead? That’s a layout shift, and Google penalizes it.

Google’s thresholds:

• Good: Under 0.1
• Needs Improvement: 0.1–0.25
• Poor: Over 0.25

According to a 2025 Chrome UX Report, 23% of websites still fail the CLS threshold — making it the most commonly failed Core Web Vital. The fix is usually straightforward, which makes it even more frustrating that so many sites ignore it.

What Causes Layout Shifts

• Images without dimensions: When you don’t specify width and height, the browser doesn’t know how much space to reserve. The image loads, and everything below it jumps.
• Ads and embeds loading late: Dynamic content injected after initial render pushes existing content around.
• Web fonts loading: When a custom font replaces a system font, text size often changes, causing shifts.
• Dynamic content above existing content: Banners, cookie notices, or notifications that push the page down.

CLS Quick Fixes

Always set explicit dimensions on images and videos. This is the single highest-impact CLS fix. In WordPress, ensure your theme outputs width and height attributes on all <img> tags.

Reserve space for ad slots and embeds with CSS min-height properties. Even if the ad hasn’t loaded yet, the space is already allocated.

Use font-display: swap in your @font-face declarations, and preload your primary web fonts to minimize the flash of unstyled text (FOUT).

How to Measure Your Core Web Vitals

Google provides several free tools — use them in combination for the fullest picture:

Google Search Console → Core Web Vitals report: This is your most authoritative source because it uses real user data (CrUX data) from Chrome users visiting your site. It tells you exactly how many URLs are Good, Needs Improvement, or Poor.

PageSpeed Insights (pagespeed.web.dev): Enter any URL to get both lab data (simulated) and field data (real users). Focus on the field data section — that’s what Google actually uses for rankings.

Chrome DevTools → Performance tab: For developers who want granular diagnosis. Record a page load and inspect every metric in detail.

Web Vitals Chrome extension: Real-time Core Web Vitals display as you browse your own site. Essential for quick spot-checks.

The Business Impact: What NH Companies Are Leaving on the Table

This isn’t abstract technical SEO. Core Web Vitals directly impact revenue:

• Vodafone improved LCP by 31% and saw a 15% increase in sales (web.dev case study)
• NDTV reduced LCP by 55% and saw 50% reduction in bounce rate
• A 100ms improvement in load time increased conversion rates by 8.4% for retail sites (Akamai)

For a New Hampshire service business getting 2,000 monthly visitors with a 3% conversion rate, improving Core Web Vitals from Poor to Good could mean the difference between 60 and 75+ leads per month. At $500 average customer value, that’s $7,500/month in revenue from a one-time technical fix.

We see this pattern consistently across our NH client base. The businesses investing in technical SEO fundamentals — not just content and backlinks — are the ones pulling ahead in local search results. Our comprehensive website audit guide covers the broader picture of technical SEO health.

Your Core Web Vitals Action Plan

This week:

1. Run your site through PageSpeed Insights — check field data for all three vitals
2. Review your Search Console Core Web Vitals report for site-wide patterns
3. Identify your worst-performing metric — fix that one first

This month:

1. Optimize all images (WebP conversion, lazy loading, explicit dimensions)
2. Audit and defer non-critical JavaScript
3. Upgrade hosting if TTFB exceeds 400ms

Ongoing:

1. Monitor Core Web Vitals monthly in Search Console
2. Test new pages before publishing
3. Audit third-party scripts quarterly

Core Web Vitals aren’t a one-time fix — they’re an ongoing optimization discipline. Every new plugin, image, or third-party integration can impact your scores. Build measurement into your workflow, and you’ll stay ahead of competitors who treat performance as an afterthought.

Need a professional Core Web Vitals audit for your NH business? Contact V12 AI — we’ll identify exactly what’s holding your site back and build a prioritized fix plan that delivers measurable ranking improvements.