Free marketing audit for your business. No commitment.
- (425) 954-3452
- info@kihanmarketing.com
- Seattle, WA | Serving Nationwide
Core Web Vitals SEO explained for owners: what LCP, INP and CLS do to rankings, which fixes matter, what they cost, and how fast you see results.
QUICK ANSWER
Core Web Vitals affect SEO as a small ranking signal, not a major one. They are three metrics: LCP for loading speed, INP for responsiveness, CLS for visual stability. A page passes when LCP is 2.5 seconds or less, INP 200 milliseconds or less, and CLS 0.1 or less on real visitors over 28 days. They matter most as a tiebreaker between pages with similar content and authority.
Core Web Vitals are three metrics Google collects from real Chrome visitors to your site. LCP measures how quickly the main content appears. INP measures how quickly the page reacts when someone taps or clicks. CLS measures how much the layout jumps around while things load. Google publishes a threshold for each one, and a page passes only when all three land in the green.
The thresholds here are not ours to set. Google's Core Web Vitals reference defines them, publicly.
The number Google uses is the 75th percentile of real visits over a rolling 28 day window. That detail matters more than most owners realize. It means your slowest quarter of visitors decides whether you pass, and it means a fix you ship today will not appear in your report for weeks. Your average visitor being fine is not the test.
| Metric | What it measures | Passing | Failing |
|---|---|---|---|
| LCP, Largest Contentful Paint | How long until the main content appears | 2.5 seconds or less | Over 4 seconds |
| INP, Interaction to Next Paint | How fast the page responds to a tap or click | 200 milliseconds or less | Over 500 milliseconds |
| CLS, Cumulative Layout Shift | How much the layout shifts while loading | 0.1 or less | Over 0.25 |
| Overall page status | All three, at the 75th percentile of real visits | All three green | Any single one in the red |
Easy to miss
Mobile and desktop are scored separately. Plenty of sites pass on desktop and fail on mobile, which is usually where most of the traffic comes from.
Less than most speed reports imply, and more than zero. Core Web Vitals sit inside Google’s page experience signals, and Google has been consistent that relevance and authority come first. In practice, passing rarely lifts a page from position 30 to position 5. It helps when you are already competitive and something has to break the tie between you and a similar page.
The bigger win usually is not ranking, it is revenue. A page that takes six seconds on a phone loses people before they ever see your offer or your phone number. Speed improvements tend to show up in bounce rate, form starts and calls long before they show up in position tracking. That is the honest business case for doing this work.
There is a second reason worth naming. If your pages are heavy enough that content arrives only after a large JavaScript bundle runs, you can end up with indexing problems that look like a ranking problem. Core Web Vitals often surface that issue even though the vitals themselves are not the cause. Fixing the underlying weight fixes both.
The 100 out of 100 trap
Chasing a perfect Lighthouse score is a well known time sink. Google grades pass or fail against the thresholds. Green is the finish line, not 100.
Start with field data, not lab scores. Field data is what real visitors experienced, and it is what Google uses to decide pass or fail. Lab tools simulate a single visit on assumed conditions and are useful for one thing only: diagnosing why something is slow. Owners get badly misled when they read a lab score as a verdict.
Spend twenty minutes gathering the picture below before you spend a dollar fixing anything. In most cases the failures cluster by template, so a handful of pages will tell you whether the problem is one oversized image or the theme itself. Check the pages that earn money first, not the ones that are easiest to test.
Most failures trace back to a short list of causes: oversized images, slow server response, third party scripts, and content that gets injected after the page starts rendering. Work down this list in order. The first four items usually handle most of the LCP and CLS problems on small business sites, and they are the cheapest to do.
INP is the least intuitive of the three, and it is where script heavy sites tend to struggle. It is caused by JavaScript occupying the browser at the moment someone taps, which is why sites loaded with chat widgets, heat maps and analytics tags feel sticky even when they look fast. Removing scripts you are not actively using is the single highest leverage INP fix available to a non developer.
Your cost depends on one question: is the problem your content or your platform? Compressed images and a caching layer solve a content problem quickly and cheaply. If the bloat is generated by the theme or page builder on every single page, you are looking at a rebuild, and no plugin will save you. Diagnose before you buy anything.
At Kihan Marketing, website design starts at $5,000, SEO starts at $1,500 per month and includes technical work like this, and growth packages start at $3,000 per month. Everything is month to month with no long term contract. If you just want a straight answer on whether your site needs a tune up or a rebuild, call (425) 954-3452 and ask.
| Option | Effort | What it typically fixes | Realistic timeline |
|---|---|---|---|
| Image compression and resizing | A few hours, often DIY | LCP on image heavy pages | Same day, field data catches up in about 4 weeks |
| Caching plus a CDN | Half a day | Slow server response, repeat visits | Same day |
| Better hosting | An afternoon plus migration | Slow time to first byte on cheap shared plans | 1 to 2 weeks including DNS |
| Cutting third party scripts | Half a day plus internal buy in | INP, and LCP on script heavy pages | About a week |
| Developer cleanup of theme and scripts | Several days of focused work | Render blocking assets, page builder bloat, INP | 2 to 4 weeks |
| Rebuild on a lighter stack | Full project | Everything, when the platform itself is the cause | Typically 6 to 12 weeks |
Ask for this before you sign anything
Any agency quoting Core Web Vitals work should show you the field data for your top pages first, and name which metric is failing and why. If they lead with a Lighthouse score, keep looking.
If your pages are not ranking on page one at all, Core Web Vitals is not your bottleneck. Google does not promote a page from position 40 because it got faster. Sites in that position almost always have a relevance problem, a page depth problem, or no authority, and speed work will feel like it did nothing because it did do nothing for rankings.
Here is a workable order of operations. If your target pages already sit in the top 20, fix the vitals, because you are competing on tiebreakers. If they sit below that, put your budget into pages that actually match what people search for and into earning links, and treat vitals as maintenance. On the SEO side generally, expect early movement in weeks and meaningful traction in 60 to 90 days.
One exception cuts across all of it. If your site is slow enough that visitors bail before it renders on a phone, fix it now, whatever your rankings look like. That is not an SEO decision, it is money leaving the building while you debate it.
Quick decision rule
Already ranking and stuck, fix Core Web Vitals. Not ranking yet, fix content and authority first. Losing mobile visitors before the page loads, fix speed today either way.
Yes, but modestly. Core Web Vitals are part of Google’s page experience signals, and Google has been consistent that relevance and authority matter more. Passing will not rescue a thin page with no links pointing at it. Where vitals do help is between pages that are otherwise close in quality, and on mobile, where slow pages lose visitors before Google’s ranking has a chance to matter. The practical way to think about it: treat Core Web Vitals as a conversion and quality project that carries a small ranking benefit alongside it.
A page passes when LCP is 2.5 seconds or less, INP is 200 milliseconds or less, and CLS is 0.1 or less, measured at the 75th percentile of real visits over 28 days. All three must pass, and mobile is scored separately from desktop, so a page can pass on one and fail on the other. There is no partial credit, and no extra benefit to going far below the thresholds. Once you are green, your time is better spent on content, offers and internal links than on shaving another 200 milliseconds.
Because they measure two different things. The score out of 100 comes from Lighthouse, a simulated test run once, from one location, under assumed conditions. Search Console reports field data: what actually happened to real Chrome visitors on real devices and real networks over the past 28 days. Your visitors include people on older phones and weak cell signal, and they pull your 75th percentile up. When lab and field disagree, the field data is the one Google uses. Use the lab score only to find causes, never to declare victory.
Plan on roughly four weeks before the report moves, because Google uses a rolling 28 day window of real visits. Nothing is broken if the chart looks flat a week after your fix. Verify the change the same day with a lab test in Chrome DevTools, confirm the file sizes and scripts really changed, then leave the report alone. If you keep shipping changes every few days you will never get a clean read on which one worked. Fix, verify in the lab, then wait out the window.
WordPress itself is not the problem, the stack built on top of it usually is. The common culprits are a heavy page builder that ships enormous CSS on every page, a theme loading sliders and icon libraries nobody uses, unoptimized images straight from a phone camera, and a long tail of plugins that each add scripts sitewide. A well built WordPress site passes comfortably. Test before you conclude anything. If the platform genuinely cannot be salvaged, a rebuild is the honest answer, and at Kihan Marketing website design starts at $5,000.
Fix them first only if you are already ranking. If your important pages sit in the top 20 and are stuck, speed and stability are a sensible tiebreaker to go after. If you are on page four or nowhere at all, the bottleneck is relevance, page depth and authority, and no amount of speed work will change that. One exception overrides this: if your pages load so slowly on mobile that people leave, fix it now regardless of rankings, because that is lost revenue, not lost position.
It depends entirely on whether the cause is content or platform. Compressing images, enabling caching and cutting three unused tracking scripts is a short piece of work that a competent developer can do in a day. A site where the page builder itself generates the bloat is a rebuild, and quotes vary widely by scope, so get the diagnosis before you accept any price. At Kihan Marketing, SEO starts at $1,500 per month and includes technical work like this, growth packages start at $3,000 per month, month to month with no long term contract. Call (425) 954-3452.
Kihan Marketing gives you a written scope and price within one business day. No pressure, and nothing to sign to see it.
Or call us directly: (425) 954-3452
Tell us about your project and we will be in touch within one business day.
Three simple steps from first hello to real results.
Fill out the form and tell us about your goals.
A custom strategy and design built to rank and convert.
Launch, then measurable growth month over month.
