Core Web Vitals: why a fast website earns more

Core Web Vitals are three metrics defined by Google to measure how fast, responsive, and visually stable a web page feels to your actual visitors. They don't reward a theoretical lab score; they capture the real experience of someone opening your site on their phone, on an average connection. A site that meets them loads quickly, responds instantly to taps, and never makes content jump just as a visitor is about to press a button.

For a small business, a shop, or a craftsperson, these metrics aren't a technical footnote: they shape both your ranking in Google results and the share of visitors who actually become customers. A slow site is penalized twice over: less visible, and less persuasive.

“

According to recurring industry studies, every additional second of load time drops conversion rates by roughly 7 percent, and more than half of mobile visitors abandon a page that takes longer than three seconds to appear.

The three Core Web Vitals to hit are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. These thresholds correspond to a "Good" rating in Google's tools; exceeding them pushes the page into "Needs improvement" or "Poor."

• LCP (Largest Contentful Paint) — aim for under 2.5 s: the time it takes for the largest visible element (often a hero image or headline) to render. It measures perceived load speed. Beyond 4 seconds, the page is rated poor.
• INP (Interaction to Next Paint) — aim for under 200 ms: the delay between a user interaction (click, tap, keystroke) and the page's visible response. INP officially replaced the older FID metric in March 2024, because it measures responsiveness across the entire visit rather than only at the first interaction. Beyond 500 ms, the experience is judged poor.
• CLS (Cumulative Layout Shift) — aim for under 0.1: it quantifies unexpected content shifts during loading. A high CLS is that frustrating moment when a late-loading ad or image bumps the button you were about to tap.

Keep it simple: LCP = speed, INP = responsiveness, CLS = stability.

Improving your Core Web Vitals affects your Google ranking and your conversion rate at the same time. It's rare for a single technical effort to deliver both, and that's exactly what makes it a priority.

On the SEO side, Google folds Core Web Vitals into its ranking signals through page experience. With equal content relevance, the faster, more stable site wins out, especially on mobile, where most local searches happen. For a craftsperson or shop trying to climb for "plumber Lille" or "bakery Roubaix," that's a direct lever.

On the conversion side, the effect is even more measurable. Every point of friction, whether a second of waiting, a button that shifts, or a form that lags, costs you customers. A frustrated visitor doesn't get in touch, doesn't add to cart, doesn't book an appointment. Speed isn't a comfort: it's a silent sales argument.

You can measure your Core Web Vitals for free in a few minutes using three complementary Google tools. None requires technical skill to get a first diagnosis.

• PageSpeed Insights: paste your page URL, and the tool shows your mobile and desktop scores along with concrete recommendations. It separates "field" data (your real visitors) from "lab" data (a simulated test).
• Lighthouse: built into Chrome's developer tools, it audits a page on demand and quantifies each metric. Ideal during the design phase.
• Search Console: its dedicated Core Web Vitals report monitors your whole site over time and groups pages by issue type. This is the tracking tool to check every month.

Always prioritize field data: it reflects the real experience on real devices, and it's what Google uses for ranking.

A custom-built Next.js site meets Core Web Vitals thresholds natively because performance is baked into the architecture rather than bolted on afterward. Where a WordPress template piles up plugins, heavy themes, and superfluous scripts, a custom site loads only what it strictly needs.

• Server rendering and static generation: pages are pre-computed and delivered ready to display, driving LCP well under 2.5 s.
• Automatic image optimization: modern formats, per-screen sizing, and lazy loading, with no manual tuning. Images, the leading cause of a slow LCP, stop being a problem.
• Code splitting: the browser downloads only the JavaScript for the page being viewed, lightening INP and tap responsiveness.
• Reserved element space: dimensions are set in advance, eliminating the shifts that wreck CLS.
• Very few third-party scripts: no cascade of plugins slowing every load, unlike a bloated WordPress install.

A generic template starts with a structural handicap: it's designed to do "a little of everything," at the cost of being lightweight. A custom build flips the logic by constructing exactly the site your business needs.

Start by measuring your homepage and your most-visited page in PageSpeed Insights: that's your baseline diagnosis. Note your three current scores, then tackle the high-impact work.

• Compress and resize your images: this is almost always the first lever on LCP.
• Remove unnecessary scripts: every non-essential widget, chat, or tracker weighs on INP.
• Set fixed dimensions for images and embeds to stabilize CLS.
• Re-audit every month in Search Console to track the trend.

If your site runs on a heavy template and scores stay flat despite your efforts, the problem is usually structural. That's precisely where a custom Next.js rebuild changes the game, turning performance into a lasting advantage rather than a permanent battle.