Core Web Vitals are three specific speed and stability metrics Google uses to evaluate website quality. They have been a ranking factor since 2021, and the weight Google assigns them has been growing. Most realtor websites fail at least one of the three, often two.
Here is what each one measures, what bad looks like, and the realtor specific fixes that actually work.
LCP: Largest Contentful Paint
LCP measures how long it takes for the largest visible element on the page (usually your hero image or main heading) to appear. Good is under 2.5 seconds. Most realtor sites measure 3.5 to 6 seconds, which Google flags as poor.
The fixes:
Optimize your hero image. A 5MB JPEG should be a 200KB WebP. Modern image formats achieve dramatically better compression than the JPEGs and PNGs most sites still use. Free online converters (Squoosh, TinyPNG) will do the job in seconds.
Serve images at the right size. If your hero is displayed at 1600 pixels wide, you do not need to ship a 4096 pixel image. Resize before upload.
Move heavy third party scripts below the fold or eliminate them. Chat widgets, popup tools, multiple analytics scripts. Each one blocks rendering. Audit your scripts, keep the essential, remove the rest.
Use edge hosting. Sites hosted on Cloudflare, Vercel, or Netlify respond to the first byte in under 200ms. Sites hosted on cheap shared WordPress hosts often take 1 to 2 seconds just to start serving content.
INP: Interaction to Next Paint
INP replaced FID (First Input Delay) in 2024 and measures how quickly the page responds when a user taps or clicks something. Good is under 200ms. Bad is over 500ms.
A bad INP makes the page feel broken even when it loads. The user taps a button, nothing seems to happen, they tap again, nothing seems to happen, and eventually two events fire at once.
The fixes:
Reduce JavaScript that runs during page load. Heavy frameworks, complex analytics, embedded chat widgets, all eat into your interaction budget. Modern realtor builders ship with significantly less JavaScript than they did five years ago, but legacy WordPress sites with 20 plugins often have hundreds of kilobytes of script blocking the main thread.
Defer non critical scripts. Anything that does not need to run immediately (analytics tracking, social media buttons, etc.) should load after the page is interactive.
Avoid layout thrashing. JavaScript that constantly reads and writes the DOM (some old image carousels, some chat widgets) causes the browser to recalculate layout over and over. Modern frameworks largely avoid this, but legacy plugins can still hit you.
CLS: Cumulative Layout Shift
CLS measures how much elements on your page move around as it loads. Late loading ads pushing content down, fonts swapping after the page paints, images without dimensions causing reflows. Good is under 0.1.
A bad CLS is the experience of trying to tap a link and having it jump out from under your finger because something loaded above it. Frustrating and disorienting.
The fixes:
Set explicit width and height on every image. The HTML attributes (width=600 height=400) or CSS aspect ratio. This lets the browser reserve space before the image loads, preventing the layout shift.
Preload critical fonts. Custom fonts can cause a flash of unstyled text or layout shift when they load. Preloading them (a single link tag in the head) avoids this.
Avoid late inserted content above the fold. Cookie banners that push everything down, popup signup forms, late loading ad slots. These cause large CLS scores. The fix is to position these elements absolutely so they overlay rather than push content.
Diagnosing your scores
Free tools:
Google PageSpeed Insights (pagespeed.web.dev). Paste your URL, look at the mobile tab. Gives you specific actionable suggestions.
Google Search Console, Core Web Vitals report. Shows real user data from actual Chrome users on your site, broken down by mobile and desktop. This is the data Google uses for ranking decisions.
WebPageTest.org. Detailed waterfall view showing exactly what loaded when. Useful when you need to understand why a specific score is bad.
The realtor specific reality
Most realtor websites fail Core Web Vitals because they were built on platforms or themes that prioritized features over performance. Adding more widgets to a slow site does not fix it. Migration to a performance focused platform usually does.
If your current site scores below 80 on mobile and you have already tried image compression and script audits, the underlying platform is probably the limit. At that point, the cost benefit shifts toward migration.