Understanding your application's Google page experience ranking and Lighthouse scores.

Core Web Vitals influence how your application's pages rank on Google. Here, we'll dive into what they are, how they’re measured, and how your users and search ranking are impacted by them.

Link to headingHow Google ranks based on page speed

Your site’s ranking in Google Search is impacted by Google’s page experience ranking system, which evaluates the performance of your site based on Google’s Core Web Vitals metrics.

Google collects Core Web Vitals by observing how real users interact with your website and reporting that back to its servers (more detail about how this works below).

We call this type of data field data because it gets collected from real users browsing your site. This is different from lab data, which is the result of tests run in a "lab setting" to determine how well your site performs. Google’s Lighthouse is an example of a lab test.

Maybe the most important takeaway of this article is this:

Google only considers the Core Web Vitals field data when ranking your site. Google does not consider your Lighthouse score in any way for search ranking.

Link to headingContextualizing search ranking factors

Page experience is a ranking factor in Google Search that utilizes Core Web Vitals to determine how your website performs relative to other sites. Page experience is one of many ranking factors in Google Search, which all get aggregated together to determine your site's ranking on a search result page.

Relevancy to the query and quality of the content are substantially more important factors than page experience. However, for scenarios where you and your competitors have very similar relevancy, page experience may decide who comes out on top.

Where page experience and Core Web Vitals are unique is that:

• You can improve these metrics through your own work.

• Google is transparent about how well you’re doing.

Core Web Vitals are much less of a black box than other ranking factors. Optimizing them involves far less “guesswork” than improving relevancy and is easier to measure than content quality.

On top of that, improving Core Web Vitals improves user experience, which drives conversion.

Link to headingHow to see your application’s Core Web Vitals

The authoritative data source for how well your entire app performs for page experience rankings is Google Search Console.

A simple way to access per-page data is Google’s PageSpeed Insights, which is grouped into two main sections: Core Web Vitals and Lighthouse.

Link to headingField data: Core Web Vitals

In the top section of PageSpeed Insights, labeled “Discover what your real users are experiencing,” Google collects global field data of the 75th percentile of actual users who have accessed your application in the last 28 days from Chrome browser (desktop and Android mobile devices).

Google uses the first three metrics of this real-world data—Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS)—to alter the rank of your application based on the scores. Note that as of March 12, 2024, INP has replaced First Input Delay (FID).

These three Core Web Vitals are the only data Google uses to affect the rank of your app based on its web performance, and the scores seen here are exactly the numbers Google uses, albeit averaged into a group with similarly-performing pages on your application.

You’ll also notice there are tabs for both desktop and mobile. This is because Google ranks your application separately for mobile users vs. desktop users, based on the mobile and desktop versions of your site respectively.

The three metrics beneath the Core Web Vitals can offer further insight into user experience, but do not impact the rank of your application in search.

Link to headingWhich users are included in Core Web Vitals field data?

The Chrome User Experience Report (CrUX) is the official dataset of Google’s Core Web Vitals program, and its collection methodology is publicly documented. Notably, to be included in the report:

• Pages must be “sufficiently popular” and “publicly discoverable.” Whether your pages meet popularity thresholds can be determined via the CWV report in Search Console.

• Users must enable usage statistic reporting, sync their browser history (be signed in to Chrome), and not set a Sync passphrase.

• Users must use Chrome on either desktop or Android.

This last bullet means that none of your iPhone users are counted. This may be relevant insofar that in some markets Android phones skew slower than iPhones, and so a larger percentage of the slower visits to your site may be counted.

If your application does not have enough real user data, then your Core Web Vitals cannot be measured and will not be considered in ranking your application.

Link to headingDoes it matter where my users are coming from?

Another frequent question is: Does it matter where my users are coming from? Do I get penalized if I have lots of users in countries with slower internet connectivity?

It does matter where your users are coming from. The point of field data is that it reflects your real users, and all users from all global regions are counted equally.

The good news is that internet connectivity and device performance have been improving worldwide, and with an edge network like Vercel’s, you can deliver great performance to every user on the planet.

Link to headingCaveat: 28-day sliding window

Google collects Core Web Vitals data on a 28-day sliding window. Your score is essentially the average score of the last 28 days. If you make an improvement—or make things worse—it’s going to be a month before you understand the full impact of that action.

See below how Vercel's Speed Insight can help you get faster access to updated CWV data, so you can react to changes in realtime and prevent ranking regressions.

Link to headingLab data: Lighthouse

In the second section of PageSpeed Insights, labeled “Diagnose performance issues,” Google simulates the performance of your application within Lighthouse, which is the same tool found in Chrome DevTools.

This is a completely distinct section from the field data scores above and is meant as suggestions for improvement if you’re not already meeting Google’s standards for real users.

To reiterate, nothing in Lighthouse counts toward your site’s search ranking. It gives optional guidance that can help you avoid common pitfalls in web app development.

The Lighthouse performance score—one of the most noticeable numbers on the page—is a weighted score of First Contentful Paint (FCP), Speed Index, LCP, Total Blocking Time (TBT), and CLS. Note that, after weighting, actual Core Web Vitals only represent 50% of this score, and INP is not accounted for.

Results here come from a device emulating a Moto G Power with a throttled network connection, which has specs that likely vary greatly from your actual users’ devices.

This and other challenges associated with lab data (such as not accounting for what page a user may be coming from before navigating to the reported page), make Lighthouse scores not suitable as your only UX metric.

For instance, Total Blocking Time (TBT) as a metric often does not reflect real user experience. This is because modern frameworks like React interrupt execution if there is a user event—and hence deliver good INP—but the lab test cannot know that when it is observing how much CPU is being used without real user interactions.

Link to headingInterpreting your Lighthouse scores

Despite challenges with lab data, Lighthouse still provides useful information, especially in narrowing down which parts of your application may be causing issues for your users. For instance:

• Performance - If your Core Web Vitals are not in an acceptable range, Lighthouse points to possible issues, like linking scripts that may be blocking the main thread for too long. It also displays which exact element is being counted as causing your LCP.

• Accessibility - Lighthouse spots common errors such as unnamed links or form fields without labels. It can also screenshot elements that don’t have a high enough contrast ratio or links that don’t have enough space to tap.

• Best Practices - This Lighthouse category is a bit of a catch-all for suggestions that

  improve the security and usability of your applications. Information here will help browsers parse your code more easily and help to prevent some (but not nearly all) common vulnerabilities like XSS.

• SEO - Lighthouse offers advice here about the technical portion of your SEO—the technical ways to help search engines crawl your site. These checks can be very helpful in debugging why your site may not be ranking as you expect, but they’re far from exhaustive in addressing all factors that may affect your app’s SEO.

Link to headingA quicker way to iterate on Core Web Vitals: Vercel Speed Insights

Google’s data is the authoritative source for how your application is ranking in search and performing for your real users. However, as we mentioned above, the data that Google makes available uses a 28-day sliding window.

This means that if you ship an improvement or a regression it can take up to one month to see the full impact. And then, if you need to ship a fix for a regression, it can take yet another month for Google to pick up the improvement.

To maximize your iteration velocity, Vercel created Speed Insights. Since Chromium browsers expose Core Web Vital metrics as users access your site, the Speed Insights package installed on your site accesses these to report your real-time data. Then, you can react quickly, discovering and fixing problems the moment they appear.

Just like all Vercel features tied to unlimited immutable deployments, you can view Speed Insights on a per-deployment or even per-branch basis, allowing you to easily see the effect of each git push on application performance.

Unlike Google’s PageSpeed Insights, you can filter data to smaller windows than the past 28 days, allowing you to see the immediate effects of your changes or to measure arbitrary timespans correlated to large codebase changes.

You can also view individual routes of your application and view data by the 75th percentile of users (Google’s standard) and 90th, 95th, and 99th.

Furthermore, you can filter results by global region, allowing you to better allocate resources to where your actual users reside.

To ensure that the Speed Insights feature can be used despite many different regulatory limitations around the world, we've designed it in such a way that it provides you with information without being tied to, or associated with, any individual visitor or IP address.

Link to headingFurther reading: Optimizing Core Web Vitals

Now that you have an overview of what Core Web Vitals are, how to measure them, and how they impact your application, you may be wondering, “How do I optimize each metric?”

We've written deep dive into the topic, specific to JavaScript frameworks and Vercel tooling.

We also recommend Google’s technical guides on optimizing individual metrics: Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP).

Link to headingTakeaways

• Improving Core Web Vitals is the most transparent ranking factor in Google Search, since you have direct access to the underlying data used by Google to rank your site.

• Only Core Web Vitals count for Google’s search ranking. Your Lighthouse score is ignored.

• Google’s data uses a 28-day sliding window. For improving your site speed at a

  higher iteration velocity, Vercel’s Speed Insights gets you real-time, easily filterable access to your Core Web Vitals.