A slow website costs you visitors. People leave before the page finishes loading, and the ones who stay are less likely to call, book, or buy. Here’s how Google measures speed, how to test your own site, and which fixes you can make yourself.
What “fast” means: Core Web Vitals in plain English
Google uses three measurements, called Core Web Vitals, to judge how a page feels to a real visitor. Each one answers a simple question:
- Loading: “Is it there yet?” Largest Contentful Paint (LCP) measures how long it takes for the main thing on screen, usually the big image or headline, to appear. Good is 2.5 seconds or less.
- Responsiveness: “Does it react when I tap?” Interaction to Next Paint (INP) measures how quickly the page responds when someone clicks a button or opens a menu. Good is 200 milliseconds (a fifth of a second) or less.
- Visual stability: “Does it stop jumping around?” Cumulative Layout Shift (CLS) measures how much the page moves while it loads, like when you go to tap a link and an image pushes it down. It’s a score, not a time. Good is 0.1 or less.
Google judges these on real visits, mostly on phones, and wants three out of four visits to hit the “good” mark. Core Web Vitals are part of how Google ranks pages, but they’re a tiebreaker: a fast page won’t outrank a more relevant one. The bigger payoff is visitors who stick around.
How to test your site
- Go to
pagespeed.web.dev, Google’s free PageSpeed Insights tool. - Enter the address of a page and click
Analyze. Test your homepage and your most important inner pages, not just the homepage. - Look at the top section first. It shows how real visitors experienced the page over the past month. Low-traffic sites may see a “not enough data” message here, which is normal.
- Scroll down to the lab test. It runs a fresh test, gives a score out of 100, and lists what’s slowing the page down.
- Switch between the
MobileandDesktoptabs. Mobile scores are almost always lower, and mobile is the one to focus on.
Don’t chase a perfect 100. The lab score shifts a few points from one run to the next. The real-visitor results tell you whether there’s a problem, and the lab suggestions tell you why. If you use Google Search Console, its Core Web Vitals report shows the same picture across your whole site.
The usual causes
- Huge images. Photos straight from a camera or phone can be several megabytes each and far wider than any screen. This is the most common cause of slow loading, and the easiest to fix.
- Too many plugins and scripts. Chat widgets, pop-ups, tracking pixels, social feeds, sliders, and duplicate analytics all add code each visitor has to download and run. The weight matters more than the count: one heavy add-on can do more damage than ten light ones. Heavy scripts are the usual cause of poor responsiveness.
- Embeds that load up front. Background videos, several YouTube videos, or embedded maps on one page all load before anyone asks for them.
- Cheap or crowded hosting. Budget plans often put many sites on one server, so your pages wait in line before they even start loading.
- No caching. Without caching, the server rebuilds every page from scratch for every visitor. A cache keeps a ready-made copy to hand out instantly. A CDN (content delivery network) goes further, serving copies from servers close to each visitor.
- Outdated software. Older versions of your website’s platform and the server software it runs on are often slower, as well as less secure.
- Things that pop in late. Images without set dimensions, banners, and cookie notices that appear after the page loads are what make the layout jump.
What you can do yourself
- Resize and compress images before you upload them. Make them no bigger than they’ll ever be shown. For most sites, a couple of thousand pixels wide is plenty, even for a full-width photo. Free tools like Squoosh can shrink a file a lot without visibly hurting quality.
- Question every add-on. Does each chat widget, pop-up, and tracking pixel still earn its place? Ask whoever manages your site before removing plugins yourself, since some depend on each other.
- Go easy on embeds. Link to videos and social feeds instead of embedding several on one page.
- Test before and after. Run PageSpeed Insights on a page before you change it and again after, so you know what helped.
What needs a developer or your host
- Setting up and fine-tuning caching and a CDN
- Upgrading or moving your hosting
- Updating server software and your site’s platform safely
- Making the site deliver the right image size to each device, and loading lower images only as visitors scroll
- Delaying or removing scripts that block the page, and finding which ones hurt responsiveness
- Replacing a heavy theme or page builder when it’s the root of the problem
Related guides: Domain, hosting, and email: who does what · Adding & managing images
If you’re a GORGEOUS client, open a ticket and we’ll find out what’s slowing your site down. Not a client yet? Get in touch.