Back to Blog
    WEB DEVELOPMENT
    10 min read•Mathew Metz, Head of Web Development•July 29, 2026

    Core Web Vitals: Speed Up Your Website (2026)

    LCP, INP, CLS — Google measures how fast (and stable) your site feels. This guide explains every Core Web Vital, the fixes that actually move the numbers, and the speed kills you should fix first.

    Quick Answer

    Core Web Vitals are three Google metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — that measure how fast and pleasant your site feels. They're part of Google's Page Experience signal, and for competitive keywords they decide tiebreakers. Google's own research says every second of delay costs roughly 7% of conversions.

    The good news: most SMB sites can pass all three vitals with image optimization, removing render-blocking scripts, and cleaning up plugins — no redesign required. Here's the exact playbook.

    Sources & further reading: Metric definitions and "Good" thresholds follow Google's Core Web Vitals documentation and the Page Experience ranking guide on Google Search Central. Tooling references: PageSpeed Insights, Lighthouse, and web.dev's INP optimization guide. Conversion-loss and bounce-rate statistics come from Google-published research, including the Deloitte-co-authored Milliseconds Make Millions study and Google's mobile load-time analysis.

    The Three Vitals, Explained in Plain English

    MetricFull nameWhat it measures"Good" target
    LCPLargest Contentful PaintTime until the main content (hero image, headline) appears≤ 2.5s
    INPInteraction to Next PaintHow quickly the page responds to clicks/taps/keys≤ 200ms
    CLSCumulative Layout ShiftHow much the page jumps around while loading≤ 0.1

    LCP = "How fast does the good stuff appear?" It's the big hero image, the headline, the product photo. Until that renders, the visitor sees a blank or skeleton page.

    INP = "How snappy does it feel when I click?" Replaced FID in 2024 because FID only measured the first tap. INP measures every interaction, which is a much tougher (and more honest) test — especially with lazy-loaded sections.

    CLS = "Does the page jump around?" When an image pops in, a font swaps, or an ad loads, content shifts under the visitor's finger. On mobile, a 0.1+ CLS means people tap the wrong button.

    Why Speed Matters Beyond the Score

    Passing CWV isn't about satisfying Google — it's about revenue.

    • ��Conversion loss: Google research found a 7% conversion drop per second of delay. A site loading 3 seconds slower quietly burns a fifth of its leads.
    • ��Bounce rate: the probability of a bounce jumps ~32% as load time goes from 1s to 3s (Google's analysis of mobile sessions).
    • ��Ad costs: if you run Google Ads or Meta Ads, landing page speed is part of quality score. Slow landing pages pay more per click and convert worse — a double tax.

    The number we track in our audits: for a client getting 2,000 monthly visits at 2% conversion with a $1,500 lead value, going from a 6s to a 2s load means roughly $1,800/mo more revenue — before any traffic increase.

    How to Check Your Core Web Vitals (10 minutes)

    1. ��PageSpeed Insights (pagespeed.web.dev) — gives lab data, field data when available, and a prioritized fix list. Start here.
    2. ��Search Console → Core Web Vitals report — shows real-user data from Chrome, split by mobile/desktop, and flags which URLs fail. This is the truth report.
    3. ��Chrome DevTools → Performance tab — for digging into why (which script is blocking, which image is heavy) after you know what fails.

    Run the report on your money pages (home, services, pricing, product) first — not the blog. Those are the pages that earn.

    The Fix Playbook, in Order of Impact

    1. Images (usually fixes LCP)

    • ��Compress everything (WebP/AVIF at 80% quality beats JPEG by 30–60% file size).
    • ��Resize to the actual display width — a 2,000px hero on a 400px phone screen is waste.
    • ��Use
      srcset
      so phones get small files.
    • ��Add
      width
      and
      height
      attributes or
      aspect-ratio
      CSS so space is reserved (this also fixes CLS).

    2. Render-blocking scripts (usually fixes INP)

    • ��Defer or async every non-critical script.
    • ��Audit third-party scripts: chat widgets, pixel trackers, map embeds, review badges. Each one costs load time. Keep the ones that make money; remove the ones that don't.
    • ��Inline critical CSS and load the rest asynchronously.

    3. Fonts

    • ��Self-host fonts (Google Fonts via CDN creates extra connections).
    • ��Use
      font-display: swap
      so text shows immediately.
    • ��Serve only the weights you actually use.

    4. Server / hosting (the ceiling on everything else)

    • ��A slow server caps how fast your site can possibly be. If you're on shared budget hosting, a decent VPS or managed WordPress host is the single best upgrade. See our VPS hosting comparison.

    5. For WordPress sites: plugin diet

    • ��Every plugin adds CSS and JS. 30 plugins = 30 chances to slow you down. If the bloat has drifted past cleanup territory, our WordPress development guide covers when a properly scoped rebuild is the faster fix.
    • ��Replace heavyweight plugins with lighter equivalents.
    • ��Use a caching plugin (and a CDN for static assets) once the rest is clean.

    Common Speed Kills We Find in Real Audits

    • ��Autoplay videos and carousels — the #1 self-inflicted LCP wound. A looping background video can add megabytes per page view.
    • ��Uncached database queries on WordPress/WooCommerce sites.
    • ��Tracking everywhere. Ten pixels measuring the same thing isn't ten times smarter.
    • ��Multi-MB "hero sliders" that delay LCP by definition.

    The Business Case for Speed

    Speed is cheap to fix and compounds:

    • ��It's part of SEO (Page Experience + better crawling).
    • ��It lifts conversions on the traffic you already have.
    • ��It lowers Google Ads / Meta Ads costs through better landing page quality.
    • ��It improves retention — a fast site builds trust; a slow one reads as "this business is disorganized".
    • ��It protects the budget you already have — speed work costs a fraction of a rebuild, as our small business website cost breakdown shows.
    • ��It decides checkout completion for online stores — every second of delay at cart is abandoned revenue, counted line by line in our e-commerce website cost guide.

    We've taken client sites from 6–8 second loads down to under 2.5s LCP in a few weeks with no redesign — just images, scripts, and hosting. If your audit surfaces deeper problems than speed (dated design, weak mobile UX), those are rebuild signals — our website redesign guide covers when a refresh beats another patch. And when the slowdown is architectural — bloat baked into the framework itself — custom web development is how you own the performance ceiling outright.

    Next Steps

    Run your money pages through PageSpeed Insights right now. If any fail the "Good" threshold, you have a measurable problem with a measurable fix. Want it handled? Get a free performance audit and quote, or check what your new build should cost with the website cost calculator.

    Related Website Cost Guides

    Methodology

    Metric definitions and "Good" thresholds (LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1) were verified against Google's official documentation on web.dev and Google Search Central in July 2026. Conversion-loss and bounce-rate figures cite Google-published research: the Deloitte-co-authored Milliseconds Make Millions study and Google's mobile load-time analysis. The revenue example is illustrative, calculated from a typical SMB profile (2,000 monthly visits, 2% baseline conversion, $1,500 average lead value); actual results vary by traffic mix, industry, and deal size. Fix recommendations reflect patterns observed across Orometa performance audits of small-business sites built on WordPress, Shopify, and custom stacks.

    About the Author

    Mathew Metz leads the web development team at Orometa, having designed and launched 180+ high-performance websites for SMBs. Specializing in conversion-optimized design, mobile-first development, and performance engineering, he helps businesses turn visitors into customers. With a focus on user experience and measurable business outcomes, he combines technical excellence with strategic thinking.

    Connect on LinkedIn

    MM

    ABOUT THE AUTHOR

    Mathew Metz

    Head of Web Development

    Mathew Metz leads the web development team at Orometa, having designed and launched 180+ high-performance websites for SMBs. Specializing in conversion-optimized design, mobile-first development, and performance engineering, he helps businesses turn visitors into customers. With a focus on user experience and measurable business outcomes, he combines technical excellence with strategic thinking.

    Connect on LinkedIn

    Frequently Asked Questions

    What are Core Web Vitals?+
    Core Web Vitals are three Google measurements of user experience: LCP (loading speed), INP (responsiveness), and CLS (layout stability). They're part of the Page Experience ranking signal, alongside HTTPS, mobile-friendliness, and intrusive-interstitial penalties.
    What is a good LCP score?+
    Good LCP is 2.5 seconds or faster. Needs improvement is 2.5–4.0s; poor is anything over 4.0s. LCP measures when the main content of a page becomes visible to the user.
    What is INP and why did it replace FID?+
    INP (Interaction to Next Paint) measures how quickly a page responds to all user interactions — clicks, taps, and keystrokes — throughout a visit. It replaced FID because FID only measured the first interaction. The good threshold is under 200 milliseconds.
    How much does website speed affect SEO rankings?+
    Significantly, but not as a pure "speed score". Google uses CWV as part of Page Experience, and for heavily-competitive keywords, a slow site loses tiebreakers. More importantly, speed directly affects conversion — every second of delay costs roughly 7% of conversions, per Google's own research.
    What is the most common cause of poor Core Web Vitals?+
    Unoptimized images and render-blocking scripts are the top two causes on SMB sites. Huge hero images kill LCP, and slow third-party scripts (chat widgets, trackers, map embeds) kill INP. Both are fixable without a redesign.
    How do I check my Core Web Vitals?+
    Use Google PageSpeed Insights (field + lab data), Google Search Console's Core Web Vitals report (real users), and Chrome DevTools for debugging. PageSpeed Insights is the fastest way to get a diagnosis with a specific fix list.

    Ready to Transform Your Business?

    Let Orometa implement these strategies for your business. Our team specializes in digital marketing, SEO, web development, and AI automation.

    Get a Free Strategy Call