Core Web Vitals is one of those topics where every article assumes you already know what it means, and none of them tell you what to actually do about it.
Here is the plain version, plus the fixes that actually move the number on a real Tampa small business website.
What Core Web Vitals Actually Are
Google measures three things about how your page feels to a real person on a real device:
- LCP — Largest Contentful Paint. How long until the main thing appears. Target: under 2.5 seconds.
- INP — Interaction to Next Paint. How quickly the page responds when someone taps. Target: under 200 milliseconds.
- CLS — Cumulative Layout Shift. How much the page jumps around while loading. Target: under 0.1.
That is genuinely it. Everything else is implementation detail.
LCP: Why Your Page Feels Slow
LCP measures when the biggest visible element — usually your hero image or headline — finishes rendering. If that takes four seconds, your visitor spent four seconds looking at a blank white screen wondering whether their phone is broken.
What breaks it
- Enormous hero images. A 4MB photo straight off a phone camera is the single most common cause.
- Render-blocking CSS and JavaScript loading before anything can paint.
- Slow hosting. A cheap shared server takes 800ms just to start responding.
- Web fonts blocking text from rendering.
How to fix it
- Compress and convert images to WebP. A 4MB JPEG becomes a 180KB WebP with no visible quality loss. This one change fixes most LCP problems by itself.
- Size your images correctly. Do not serve a 3000px-wide image into a 400px-wide slot on a phone.
- Preload the hero image. Tell the browser to fetch it immediately rather than discovering it later.
- Defer non-critical JavaScript. Nothing above the fold should wait on an analytics script.
- Use decent hosting. Server response time under 200ms. See our hosting plans.
- Use
font-display: swap. Show text in a fallback font immediately rather than showing nothing.
INP: Why Your Page Feels Broken
Someone taps your menu button. Nothing happens. They tap again. Then the menu opens twice. That is bad INP, and it is infuriating in a way that people remember.
What breaks it
- Heavy JavaScript hogging the main thread so the browser cannot respond to taps.
- Too many third-party scripts — chat widgets, tracking pixels, review embeds, all fighting each other.
- Page builders running enormous amounts of JavaScript for layouts that should be plain CSS.
How to fix it
- Audit third-party scripts ruthlessly. Every chat widget, pixel, and embed has a cost. Most are not earning it.
- Break up long JavaScript tasks so the browser can respond between them.
- Lazy-load below-the-fold widgets — chat, maps, video embeds — so they do not compete during initial load.
- Drop the page builder. This is a recurring theme. See our WordPress vs custom code breakdown.
CLS: Why the Page Jumps and You Tap the Wrong Thing
You go to tap "Call Now." An ad loads above it, everything shifts down, and you tap "Terms and Conditions" instead. That is layout shift, and it is the most viscerally annoying of the three.
What breaks it
- Images without width and height attributes, so the browser does not reserve space.
- Ads and embeds injected without a reserved container.
- Web fonts swapping and changing text dimensions.
- Content injected above existing content after load — banners, popups, notification bars.
How to fix it
- Always set width and height on images. Always. This is a five-minute fix that solves most CLS problems.
- Reserve space for ads, embeds, and iframes with a fixed-height container.
- Preload fonts and use a size-adjusted fallback so the swap does not change dimensions.
- Never inject content above the fold after load.
How to Actually Test
- Google Search Console → Core Web Vitals report. This is field data from real users on real devices. It is the one that counts.
- PageSpeed Insights. Gives both lab data and field data. Use the field data. The lab score is a simulation.
- Your own phone, on cellular, away from your wifi. Honestly the most useful test there is.
The mistake almost everyone makes
Testing on a desktop, on office wifi, and concluding the site is fast. Google measures mobile field data from real users on real connections. Your site can score 95 in a lab simulation and fail in the field.
The Fixes That Actually Matter
In order of impact on a typical Tampa small business site:
- Compress images and convert to WebP. Usually fixes LCP outright.
- Set width and height on every image. Usually fixes CLS outright.
- Remove unused plugins and third-party scripts. Usually fixes INP.
- Move to decent hosting. Cuts server response time.
- Defer non-critical JavaScript.
- Drop the heavy page builder. The biggest structural fix, and the hardest.
Steps one and two take an afternoon and fix most sites. Everyone skips them and buys a caching plugin instead.
What Is Not Worth Doing
- Chasing a 100 score. Diminishing returns past "passing." Green is green.
- Installing four caching plugins. They conflict and make things worse.
- Optimizing desktop while mobile fails. Google measures mobile.
- Micro-optimizing before compressing your images. That 4MB hero is still a 4MB hero.
Does This Actually Affect Rankings?
Yes, but it is a tiebreaker, not a trump card. A fast page with weak content will not outrank a slow page with excellent content that genuinely answers the query.
Where speed matters enormously is conversion. Every second of load time costs you visitors, and past three seconds the drop-off is severe. The ranking benefit is real but secondary — the revenue benefit is direct and immediate. That is why we treat speed as a conversion issue first and an SEO issue second.
People Also Ask
What are Core Web Vitals?
Three measurements of how a page feels to a real user: LCP (how long until the main content appears, target under 2.5 seconds), INP (how fast the page responds to a tap, target under 200 milliseconds), and CLS (how much the layout jumps while loading, target under 0.1).
Do Core Web Vitals affect Google rankings?
Yes, but as a tiebreaker rather than a primary factor. A fast page with weak content will not outrank a slow page with excellent content. Where speed matters most is conversion — every second of load time costs visitors, and past three seconds the drop-off is severe.
How do I improve my LCP score?
Compress your images and convert them to WebP — this alone fixes most LCP problems. Then size images correctly for their display slot, preload the hero image, defer non-critical JavaScript, and use hosting with a server response time under 200 milliseconds.
What causes layout shift on a website?
Images without width and height attributes, so the browser does not reserve space. Ads and embeds injected without a fixed container. Web fonts swapping and changing text size. Banners injected above existing content after load. Setting explicit image dimensions fixes most of it.
How do I test my website speed properly?
Use the Core Web Vitals report in Google Search Console — that is field data from real users on real devices, and it is what Google actually measures. Then open your site on your own phone on cellular data, away from wifi. Testing on a desktop on office wifi tells you almost nothing.
Want this handled for you?
Book a free thirty-minute strategy call. We will look at your site, your Tampa competitors, and tell you exactly what is costing you leads — even if you never hire us. Schedule a call →