Page Speed and Core Web Vitals Checker

Google Lighthouse speed and metrics check
The check usually takes 10–30 seconds, or up to 90 seconds for heavy pages. Google runs a browser and performs a full page audit.

Frequently asked questions

Why do mobile and desktop speed differ?

A mobile check models the conditions of an average smartphone on a not-particularly-fast connection – that is closer to the real experience of a noticeable share of visitors than a measurement on a powerful computer with fast internet. That's why the score and Core Web Vitals metrics for mobile are usually lower than for desktop – the gap itself is not a sign of a measurement error, just a result of the different test conditions.

How important is speed for a site's rankings?

Load speed is one of the technical ranking factors, but it weighs less than how well the content matches the query. A more noticeable effect of slow loading is a rise in bounces: some visitors close the page before it finishes loading, which then has a secondary effect on behavioral metrics.

What load speed counts as good?

A rough target is for the visible part of the page to finish loading within a couple of seconds on an average-quality mobile connection. The exact threshold depends on the type of site: it matters more for an online shop than for a page with a single article.

Why does checking the same page again give a different number?

Network conditions and server load change from one measurement to the next, so a small spread in results is normal. It is better to go by a range of values than by a single exact number.

Does every page of a site need to be checked separately?

It is enough to check a few typical templates – the homepage, a product or article page, a category page. Pages sharing a template usually behave similarly in terms of speed.

Does the check account for loading with cached files?

The measurement models the conditions of a new visitor with no browser cache – that is the worst-case and, at the same time, the most common scenario for the part of the audience landing on the site for the first time.

Enter the page URL, choose a device – mobile or desktop – and press "Analyze speed". The tool measures load time separately for each device type, because the results usually differ noticeably.

How to check a page's speed

  1. Enter the page URL. It is better to check a specific page rather than only the homepage – speed can vary a lot across different sections of a site because of differing numbers of images and scripts.
  2. Choose a device. Mobile or desktop – the choice affects the measurement conditions: a mobile check emulates a slower connection and a weaker processor, so mobile numbers are usually worse than desktop ones.
  3. Press "Analyze speed". The check takes a few seconds – the page is actually loaded for the measurement.

What most often slows loading down

  • Heavy images. Uncompressed photos at their original resolution are the most common cause of slow loading.
  • Excessive scripts. A pile of third-party widgets and trackers, each of which blocks part of the load.
  • No caching. The same files being loaded again on every visit.
  • A slow server response. The time to the first byte of data, which does not depend on the size of the files on the page.

The image converter helps compress images before uploading them to a site, and the CSS minifier and JavaScript minifier help cut the weight of CSS and JS files.

What's next

If the speed is fine but the site is still unstable, check basic site availability. For a full picture of technical health, run a comprehensive site audit – speed is checked there alongside indexing and meta tags.