Epic Insights
Edition 24 · Jun 16, 2026
|
|
Fast Enough Last Year Might Be Too Slow Now |
|
|
Your website probably loads just fine when you check it on your office wifi. The trouble is, Google isn't grading you on your office wifi. It's grading you on a customer standing in your parking lot on a three-bar cell signal, and this spring it got stricter about what counts as fast. |
|
|
The Big Story
Google Quietly Raised the Speed Bar and Most Sites Slipped Under ItThis spring, Google tightened the bar for what counts as a fast-loading page. The "good" score for Largest Contentful Paint, which is really just the time it takes for your biggest image or headline to show up, dropped from 2.5 seconds to 2.0. Google confirmed it on its Search Central blog back in March, and at the same time promoted INP, a measure of how quickly your site reacts when someone taps, to a full ranking signal next to it. Then the receipts landed. The latest Chrome user-experience data, published June 9, shows only about 56% of tracked sites now pass all three Core Web Vitals. The thing dragging most of them down is that load-speed number, where barely two-thirds of sites score well. Think of it like a class where the passing grade moved from 70 to 80. You scored your usual 75 and went from passing to failing without changing a single answer. Same site. New cutoff. A page that sailed through a year ago can be sitting in the "needs improvement" column today, and you'd never know unless you went looking. This isn't about chasing a perfect score. It's about not slipping below a line your customers feel in their thumbs before Google ever measures it. The good news is that load speed is usually fixable, and the culprits are boringly consistent: an oversized hero image, a slow host, a pile of plugins all loading before anything you can actually see does. |
|
|
|
|
Your move: Run your homepage through Google's free PageSpeed Insights and look at one number, the LCP. If it's over 2 seconds on mobile, that's this month's fix list. Send us the result and we'll tell you what's worth doing first. |
|
|
Quick Hits
The rest of the week, in bite-sized pieces |
|
|
|
|
|
|
|
|
|
|
Ask Epic
"My site loads fast for me. Why do you keep harping on speed scores?"Fair question. Here's why we keep bringing it up: the speed you experience isn't the speed Google measures. You're loading your site on a fast computer, on your own wifi, with the page already saved in your browser's memory from the last fifty times you opened it. Of course it's quick for you. Google ignores all of that. It pulls its score from real visits by real people on real phones and networks, then looks at how the slower three-quarters of them experienced your site, not the fastest one. So the number that counts is closer to your customer on an older phone, in a spotty-signal waiting room, opening your page cold for the first time. That's the gap we're closing when we talk speed. Not the version you see. The version they do. And the fix is almost never a rebuild, just trimming what's making the first screen heavy. |
|
|
What Epic's doing for you this week
This week the team is re-running speed checks across the sites we host against the new, stricter load-time bar, and building a short fix list wherever a page slipped into the "needs improvement" zone (usually heavy images or a few too many plugins loading up front). We're also pulling clean post-core-update reads now that the May dust has settled, and keeping an eye on the Google Business Profile invite bug for anyone mid-transfer. If something on your account needs your eyes, you'll hear from us directly. Otherwise, your latest reports and any messages from the team are waiting in your Client Center.
|
|
|
|
|
Thanks for reading! Got questions? Ideas? I'm all ears. Share your thoughts with me and help shape future editions of Epic Insights. — Kristy Freeman |
|
|
|
