LCP Just Dropped to 2 Seconds. Most East Texas Websites Already Failed.
Key takeaways
- The LCP target dropped from 2.5s to 2.0s in March 2026 — what passed in 2025 may fail in 2026.
- Only about 44% of WordPress sites on mobile were already passing the old 2.5s threshold.
- The fix is usually the hero image and the hosting, not some mysterious code problem.
- You don’t need to chase a perfect score — you need a green LCP. There’s a difference.
If you’ve been ignoring the Core Web Vitals lectures, here’s the part you can’t ignore anymore: Google quietly tightened the LCP rule earlier this year. A site that loaded in 2.3 seconds was fine in December. In June 2026, it’s a fail.
That sounds small. It isn’t. It moves a huge chunk of small-business sites from the “good” column into the “needs work” column overnight — without anyone touching their website.
What actually changed
LCP stands for Largest Contentful Paint — the time it takes for the biggest visible thing on your page to show up. Usually that’s the hero image at the top of your homepage, or the photo at the top of a service page.
The old rule was: under 2.5 seconds is “good.” The new rule, as of the March 2026 update, is: under 2.0 seconds is “good.” Google didn’t make a big deal about it. They almost never do. But the threshold quietly shifted.
| Status | Old (pre-March 2026) | New (current) |
|---|---|---|
| Good (green) | Under 2.5s | Under 2.0s |
| Needs improvement | 2.5s – 4.0s | 2.0s – 4.0s |
| Poor (red) | Over 4.0s | Over 4.0s |
Why this hits East Texas small businesses harder
Two reasons.
First, a lot of small-business sites around here run on cheap shared hosting and a stack of plugins someone installed and forgot about. That stack was barely getting under 2.5s. It’s not getting under 2.0s without help.
Second, mobile rural traffic isn’t always great. Your shop in Longview might serve customers driving in from Marshall, Henderson, or Carthage. Those phones aren’t always on a perfect 5G signal. Every fraction of a second on the server side matters more when the network is shaky to begin with.
The websites that fail this quietly are the ones whose owners only check their phone on Wi-Fi at home.
The thing that almost always fixes it
If your LCP is bad, your hero image is the suspect. That’s it, nine times out of ten.
- It’s a 3.2 MB JPG from a stock site, uploaded without resizing.
- It’s being loaded “lazy” when it shouldn’t be (above-the-fold images should load eagerly).
- It’s being served by your page builder in a format from 2013 instead of WebP or AVIF.
- It’s being requested by JavaScript instead of being in the initial HTML.
The other suspect: your hosting
Shared hosting at $5/month was always a compromise. The server is shared with hundreds of other sites. When one of them gets a traffic spike, yours slows down. When you finally outgrow it, the symptoms show up exactly as a creeping LCP problem.
You don’t need to spend $100/month on hosting. But the difference between a $4 plan and a $25 plan is usually night and day on the speed numbers.
What you can ignore
You don’t need a 100/100 PageSpeed score. Google doesn’t rank by perfection — it ranks by whether you’re in the green zone. Chasing 95 → 100 is a waste of weekends. Chasing 65 → 85 actually moves your rankings.
The competitive reality
Here’s the part that gets ignored. Core Web Vitals only matter as a tiebreaker. If you’re competing for a search term where the other top results all load in 1.7 seconds and yours loads in 2.4, you’re going to slide. If you’re competing for a term where the top result loads in 3.1 seconds, you’ve got room.
For East Texas small businesses, that competitive reality varies wildly by industry. Local plumbers? Some of the top-ranking sites are surprisingly slow — there’s opportunity. Local restaurants? The market is faster; you need to keep up. The honest move is to measure your top three competitors and see where you actually stand, not chase a number in isolation.
How to actually check your score
Two ways, both free.
- PageSpeed Insights (pagespeed.web.dev): paste your URL. Look at the Mobile tab, not Desktop. The “Core Web Vitals Assessment” box at the top is the one Google ranks by.
- Search Console (search.google.com/search-console): the “Core Web Vitals” report shows real visitor data, not a simulation. This is the one that actually counts.
Where people go wrong (and when to call a pro)
The most common DIY mistake is treating the lab score from PageSpeed Insights as gospel. The number that affects rankings is the field data in Search Console — your real visitors on their real phones. If Search Console says you’re failing and PageSpeed says you’re passing, the field data wins. If you’ve already tried compressing images and switching to a caching plugin and the LCP is still red, it’s usually time to bring in someone who can rebuild the page properly instead of bolting on another optimization layer.
Frequently Asked Questions
Will my site lose rankings overnight?
Not overnight, but yes, over weeks. Core Web Vitals are a tiebreaker, not the main ranking factor. Two sites with similar content — the faster one wins. If you were already ranking #1 on a search nobody else competes for, you’ll probably stay there. If you’re in a competitive space, this matters.
Does this apply to my Wix or Squarespace site?
Yes. Every platform is judged by the same Core Web Vitals. Wix has gotten better but is still slower than a tuned WordPress site. Squarespace is in the middle. Shopify is generally fast. The platform sets the ceiling — what you do with it sets the floor.
What about my desktop scores — they’re fine.
Google ranks by the mobile score for almost every site. Desktop is a vanity metric. Mobile is the one that matters.
How fast is fast enough?
Aim for the green LCP — under 2.0s on the field data report in Search Console. Beyond that, your time is better spent on content than on shaving off another tenth of a second.
Want a real human to look at your numbers and tell you straight what’s slowing you down?