It’s a Thursday evening, and a shopper waiting for the bus sees an ad for a cosmetics e-shop. She taps it, the screen stays white, the banner eventually appears, and just as she goes to tap “Add to cart,” the page jumps and opens something else. She closes the tab. The click was paid for, but the order never happened. This is exactly the scenario Core Web Vitals describe: three Google metrics that capture how pleasant or frustrating a page is for a real person.
In this article we’ll cover what each of the three metrics means without the jargon, how to run a first check yourself with free tools, where time is usually lost, and in what order to tackle the fixes so you don’t spend money in the wrong places.
At a glance
- The three metrics measure loading (LCP), responsiveness to taps (INP) and layout stability (CLS).
- Google judges based on visits from real users, mostly on mobile, not on a single test run from your office.
- Most delays come down to a few usual suspects: heavy images, a slow server and too many third-party scripts.
- Start with the pages that bring in revenue, and measure again after every change.
What Core Web Vitals measure, in plain English
Think of a brick-and-mortar store. When you walk in, you first want the lights on so you can see the shelves. Then, when you ask a question, you want the clerk to answer right away. And of course, you don’t want the shelves moving while you reach for something. Google’s three metrics map exactly onto these three expectations.
| Metric | The question it answers | Target for “good” |
|---|---|---|
| LCP – Largest Contentful Paint | How long does it take for the main element on screen to appear, e.g. the product photo or the large headline? | Up to 2.5 seconds |
| INP – Interaction to Next Paint | How quickly does the page react to a tap, a click or typing? | Up to 200 ms |
| CLS – Cumulative Layout Shift | How much does the content “dance around” while loading finishes? | Up to 0.1 |
INP replaced the older FID, so if you see FID mentioned in an old guide, know that what counts now is overall responsiveness across every interaction during a visit, not just the first one.
Why the “slow” visitor counts, not the fast one
Google doesn’t look at the average. For a page to be rated good, it has to hit the target for 75% of visits. In other words, the person on an older phone with a weak signal at the port of Piraeus counts too, not just you with your new laptop and the office fiber connection. Results are reported separately for mobile and desktop.
What does your business gain from a fast site?
Speed is often treated as “the developer’s problem.” In practice, it affects three very specific things that matter to every business owner.
- Sales and inquiries. Every moment of waiting is a chance for the visitor to think “I’ll check it out later.” Impatience runs highest on product pages and at checkout, because that’s where the customer has already decided and just wants to get it done.
- Organic visibility. Page experience is one of Google’s ranking signals. You won’t outrank a far better article just because you load faster, but when two pages are equally good, the faster one has the edge.
- Ad performance. In Google Ads, landing page experience affects your Quality Score. A slow landing page means you’re paying for clicks that are lost before your offer even appears.
Speed isn’t decoration. It’s the hallway between the click you paid for and the order you’re waiting for.
How to check your website speed yourself
You don’t need subscriptions to expensive tools for a first diagnosis. Follow the steps below and take notes, so you have a baseline to compare against later.
- Pick five key pages. Your homepage, your two most popular product or service pages, the cart or contact form, and the page your ads send people to.
- Run them through PageSpeed Insights. At the top you’ll see data from real users, if the page gets enough traffic. Below that is a simulation with a list of suggestions.
- Open Google Search Console. The relevant report groups your pages into “good,” “needs improvement” and “poor,” separately for mobile and desktop.
- Test it with your own hands. Grab an average phone, turn off Wi-Fi and complete a purchase or an inquiry from start to finish.
Field data or lab data?
This distinction confuses a lot of people. Field data is collected from real visits over the last 28 days, and it’s what Google takes into account. Lab data is a one-off test under specific conditions. It’s invaluable for finding the cause of a problem, but it isn’t your “score.” If the two disagree, trust the field data. You’ll find more on why mobile is always the top priority in our guide to a mobile-friendly website.
Where time is usually lost
Group the causes by the metric that’s “in the red,” so you know right away where to look.
When content is slow to appear (poor LCP)
- Oversized photos. A 5,000-pixel image in an 800-pixel frame is the most common culprit. Reduce the dimensions, compress, and prefer formats such as WebP or AVIF.
- Slow server response. If the server takes a long time to send the first byte, no other improvement will make up for it. Hosting quality and caching play a role here, a topic we cover in our article on hosting for WooCommerce.
- A heavy slider or video above the fold. Three rotating photos or an autoplaying video often weigh as much as the rest of the page combined. One strong image with a clear message does a better job.
When the page is slow to respond (poor INP)
- Too many third-party scripts. Chat widgets, pop-ups, pixels, embedded maps and social media feeds all run code on the visitor’s phone. Keep only the ones you actually use, and load them only where they’re needed.
- Plugins that load everywhere. A form plugin doesn’t need to load on every product page. Selective loading and deferring JavaScript that isn’t immediately needed free up the browser.
When content shifts around (poor CLS)
- Images and iframes without declared dimensions. The browser doesn’t know how much space to reserve, so it pushes the text down as soon as they load.
- Banners and bars that appear later. A promo or cookie bar that “drops in” from the top shifts the whole page. Reserve its space from the start, or display it as an overlay.
- Fonts that change size. Fewer font families and weights, loading them from your own server and the right display settings all reduce the effect.
Common mistakes when improving Core Web Vitals
We often see businesses spend time on moves that don’t deliver results. The classics:
- Chasing a “100.” The simulation score is only indicative. The goal is for real users to land in the green zone, not a round number.
- Three optimization plugins at once. When two tools do the same thing, they usually clash and break features such as the cart.
- Checking only the homepage. Customers often never pass through it. They land directly on a product page from Google or from an ad.
- Fixing it once and forgetting about it. A new pop-up for a sale or a new plugin is enough to undo the improvement. That’s why speed is part of ongoing WordPress support, not a one-off project.
In what order to tackle the fixes
A logical order saves you effort. Images first, because they’re easy and usually bring the biggest gain. Next, hosting and caching, which affect every page at once. Then third-party scripts and plugins, and finally code details such as fonts and CSS.
If you run an e-shop, prioritize the product, cart, checkout path. It’s the most profitable path and the one that will come under the most pressure during peak periods, which is why a technical speed check is one of the steps in preparing your e-shop for Black Friday. Also keep in mind that because field data covers the last four weeks, improvements show up gradually in Google’s reports.
How FoxWeb can help
Speed is decided on three levels: how the page is built, where it’s hosted and how it’s maintained. At FoxWeb we handle all three together, so no one is left passing the blame to someone else.
An audit based on real data
We measure the pages that generate revenue and hand you a short list of what’s worth fixing first.
Built with lightweight code
In our website development work, we design from the ground up with optimized images and only the scripts that are truly necessary.
Hosting that handles the peaks
Our premium web hosting is tuned for WordPress and WooCommerce, with caching and headroom for high-traffic days.
Frequently asked questions
Do I need a score of 100 in PageSpeed Insights?
No. The score comes from a simulation and varies from test to test. What matters is that the three metrics in your real-visitor data fall within the “good” thresholds.
How long until the improvement shows?
Your visitors feel it from day one. Google’s reports, however, are based on four weeks of data, so it takes about a month for it to be fully reflected.
Will my rankings go up from better speed alone?
Rarely, on its own. Speed strengthens a site that already has useful content and solid SEO; it doesn’t replace them. The most immediate benefit usually shows up in sales and contact inquiries.
Why is my site fast on desktop but slow on mobile?
Phones have less processing power and often a less stable connection, so the same page weight takes a bigger toll on them. That’s why you should always check the mobile results first.
Conclusion
Core Web Vitals aren’t just another technical acronym to worry about. They’re a way to see your website through the eyes of a customer in a hurry. Measure the pages that drive revenue, start with images and hosting, and keep speed on your regular maintenance checklist.
Want to find out what’s slowing down your website? Contact FoxWeb or call us at +30 210 300 57 57 for a speed audit.
