LCP (Largest Contentful Paint) is the Core Web Vital that most small business websites fail — and the fixes are almost always the same three issues: Largest Contentful Paint measures how quickly the largest visible element on the page loads — typically a hero image, a heading, or a large text block. Google's 2026 passing threshold is LCP under 2.5 seconds on mobile. The 'Needs Improvement' range is 2.5 to 4.0 seconds; 'Poor' is over 4.0 seconds. For most small business websites, LCP failures trace to three root causes: unoptimized hero images (JPEG or PNG files above 200KB that could be served as WebP at under 60KB without visible quality loss), render-blocking resources (JavaScript or CSS files in the document head that delay the browser from painting any content), and slow server response times (TTFB above 800ms from cheap shared hosting). Check your current LCP score using PageSpeed Insights (pagespeed.web.dev) on your homepage and primary service pages. The tool shows your current LCP element, the LCP time, and specific fix recommendations. GTmetrix provides the waterfall breakdown that shows exactly when the LCP element loads relative to other resources. Screaming Frog's JavaScript crawl mode identifies render-blocking scripts that standard crawl modes miss. Ahrefs' Site Audit and Semrush's Site Audit both flag LCP failures across the full site with severity ratings and fix guidance.

INP (Interaction to Next Paint) replaced FID in 2024 and measures how quickly your page responds to user interaction — the fixes are primarily JavaScript-related: Interaction to Next Paint measures the delay between a user interaction (clicking a button, tapping a menu, submitting a form) and when the browser visually responds. Google's 2026 passing threshold is INP under 200 milliseconds. 'Needs Improvement' is 200 to 500ms; 'Poor' is over 500ms. For local service business websites, INP failures almost always originate from: third-party JavaScript executing on the main thread (chat widgets, appointment booking plugins, marketing pixels, review display widgets), large JavaScript bundles that haven't been code-split or deferred, and animations or transitions triggered by user interaction that are implemented inefficiently. Check INP using PageSpeed Insights — field data shows real-user INP from Chrome users visiting your site. Lab data shows a simulated INP score. The fixes: defer non-critical third-party scripts using the 'defer' or 'async' attribute so they load after the main page content rather than blocking it. Audit which third-party scripts are running on your service pages using GTmetrix's waterfall view — chat widgets and appointment booking tools are frequently the largest INP contributors. Screaming Frog in JavaScript rendering mode shows which scripts are executing during the initial page load. Use Semrush's Site Audit to identify pages with INP failures across the site rather than checking each page individually.

CLS (Cumulative Layout Shift) measures visual stability — and the fix for the most common cause on small business sites takes under 30 minutes: Cumulative Layout Shift measures how much page content unexpectedly moves during loading. A page where images load and push text down, or where a cookie banner appears and shifts the navigation, has high CLS. Google's 2026 passing threshold is CLS under 0.1. 'Needs Improvement' is 0.1 to 0.25; 'Poor' is over 0.25. The most common CLS sources on small business websites: images without explicit width and height attributes in the HTML (the browser doesn't know how much space to reserve until the image loads, causing layout shifts when it does), web fonts loading late and causing text to reflow (fix: use font-display: swap and preload the primary font), and late-loading content blocks from third-party embeds like review widgets, social media feeds, or chat windows that claim space after the initial render. The single fastest CLS fix: add explicit width and height attributes to every img tag on your site. Use Screaming Frog's 'Images' export to identify all images missing these attributes. Check PageSpeed Insights for the specific CLS elements Google has identified as the largest contributors to your CLS score — the tool names the specific elements causing the shifts. GTmetrix's Layout Shifts visualization shows exactly when and where layout shifts occur during page load.

How to diagnose Core Web Vitals failures systematically across all pages — the toolchain that surfaces issues site-wide rather than page by page: Checking Core Web Vitals page by page using PageSpeed Insights is too slow for a site with 20+ pages. The systematic approach uses three tools in sequence. Step 1: Google Search Console's Core Web Vitals report (under 'Experience' in the left sidebar). This shows the count of 'Poor,' 'Needs Improvement,' and 'Good' URLs across your entire site using field data from real Chrome users. It groups pages by the URL pattern causing the issue, which is more useful than individual URL data. Step 2: Ahrefs' Site Audit or Semrush's Site Audit. Both crawl your entire site and flag Core Web Vitals failures across all pages in a single report, with links to PageSpeed Insights for each failing page. This is the fastest way to identify which page templates are failing and whether the issue is site-wide or page-specific. Step 3: GTmetrix for deep diagnosis on specific failing pages. GTmetrix's waterfall chart and Layout Shifts visualization identify the exact resources and load order causing each failing metric. The typical workflow: Search Console identifies failing URL patterns — Semrush or Ahrefs confirms which specific pages fail — GTmetrix diagnoses the root cause on representative pages from each failing pattern.

Hosting upgrade and Webflow-specific CWV optimizations — the infrastructure fixes that set a performance ceiling for all other optimizations: Time to First Byte (TTFB) is the time from the browser's request to the first byte of the server response. Google's 2026 recommended threshold is TTFB under 800ms. Sites on cheap shared hosting routinely show TTFB of 1,500 to 3,000ms, which creates a performance floor that makes passing LCP nearly impossible regardless of image or script optimizations. Check TTFB using GTmetrix's waterfall chart — the first bar in the waterfall is the TTFB. If it's above 800ms consistently, a hosting upgrade (to a VPS, managed WordPress host, or CDN-backed platform) will produce more Core Web Vitals improvement than any amount of image optimization. For Webflow sites specifically: use Webflow's built-in image optimization (WebP conversion and lazy loading) for all uploaded images, limit custom code embeds to essential scripts only and defer or async all third-party scripts, minimize the number of custom fonts loaded (each font weight is a separate request), and use Webflow's CDN which provides globally distributed content delivery. Verify Webflow CWV performance using PageSpeed Insights on primary service pages after any template changes — Webflow updates and added components can introduce CWV regressions. Screaming Frog's crawl time data identifies the slowest-loading pages on the site for prioritized investigation.