In early 2026, we got a call from a skilled nursing facility in Rockford, Illinois. Their Google Analytics was showing a dramatic traffic drop. Their Core Web Vitals scores had fallen to zero across the board. And their site — which had always been a steady source of family inquiries — had gone almost completely quiet. Nobody was calling anymore.
When we ran the first performance test, the Largest Contentful Paint came back at 22.4 seconds. On mobile. That number doesn't just mean a slow website. It means the page was functionally broken for anyone on a cell phone — which is most people doing local searches. Before the main content even loaded, the majority of visitors had already bounced.
This is the full story of what caused it, how we fixed it, and what Core Web Vitals actually mean for your business.
What Are Core Web Vitals?
Core Web Vitals are a set of metrics Google uses to measure the real-world user experience of a web page. They became an official Google ranking factor in 2021, meaning poor scores can directly hurt where you show up in search results. There are three primary metrics:
LCP measures how long it takes for the largest visible element on the page — usually a hero image or headline — to fully load. Google's target is under 2.5 seconds. Our client was at 22.4 seconds. Every second beyond 2.5 is hemorrhaging potential customers.
CLS measures how much the page visually "jumps" as it loads — images popping in, fonts swapping, banners appearing and pushing content down. A high CLS score means visitors are clicking the wrong things because the page moved underneath their finger. Google's target is under 0.1.
INP replaced First Input Delay in 2024. It measures how quickly the page responds to user interactions — clicks, taps, keyboard input. A page that feels "laggy" or unresponsive has a poor INP score. Google's target is under 200 milliseconds.
The Root Cause Diagnosis
When we dug into the site's technical setup, we found not one problem but a cascade of compounding issues — each one making the others worse:
RevSlider Serving Uncompressed, Oversized Images
The homepage hero used RevSlider, a popular WordPress slider plugin. The images being served were original photography files — 4–6 MB each, completely uncompressed, with no responsive sizing. The browser was downloading a 5MB image to display it at 400 pixels wide on a mobile screen. This alone accounted for the majority of the LCP problem.
Conflicting Caching and Optimization Plugins
The site had both Autoptimize and Smush Pro installed, along with WP Rocket — three plugins that all touch CSS, JavaScript, and image loading. When these plugins conflict, they can create a situation where caching rules contradict each other, JavaScript loads in the wrong order, and images get lazy-loaded incorrectly. The combined effect was catastrophic for page speed.
reCAPTCHA Loading on Every Page
Google reCAPTCHA was loading its JavaScript on every single page of the site, including the homepage — even though it was only needed on the contact page. reCAPTCHA's script alone adds significant page weight and load time. Loading it everywhere is unnecessary and expensive in performance terms.
Render-Blocking Font Loading
Font Awesome and Flaticon were both loading their full icon libraries on every page, with no font-display optimization. This meant the browser couldn't render any text until these external font files had fully loaded — creating a blank-page experience that lasted seconds on slower connections.
The Fix: A Systematic Performance Recovery
We tackled the issues in order of impact, verifying improvement at each step before moving to the next one. Here's the sequence:
1. RevSlider Image Replacement and Compression
We exported every RevSlider image, compressed them to under 200KB each using ShortPixel, resized them to the actual display dimensions, and converted them to WebP format. We then configured RevSlider to serve the correct image size for mobile vs. desktop viewports. LCP dropped from 22.4 seconds to approximately 8 seconds from this step alone.
2. Plugin Conflict Resolution
We deactivated Autoptimize and Smush Pro and configured WP Rocket as the sole optimization plugin. WP Rocket's built-in image optimization, CSS minification, and JS deferral settings were configured carefully to avoid conflicts. This eliminated the cascading caching failures and brought LCP down to approximately 5 seconds.
3. Conditional reCAPTCHA Loading
We added a conditional loading rule so that reCAPTCHA only loads on the Contact page where it's actually used. Removing it from every other page eliminated a significant JavaScript weight from the homepage and all service pages.
4. Font-Display Optimization
We added font-display: swap to both Font Awesome and Flaticon's CSS, and restricted each library to load only the icon subsets actually used on each page rather than the full library. This eliminated the render-blocking text issue entirely.
5. Lazy Loading Configuration and Image Optimization Site-Wide
We audited every image on the site, replaced oversized images, and configured WP Rocket's lazy loading correctly so that above-the-fold images load immediately while below-the-fold images load as the visitor scrolls. Incorrect lazy loading — where even the hero image is deferred — is a surprisingly common cause of poor LCP scores.
The Results
LCP: 22.4 seconds → 3.8 seconds · CLS: 0.42 → 0.04 · INP: Poor → Good · Core Web Vitals: Fail across the board → Pass on mobile and desktop · Organic traffic: Recovering month over month after the fixes
Within 30 days of deploying the fixes, Google had re-crawled and re-evaluated the site. Core Web Vitals scores were passing. Organic traffic began recovering. Within 60 days, family inquiry calls were coming in again — and the client told us the volume had actually exceeded what they were seeing before the performance crash.
What This Means for Your Business
The 22-second load time story is an extreme case — but slow websites are not rare. In our experience, the majority of small business WordPress sites have at least one significant performance issue that's hurting both their user experience and their search rankings. Most business owners have no idea it's happening because they're viewing their own site on a fast connection with a cached browser.
Run a Google PageSpeed Insights test on your homepage right now. If your LCP is above 2.5 seconds on mobile, it's costing you. The question is just how much.
If you want a full technical audit — not just the speed score but the root causes and the prioritized fix list — that's part of every Foundation Audit we run. Book a free strategy call and we'll talk through what we'd find on your site.