Google has turned user experience into a ranking factor. Not in a vague, theoretical way — in a measured, scored, pass-or-fail way. They call these measurements Core Web Vitals.
If your website fails Core Web Vitals, you're at a ranking disadvantage compared to competitors who pass. And most Edmonton business websites fail at least one metric.
Here's what they are, what they measure, and how to fix them — without needing a computer science degree.
The Three Core Web Vitals
LCP — Largest Contentful Paint
What it measures: How fast the main content of your page loads.
In human terms: When a customer clicks your search result, how long do they wait before they can actually see your page? The hero image, the main headline, the primary content block — how long until the biggest visible element renders?
Thresholds:
- Good: Under 2.5 seconds
- Needs improvement: 2.5 - 4.0 seconds
- Poor: Over 4.0 seconds
Most common causes of bad LCP:
- Huge, unoptimized images (the #1 culprit for Edmonton business sites)
- Slow server response time (cheap shared hosting)
- Render-blocking JavaScript and CSS
- Client-side rendering (the page loads blank, then JavaScript builds the content)
How to fix it:
- Optimize your hero image: compress, use WebP, set explicit width/height
- Preload your LCP image so the browser prioritizes it
- Upgrade hosting if server response time is over 600ms
- Defer non-critical JavaScript
- Inline critical CSS
INP — Interaction to Next Paint
What it measures: How quickly your site responds when someone interacts with it.
In human terms: When a customer taps a button, clicks a link, or opens a menu on your site, does it respond instantly or is there a noticeable delay? That lag — where you tap something and nothing happens for a beat — is what INP measures.
Thresholds:
- Good: Under 200 milliseconds
- Needs improvement: 200 - 500 milliseconds
- Poor: Over 500 milliseconds
Most common causes of bad INP:
- Heavy JavaScript execution blocking the main thread
- Too many event listeners
- Complex DOM updates when interacting with elements
- Third-party scripts (chat widgets, analytics, social embeds) hogging resources
How to fix it:
- Reduce JavaScript payload and execution time
- Break up long tasks into smaller chunks
- Remove or defer unnecessary third-party scripts
- Optimize event handlers
- Use web workers for heavy computation
CLS — Cumulative Layout Shift
What it measures: How much the page layout jumps around while loading.
In human terms: You're reading a paragraph on a website. Suddenly the text shifts down because an ad loaded above it. You go to tap a button and it moves because an image loaded and pushed everything else down. That's layout shift, and it's infuriating.
Thresholds:
- Good: Under 0.1
- Needs improvement: 0.1 - 0.25
- Poor: Over 0.25
Most common causes of bad CLS:
- Images without specified dimensions (browser doesn't know how much space to reserve)
- Ads or embeds loading dynamically and pushing content
- Web fonts loading and causing text to reflow (FOIT/FOUT)
- Content injected above existing content after page load
How to fix it:
- Always set width and height attributes on images and videos
- Reserve space for ads and dynamic content with CSS aspect-ratio or min-height
- Use
font-display: swapfor web fonts and preload them - Avoid inserting content above existing visible content
How to Check Your Core Web Vitals
PageSpeed Insights
pagespeed.web.dev — Test any URL and see your Core Web Vitals scores. Test on mobile — that's what Google uses for ranking.
The "Field Data" section shows real user experience (if available). The "Lab Data" section shows simulated performance. Field data is what Google actually uses for rankings.
Google Search Console
Core Web Vitals report shows your entire site's performance, categorized as Good, Needs Improvement, or Poor. This is the most authoritative source because it uses real user data from Chrome browsers visiting your site.
Chrome DevTools
For developers: Performance panel provides detailed waterfall analysis of exactly what's happening during page load and interaction.
How Core Web Vitals Affect Rankings
Core Web Vitals are a tiebreaker ranking factor. They don't override content relevance, authority, or backlinks. But when two pages are roughly equal in quality and relevance, the one with better Core Web Vitals gets the edge.
In Edmonton's competitive local markets — where multiple dental clinics, law firms, or HVAC companies compete for the same keywords with similar content — that tiebreaker can mean the difference between position 3 and position 7.
Think of it this way: Core Web Vitals won't make a bad page rank. But they can prevent a good page from ranking as high as it should.
The Quick Win Approach
You don't need to achieve perfect scores. You need to pass — get into the "Good" threshold for all three metrics.
Priority order:
- Fix CLS first — Usually the easiest to fix (add image dimensions, reserve space for dynamic content)
- Fix LCP next — Optimize your largest image, improve hosting, defer render-blocking resources
- Fix INP last — Often requires JavaScript optimization, which is more technical
Getting from "Poor" to "Good" has the biggest ranking impact. Going from "Good" to "Perfect" has diminishing returns.
Edmonton Business Reality Check
We audit Edmonton business websites weekly. Here's what we typically find:
- LCP: 70% of sites fail (over 2.5 seconds on mobile). Usually caused by unoptimized hero images on cheap hosting.
- CLS: 40% of sites fail. Usually caused by images without dimensions or late-loading ads/widgets.
- INP: 30% of sites fail. Usually caused by bloated WordPress installations with too many plugins.
The silver lining: because most of your competitors also fail, fixing your Core Web Vitals gives you a competitive advantage that most Edmonton businesses don't have.
Get your Core Web Vitals diagnosed →
Related reading: