Short answer: A fast website answers quickly, shows its main content soon, responds to clicks and doesn’t jump around while it loads. Measure it in PageSpeed Insights, then work through the server, the files that block the first paint, images, layout space and JavaScript.
Why speed matters
Google’s Core Web Vitals measure real visits for loading, responsiveness and visual stability. Google recommends good scores for success with Search and says they align with what its core ranking systems seek to reward.
Its targets are an LCP within 2.5 seconds, an INP under 200 milliseconds and a CLS under 0.1. Our Core Web Vitals guide explains each one.
What slows a page and what to do
| What slows the page | What to do | Metric it helps |
|---|---|---|
| A slow server answer | Cache pages and avoid chains of redirects | TTFB, then LCP |
| Files that block the first paint | Load less CSS and JavaScript before the content shows | LCP |
| Heavy images | Right size, compressed, modern format, lazy below the first screen | LCP |
| Content that moves | Give images, ads and embeds their space before they load | CLS |
| Long tasks in JavaScript | Break up the work so the page can answer clicks | INP |
From web.dev’s articles on optimizing TTFB, LCP, CLS and INP, read November 4, 2026.
How to speed up your website
- Run PageSpeed Insights on your main pages, on mobile first.
- Check the server answer: cache pages and remove redirect chains.
- Make sure the main image is in the HTML, not added later by a script.
- Resize, compress and convert your images, and lazy load those below the first screen.
- Give every image, ad and embed its width and height or an aspect ratio.
- Load fewer font files and less JavaScript before the page can be used.
- Test again, then watch the real-visit data in the Core Web Vitals report in Search Console.
Our guides go deeper on each step: PageSpeed Insights, TTFB, LCP, CLS, INP, image compression, WebP, lazy loading and website fonts. Our browser caching guide covers repeat visits.
Lab tests and real visits
PageSpeed Insights shows both. Its lab test runs Lighthouse on a simulated mid-tier phone on a mobile network, which helps you find problems.
Its field data comes from the Chrome User Experience Report: anonymized measurements from real Chrome users. When the two disagree, trust the real visits: they show what people got.
What we measured and fixed on our site
On the morning of November 4, 2026, we ran four of our pages through PageSpeed Insights. On mobile the main content appeared within 2 seconds on all four and nothing moved while loading. The server answered in 60 milliseconds or less, with our page cache.
Lighthouse listed two savings: files that block the first paint, up to 1.25 seconds on our inner pages, and longer cache lifetimes, about 300 KiB on repeat visits. That same morning we gave our stylesheets and scripts a year of cache, and our cookie notice script stopped blocking the page.
An hour later the cache savings were down to between 183 and 206 KiB, mostly ad pixels whose cache lifetime Meta and OpenAI set. Our home had no blocking file left; the inner pages still list up to 1.2 seconds, from their stylesheets.
The scores moved more than any of that: 93 to 99 on mobile in the first reading, 85 to 99 in the second. Test more than once before you trust a number.
Before you call a page fast
- LCP is within 2.5 seconds on mobile.
- INP is under 200 milliseconds.
- CLS is under 0.1.
- The server answers quickly, with no redirect chains.
- Images are sized, compressed and lazy below the first screen.
- Every image and embed has its space reserved.
RememberStart with what PageSpeed Insights shows on mobile. The slowest part of the page is where a fix pays most.
If you would rather hand this over, our web design team can do it.
Quick answers about website speed
How fast should a website load?
Google’s targets are an LCP within 2.5 seconds, an INP under 200 milliseconds and a CLS under 0.1, measured on real visits. A page that meets all three gives people a good loading, responding and stable experience.
Does website speed affect SEO?
Google recommends good Core Web Vitals for success with Search and says they align with what its core ranking systems seek to reward. Speed won’t replace relevant content, but poor Core Web Vitals can work against a page.
What slows a website down most?
Usually a slow server response, files that block the first paint, and heavy images. On many pages images make up a large share of the data, so they are often the quickest saving.
How do I test my website speed?
Run PageSpeed Insights. It shows real visits from the Chrome User Experience Report when there is enough data, and a lab test of the page, with the problems to fix.
Why is my mobile score lower than my desktop score?
Because the tests differ. PageSpeed Insights simulates a mid-tier phone on a mobile network for mobile, and a desktop with a wired connection for desktop. Fix what the mobile test shows first: that is the harder case.
Sources
Read on November 4, 2026. Google Search Central: Understanding Core Web Vitals and Google search results. PageSpeed Insights: About PageSpeed Insights. web.dev: Web Vitals, Optimize Time to First Byte, Optimize Largest Contentful Paint, Optimize Cumulative Layout Shift and Optimize Interaction to Next Paint. Our case: four of our pages in PageSpeed Insights on November 4, 2026.