✧ Key takeaways
Your site feels slow to visitors too. Learn what Core Web Vitals mean, how to check them free, and the fixes that matter most.
Your website feels slow to you, so it feels slow to your visitors too. They will not tell you. They will just leave. A page that takes four seconds to load loses a large share of its visitors before they ever read a word, and Google has said openly for years that speed feeds into search rankings. The good news: you do not need to learn to code to fix most of it. This guide covers what Core Web Vitals are, how to check them for free, and the fixes that help most.
What Core Web Vitals actually measure
Core Web Vitals are three measurements Google uses to judge how a page feels to a real visitor. They replaced a pile of older speed scores because they measure experience, not just raw loading time. A page can load fast on paper and still feel broken if it jumps around while you read it.
There are three of them, and each one answers a different question.
Largest Contentful Paint (LCP): how fast does the main thing appear?
LCP measures how long it takes for the biggest visible piece of content to show up — usually the hero image or the main headline. If your visitor stares at a blank page for three seconds, your LCP is three seconds, whatever the rest of the page is doing. Google calls an LCP of 2.5 seconds or less good. Between 2.5 and 4 seconds needs improvement. Over 4 seconds is poor.
Interaction to Next Paint (INP): does the page respond when I click?
INP measures the delay between a visitor doing something — clicking a button, tapping a menu, typing in a form — and the page visibly responding. A page can load quickly and still feel frozen if heavy scripts hog the browser. Google calls an INP of 200 milliseconds or less good. Between 200 and 500 milliseconds needs improvement. Over 500 milliseconds is poor. For most sites, this is the metric that got harder in 2024, when INP replaced the older First Input Delay measurement.
Cumulative Layout Shift (CLS): does the page jump around while I read?
CLS measures how much the visible content moves after it first appears. You know the feeling: you are about to tap a link and an image loads above it, shoving the link down, and you tap an ad instead. That is layout shift, and it is infuriating. Google calls a CLS score of 0.1 or less good. Between 0.1 and 0.25 needs improvement. Over 0.25 is poor. CLS has no seconds attached to it — it is a score, and lower is better.
Those three numbers are the whole game. If all three are green, your site feels fast. If one is red, fix that one first.
Why website speed costs you visitors and sales
Speed is not a technical vanity metric. It shows up directly in your business numbers. Google's own research has repeatedly found that as page load time rises from one second to three seconds, the chance a visitor leaves jumps sharply, and it keeps climbing from there. On mobile, where most traffic now comes from, patience is even thinner — a phone on a patchy connection punishes a heavy page twice over.
Slow pages also convert worse. A shopper who waits for a product image buys less often than one who sees it instantly. And because Google uses Core Web Vitals as a ranking signal, a slow page can rank below a faster page with similar content. Speed is one of the few SEO factors entirely in your control.
The point is not to chase a perfect score. A small business site with green Core Web Vitals and honest content will beat a bloated site with a perfect-looking homepage every time. Fix the worst problem first, then the next one.
How to check your site speed for free
You do not need to pay for a speed tool. Google gives away the two that matter, and they use the same data Google itself uses for ranking.
PageSpeed Insights: the first test to run
Go to PageSpeed Insights, paste in your homepage URL, and wait about thirty seconds. You get a score out of 100 for mobile and desktop, plus your actual Core Web Vitals numbers and a list of specific problems, each with an estimated time saving. Run the test on your homepage first, then on your two or three most visited pages. Mobile matters more than desktop, so read the mobile tab first — that is the score most of your visitors experience.
One warning: run the test twice. Speed scores vary from run to run depending on server load and network conditions. If a number jumps around, trust the rough range, not a single reading.
Google Search Console: the report that shows your whole site
PageSpeed Insights tests one URL at a time. Google Search Console shows you every page on your site, grouped into good, needs improvement, and poor, based on real visits from real users over the past 28 days. In Search Console, open the Core Web Vitals report under the Experience section. It tells you which groups of pages fail and why — slow LCP on your product pages, say, or layout shift on your blog. If you have not set up Search Console yet, our guide to setting up Google Search Console walks through it step by step. This report is the one to check monthly, because it reflects what visitors actually experienced, not a single lab test.
Chrome DevTools and Lighthouse: the deeper look
If you use Chrome, you already have Lighthouse built in. Right-click any page, choose Inspect, open the Lighthouse tab, and run a report. It gives you the same Core Web Vitals numbers plus a longer list of fixes, including which images are oversized and which scripts block the page. You do not need to understand every line of it. Read the top three opportunities and ignore the rest until those are done.
What your numbers mean, in plain language
Google sorts every page into three buckets for each metric. Here is the short version to keep beside your test results.
- LCP — good: 2.5 seconds or less. Needs improvement: up to 4 seconds. Poor: over 4 seconds.
- INP — good: 200 milliseconds or less. Needs improvement: up to 500 milliseconds. Poor: over 500 milliseconds.
- CLS — good: 0.1 or less. Needs improvement: up to 0.25. Poor: over 0.25.
Do not panic over a single red number on one page. Look for patterns: if every blog post fails CLS, you have one fix that helps everywhere. If only your homepage fails LCP, the hero image is the suspect. Patterns point at the fix.
Fixing LCP: make the biggest thing load faster
Most LCP problems come down to one thing: the largest element on the page is too heavy or arrives too late. On most sites that element is an image, usually the big banner at the top. Here is what to do about it, in order of impact.
First, shrink your images before you upload them. A photo straight from a camera can be 5 MB. The same photo resized to the width it actually displays at — often 1200 pixels or less — and compressed can be under 200 KB, and nobody can tell the difference on screen. Use a free compressor like TinyPNG or Squoosh before uploading, or install an image optimization plugin that does it automatically. WordPress users can also switch to the WebP format, which gives the same quality at a smaller file size. This single habit fixes more slow sites than anything else.
Second, look at the hero image specifically. If your homepage opens with a huge background photo or a video, that file is your LCP element, and everything else waits behind it. Use a compressed still image instead of an autoplaying video for the first screen. If you must keep the video, make sure it does not block the headline from appearing first.
Third, check your hosting. A cheap shared hosting plan on an overloaded server can add a full second before anything loads at all. If your server response is slow on every page, no amount of image compression will save you. Our best web hosting for beginners roundup compares hosts on speed as well as price, and moving to a faster host is often the highest-impact fix a non-developer can make.
Fourth, remove the slider. Image sliders load several large images plus the slider script before the visitor sees anything. A single strong image with a clear headline almost always converts better and loads far faster.
Fixing INP: stop the page freezing when people click
INP problems are almost always caused by too much JavaScript — the code that makes buttons, popups, chat widgets, and animations work. Every plugin, tracker, and widget you add runs code in the visitor's browser, and when several of them run at once, clicks get queued behind them.
Start by auditing your plugins. On WordPress, go to your plugins list and ask of each one: does this earn its place? Contact form, yes. Caching, yes. That social sharing bar, the weather widget, the three analytics tools, the live chat you never answer — probably not. Deactivate one, test the page, and see if anything breaks. Most sites carry five to ten plugins they no longer need, and each one costs speed.
Next, look at third-party scripts: chat widgets, ad networks, social media embeds, and tracking pixels. Each one is a separate download from a separate server, and a slow one can freeze the whole page. If you embedded a social feed, that embed loads the platform's code too. A chat widget that nobody uses is pure overhead.
Finally, delay what can wait. Many tools let you load scripts after the main page appears — look for "defer" or "delay JavaScript" settings in your caching plugin. Analytics and chat do not need to load in the first second. Your headline and your call-to-action do.
Fixing CLS: stop the page jumping around
Layout shift happens when the browser does not know how much space something will take until it loads. The fix is to tell it in advance.
The biggest cause is images without dimensions. When you upload an image, make sure its width and height are set — WordPress does this automatically for images added through the editor, but images pasted in as raw HTML often lack them. Without dimensions, the browser reserves no space, the image arrives late, and everything below it jumps down.
Fonts are the second cause. When a page loads a custom font, text often appears first in a fallback font and then swaps, shifting every line. The fix is to use a well-optimized web font with a proper fallback, and to avoid loading five weights of a font family when you only use two.
Ads and embeds are the third cause. An ad slot with no reserved height will shove content down the moment the ad loads. The same goes for embedded videos and social posts. Reserve space for them with a fixed-height container, or accept that an ad in the middle of your article costs you readers as well as earning you money.
The non-developer fix list, in order
If you do nothing else, do these in this order. Each step takes under an hour, and most sites see a visible improvement after the first three.
- Compress every image and resize them to the width they actually display at. Start with the homepage and your most visited pages.
- Turn on caching. A caching plugin stores a ready-made copy of each page so the server does not rebuild it for every visitor. On WordPress, a free caching plugin is a ten-minute install.
- Remove plugins and widgets you do not use. Deactivate, test, then delete.
- Set image dimensions and reserve space for ads and embeds so nothing jumps.
- Check your hosting. If server response is slow on every page, talk to your host or move to a faster plan.
- Use a CDN if your visitors are spread across countries. A content delivery network serves your images from a server near each visitor instead of one server far away.
- Re-test with PageSpeed Insights and compare before and after. Keep the screenshots — they are useful if you ever hire a developer and need to show what changed.
For a deeper explanation of the three metrics and the free tools, our companion article on what Core Web Vitals are and how to check yours for free covers the same ground in a shorter form.
Hosting, caching, and CDNs in plain English
Three words come up in every speed conversation, and they are simpler than they sound.
Hosting is the computer your website lives on. A cheap shared plan puts your site on a server with hundreds of others, and when one of them gets busy, yours slows down. A better plan — or a host that specializes in your platform, like managed WordPress hosting — gives your site more room. If your server response time is over 600 milliseconds on PageSpeed Insights, hosting is part of the problem.
Caching is keeping a ready-made copy. Without caching, your server rebuilds each page from the database for every visitor. With caching, it serves a saved copy instantly and rebuilds it only when the content changes. Most caching plugins also minify your code — removing spaces and comments from files so they download faster — and combine files so the browser makes fewer requests.
A CDN is a network of servers around the world that holds copies of your images and files. A visitor in London downloads your images from a London server instead of your host in Texas. Many hosts include a basic CDN for free, and Cloudflare offers a free plan that covers most small sites. If your audience is in one country, a CDN matters less. If it is global, it matters a lot.
How often should you re-check?
Run PageSpeed Insights after every change you make, so you know which fix actually helped. Then check Search Console once a month — its 28-day data smooths out the day-to-day noise and shows whether real visitors are getting a faster experience. Re-check after any big change: a new theme, a new plugin, a redesign, or a traffic spike.
Speed work is never finished, but it does reach a point of diminishing returns. Once your three Core Web Vitals are green on your most important pages, stop optimizing and go back to publishing. A fast site with thin content loses to a slightly slower site with content people actually want.
The bottom line
Website speed optimization comes down to three numbers — LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1 — and a short list of fixes a non-developer can do in an afternoon: compress your images, turn on caching, remove the plugins and widgets you do not need, give your images dimensions, and check whether your hosting is holding you back. Test with PageSpeed Insights, confirm with Search Console, and fix the worst metric first. Your visitors will not notice the work. They will just stay longer, and that is the whole point.