How to check if a website is fast enough for Google rankings

The short answer

Google treats a website as fast enough when it passes the three Core Web Vitals on mobile:

• Largest Contentful Paint (LCP) under 2.5 seconds. How long the main content takes to appear.
• Interaction to Next Paint (INP) under 200 milliseconds. How quickly the page responds when someone taps or clicks.
• Cumulative Layout Shift (CLS) under 0.1. How much the page jumps around while loading.

Pass all three and speed is not holding your rankings back. Fail one and it is worth fixing, but speed is a tie-breaker rather than the whole game. Content, links and local signals still decide most of the result.

Three free ways to check

1. Google PageSpeed Insights. Paste your URL. Ignore the big overall score at first and look at the Core Web Vitals assessment at the top. That section uses real visitor data where Google has enough of it.
2. Lighthouse in Chrome. Open your site, press F12, choose the Lighthouse tab and run a mobile report. This is a lab test on your machine, so treat it as a diagnosis rather than a verdict.
3. Search Console. The Core Web Vitals report shows which URLs Google itself sees as passing or failing, grouped by problem. This is the one that matters for rankings.

Our website speed scorecard runs the first check for you and translates the numbers into plain English.

Lab scores and real-world data are different things

PageSpeed Insights can show a green lab score and a failing real-world result on the same page. The lab test runs once on a simulated device. The real-world data comes from actual visitors on their own phones and connections, and that is what Google uses.

If the two disagree, trust the real-world data. It usually means the page is fine on fast connections but slow on the 4G phones most local customers are using.

What slows most small business sites down

The usual culprits are large unoptimised images, too many plugins or third-party scripts, slow shared hosting, and JavaScript that blocks the page from rendering. Hero sliders and embedded videos above the fold are common LCP killers.

What to fix first

1. Images. Compress and resize them, and make sure the main hero image loads early. This fixes more LCP failures than anything else.
2. Hosting. If the server takes more than 600 milliseconds to respond, no amount of front-end work will rescue the page.
3. Third-party scripts. Chat widgets, tracking pixels and font loaders each add delay. Keep the ones that earn their place.
4. Layout shift. Give images and embeds fixed dimensions so the page does not jump when they load.

Our page speed loss calculator estimates what each second of delay is costing you in enquiries, which helps decide how much effort the fixes deserve. For a full picture that connects speed to SEO, trust and conversion, see the website audit service.