Google published an FAQ on Core Web Vitals and the upcoming Google Page Experience update, which will be released in May 2021. According to Google's Cheney Tsai, the company has compiled some of the most frequently asked questions about Core Web Vitals and Page Experience. This was not published as a blog post or help document, but on the Google Webmaster Help forums.
Here is this list:
Q: What are the metrics? Why are they relevant to users?
A: User-centric metrics are an important tool in understanding, measuring, and improving the user experience of your website. Largest content color measures how quickly users see content. First entry delay measures how quickly a site responds to user input such as tapping a button or entering data on a form. Cumulative layout shift measures how often elements of the page move while the user tries to read or interact with it.
Q: Does Google recommend that all of my pages meet these thresholds? What's the advantage?
A: We recommend that websites use these three thresholds as a guide for the best user experience on all pages. The thresholds for the most important web vitals are rated at the page level. You may find that some pages are above and others are below these thresholds. The immediate benefit will be a better experience for users who visit your website. In the long term, however, we believe that working on a common set of metrics and user experience thresholds across all websites is critical to maintaining a healthy web ecosystem.
Q: If I created AMP pages, do they meet the recommended thresholds?
A: There is a high chance that AMP pages will hit the thresholds. AMP is all about delivering high quality user experiences. The original design goals are closely aligned with what Core Web Vitals measure today. This means that websites built with AMP are likely to easily meet the Web Vitals thresholds. In addition, the evergreen version of AMP enables website owners to achieve these performance improvements without changing their code base or investing in additional resources. It's important to note that there are things that are outside of AMP's control that can cause pages to fail to meet the thresholds, such as: B. Slow server response times and unoptimized images. Find out more here.
Q: Can a site meet the recommended thresholds without using AMP?
A: Yes. The instructions on web.dev/vitals tell you how to optimize your performance compared to Core Web Vitals. The advantage of using AMP is that you can incorporate these web development best practices into the framework without any additional effort.
Q: If my website is a Progressive Web App, does it meet the recommended thresholds?
A: Not necessarily, as it still depends on how the Progressive Web App is implemented and how real users experience the site. Core Web Vitals complement the dispatch of a good PWA. It is important that every site, PWA or not, focus on loading experience, interactivity, and layout stability. We recommend that all PWAs follow Core Web Vitals guidelines.
Q: Can a site meet the recommended thresholds if it is a single page application?
A: Core Web Vitals measure the end-user experience of a given webpage and do not consider the technologies and architectures required to deliver that experience. Layout shifts, input delays, and content colors are just as relevant for a single page application as they are for other architectures. Different architectures can lead to different points of friction in order to achieve the threshold values. Regardless of which architecture you choose, the observed user experience matters.
Q: My website is cell phone rated, but my Core Web Vitals score for cell phones is low. How is that possible?
A: The Page Experience signal measures how users perceive the experience of interacting with a web page. Core Web Vitals is one aspect of this alongside mobile friendliness. These should not overlap, but rather be additive in order to obtain a holistic picture of the side experience.
Q: How do I improve my LCP / CLS / FID score?
A: For recommendations on how to improve your Core Web Vitals metrics, see web.dev/fast/. Improving the metrics for your website requires a knowledge of web development. If you're not a technical user, our search console help has some suggestions. However, you should contact a professional.
Q: Why are there differences in scores between mobile and desktop?
A: Currently, using page experience as a ranking signal applies to mobile search only. However, when you measure Core Web Vitals with the RUM tool of your choice, you may find that the results are different between Mobile Web and Desktop Web. While the technology used to create the site may be similar, real users of the two versions have different limitations such as device, viewport size, network connectivity, and more.
Q: Can sessions that do not report an FID be considered "bounce" sessions?
A: No, FID excludes scrolling, and there are legitimate no-scrolling sessions. Bounce rate and abandonment rate can be defined as part of the analytics suite of your choice and are not taken into account when designing CWV metrics.
Q: How does Core Web Vitals consider websites whose user base is high volume NBU traffic or other users with poor internet connectivity?
A: Core Web Vitals is designed to measure the quality of the user experience on a website. The user population of each site is different, and some sites, not limited to a specific region, may have significant numbers of users who may be using older devices, slower networks, and so on. In such cases, websites should adjust the content to ensure that these users continue to have a great user experience and, ideally, continue to meet the recommended thresholds for Core Web Vitals.
Q: Do Core Web Vitals Affect Ranking?
Starting in May 2021, key web vitals will be included in page experience signals along with existing search signals including ease of use, safe surfing, HTTPS security and intrusive interstitial guidelines. For more information, see our Search Central blog post.
Q: How does Google determine which pages are affected by the evaluation of the page experience and usage as a ranking signal?
A: Page experience is just one of many signals used to rank pages. Note that the intent of the search query is still a very strong signal. Therefore, a page with below average page experience can still rank high if it has great, relevant content.
Q: Is there a difference between desktop and mobile ranking?
A: Currently, using page experience as a ranking signal applies to mobile search only.
Q: What can website owners expect from their traffic if they fail to meet Core Web Vitals' performance metrics?
A: It is difficult to make a general prediction. We may need to share more in the future when we officially announce the changes go into effect. Note that the content itself and its correspondence with the type of information a user is looking for also remains a very powerful signal.
Q: What information does Search Console provide about Core Web Vitals? What do these errors mean?
A: Search Console released the Core Web Vitals Report, based on Chrome UX Report data, to help website owners identify potential user experience issues. This is to ensure that the Core Web Vitals report matches the status of each Core Web Vitals on their site and provides website owners with insight into the status of each Core Web Vitals. For more information about what various errors mean and how to fix them, see Help.
Q: My side is fast. Why are warnings displayed on the Search Console Core Web Vitals report?
A: Different devices, network connections, geography, and other factors can all contribute to how a page loads and is perceived by a particular user. While some users may observe a good experience under certain conditions, it may not be indicative of the experience of other users. Core Web Vitals look at the total number of user visits and their thresholds are rated at the 75th percentile of the total number of users. The SC CWV report helps in reporting this data.
Remember, Core Web Vitals is more than just speed, depending on how you rate "Fast". For example, Cumulative Layout Shift describes user annoyances such as moving content. In addition, you can also use synthetic testing tools that try to emulate a user. However, this representation may differ from your actual users.
Q: When I look at Lighthouse, I don't see any errors. Why do I see errors in the Search Console report?
The Search Console Core Web Vitals report shows the performance of your pages based on the real world usage data from the CrUX report (sometimes called "field data"). Lighthouse, on the other hand, displays data based on so-called laboratory data. Laboratory data is useful for debugging performance problems while developing a website because it is collected in a controlled environment. However, real bottlenecks may not be captured. You can use either report to improve the user experience. However, the information in each report is different.
Forum discussion in Google Webmaster Help.