Page Experience report

The Page Experience report provides a summary of the user experience of visitors to your site. Google evaluates page experience metrics for individual URLs on your site and will use them as a ranking signal for a URL in Google Search results. Learn more about page experience on Google.

Open Page Experience Report

About Page Experience

Page Experience is evaluated per-URL. The assessment, and the report, were developed to help sites create pages that provide a better user experience for their visitors.

Read our FAQs about page experience.

Page experience in Google Search is evaluated using the following criteria:

  • Core Web Vitals
    Core Web Vitals tests the speed, responsiveness, and stability of the page loading experience for users. The Core Web Vitals report provides a rating of Good, Needs improvement, or Poor to each page. A page must have a Core Web Vitals rating of Good in both CLS and LCP, and Good (or not enough data) in FID in order to qualify for Good page experience status. Note that it takes a few days to import data from the Core Web Vitals report into the Page Experience report, and so the rating for a URL in the Page Experience report can lag slightly behind the URL's rating Core Web Vitals report. URLs without Core Web Vitals cannot appear in the Page Experience report. Open the Core Web Vitals report.
  • Mobile usability
    A mobile URL must have no mobile usability errors in order to qualify for Good status on mobile devices in the Page Experience report. URLs without mobile usability data are considered to be Good. Note that mobile usability is reported only for URLs listed as mobile URLs in the report. Open the Mobile Usability report.
  • HTTPS usage
    A page must be served over HTTPS to be eligible for Good page experience status in Google Search. The Page Experience report doesn't have URL-level HTTPS data for your site, only the overall HTTP/HTTPS ratio for your site. If your site has too high a ratio of HTTP URLs, you will see warning banner on your site, and the HTTPS section will show Failing.
    We don't yet have a report that shows exact numbers of HTTP vs HTTPS on your site, but here are tips on how to locate your HTTP pages, and here's a guide describing why HTTPS is important, and how to implement it on your site. The important thing to remember is that if a URL in Google Search results is HTTPS, then it will be considered as passing the HTTPS criterion.

Report coverage

In order for a URL to be counted in the report data:

  • The URL must have data in the Core Web Vitals report. (Exception: A URL without Core Web Vitals data might appear in Page Experience if the URL group for that URL appears in Core Web Vitals).

Note that URLs counted by the Page Experience are the URLs that appeared in Google Search. Core Web Vitals also reports on actual URLs, not canonical URLs. However, the Mobile Usability report assigns all data to a page's canonical URL.

About the chart

The chart shows the following data:

  • Good URLs: Percentage of URLs with Good status on the last date measured in the chart, where Good means that a URL has Good status in the Core Web Vitals report. Good status for mobile means that the URL also has no mobile usability issues (or no mobile usability data) in the Mobile Usability report. HTTPS status is not a factor in this count. See more about status reporting.
  • Total impressions of good URLs: The number of impressions generated by good URLs over the time period shown by the chart. Latest data for impressions may lag the daily good URL count because of differing data processing schedules.
  • Chart daily values: The percentage of URLs considered good on each given day. URLs considered "good" follow the same criteria described above for Good URLs.

⚠︎Important qualifications about the data: 

  • There is a delay in importing data form the Mobile Usability report and Core Web Vitals report into the Page Experience report. Therefore, the evaluation of a specific URL in Page Experience can lag slightly behind that URL's evaluations in those other source reports.
  • The Good percentage shown in this report doesn't include the HTTPS status of URLs on your site. Google Search does take into account the HTTPS status of any URL shown in Search results.
Data time lag: The source data for the Page Experience report is based on the evaluation of data from several other sources and reports: Core Web Vitals report, Mobile Usability report, and so on. These child evaluations occur on different time schedules, so the live, current state of any given URL might be different than that shown on the report. Because of this, you should look at trends in your data (getting better or not?) and the general evaluation (most of your pages are good or not) rather than using this report as an exact, real-time evaluation of your site status.

Missing data

If you see Your site doesn't have enough usage data instead of the Page Experience report, it means either that your property is new in Search Console, or that there is not enough data available in the CrUX report to provide meaningful information for the chosen device type (desktop or mobile). The CrUX database gathers information about URLs whether or not the URL is part of a Search Console property, but it can take a few days after a property is created to analyze and post any existing data from the CrUX database.

If you see Not enough data collected instead of a chart, it means that you do not have sufficient data for any URL on your site in the Core Web Vitals report.

If you see Not enough recent usage data for Core Web Vitals in the report, then you don't have enough recent CrUX data to generate Core Web Vitals information. CrUX data is generated by user visits. Nothing for you to do here, just wait until enough user traffic accrues to generate this report.

If you see Not enough data for HTTPS, then Search Console can't find any information about HTTPS URLs on your site. Nothing for you to do here; just let Google continue to crawl your site.

If you see a banner saying Not enough recent site traffic for a complete evaluation, it means that there is either a gap in recent HTTPS or Core Web Vitals data, and so the current page experience values can't be calculated.

Status of a specific URL

The Page Experience report checks a subset of the page experience criteria applied by Google Search results.

Also, HTTPS is evaluated at the site level in this report:

  • HTTPS is shown in this report at the site level, but evaluated in Google Search at the URL level. This means an HTTPS URL in Search will always pass the HTTPS criteria, and an HTTP URL in Search will always fail the HTTPS criteria.
  • Core Web Vitals and mobile usability are evaluated at the page level on Search, and also in this report.

Here is a summary of the differences of how a URL is evaluated in the Page Experience report compared to how it is evaluated in Search:

  Page Experience Report Google Search
Core Web Vitals At the specific URL level (with some lag in results) At the specific URL level  (with no lag in results)
Mobile usability At the URL level At the URL level
HTTPS usage At the site level At the URL level


Here are the criteria for a URL to rate as good in page experience status in Google Search:

Good Failed

All of the following are true:

  • The URL has Good status in the Core Web Vitals  in both CLS and LCP, and Good (or not enough data) in FID
  • On mobile devices: The URL has no mobile usability issues according to the Mobile Usability report
  • The URL is served over HTTPS

Good status will be used as a ranking signal for a URL in Google Search results on desktop or mobile devices.

At least one of the following is true:

  • The URL has Poor or Needs Improvement status, or does not appear, in the Core Web Vitals report
  • On mobile devices: The URL has one or more mobile usability issues according to the Mobile Usability report, or the URL doesn't appear in the Mobile Usability report but appears in the Page Experience report.
  • The URL is served using HTTP, not HTTPS.

Find your HTTP pages

Here are two methods to help get a general idea of which URLs on your site are HTTP vs HTTPS:

If you think you have an equivalent HTTPS version for an HTTP URL that's appearing in Search, inspect the HTTPS URL in the Google Index to see if it's appearing in Search, and if not, why not.

Was this helpful?
How can we improve it?
Clear search
Close search
Google apps
Main menu
Search Help Center