In order to help clarify the landscape of webpage metrics and bring light to the myriad unknowns and concerns of how Google actually ranks a page’s performance, we have outlined an FAQ on Google’s page experience.
These include some of the most commonly asked questions about Core Web Vitals that Google has received.
So let’s jump into the unknown and clear up the metric landscape.
Question
What are Google’s Core Web Vitals?
Answer
There are three Core Web Vitals: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift.
Largest Contentful Paint measures how fast a user can see all of the content. First Input Delay measures the responsiveness of a website, such as the ability for a user to enter data in a form or clicking a button. Cumulative Layout Shift measures how much elements of a page move around the screen while it loads.
Question
What is the benefit of scoring good results across all three Core Web Vitals?
Answer
Websites use Core Web Vitals as a benchmark for how good their user experience is across its pages. But each page has its own performance score, so one website may be a collection of different Core Web Vitals scores.
The benefit of good scores of Core Web Vitals beyond providing users with a better digital experience is that Google will reward that page in its search engine rankings.
Question
Do pages built on AMP meet the recommended benchmarks?
Answer
In short, it is likely that AMP pages would meet the Core Web Vitals benchmarks. Because AMPs are optimized for mobile and help to load pages faster, its design is closely aligned with those of Core Web Vitals.
There are things, however, that are outside of the control of AMPs that can influence pages not meeting the Core Web Vitals benchmarks. These include slow server response times as well as unoptimized pages.
Question
Can a non-AMP page meet the Core Web Vitals benchmark scores?
Answer
Of course! Using AMP is not a prerequisite for good or even strong Core Web Vitals scores. However, the advantage of AMP is that it uses best practices in web development, which are baked into the framework, so that you don’t need to add extra effort.
Question
Does my site meet the benchmarks if it is a Progressive Web App?
Answer
No, not necessarily. It all depends on the implementation of the Progressive Web App as well as how users interact with the page. Think of Core Web Vitals as a way to complement a Progressive Web App.
Question
Does my site meet the benchmarks if it is a Single Page Application?
Answer
Because Core Web Vitals measure the user experience on a particular page, they don’t take into account the architecture nor the technology that are involved in creating a particular page’s experience. Layout shifts, content jumps, and input delays are equally important to a Single Page Application.
Question
Why is my page’s scores for Core Web Vitals low despite it being mobile-friendly?
Answer
Core Web Vitals is only one aspect (Ok well technically three) of Google’s page experience metrics. There are other metrics at play, such as mobile-friendliness, HTTPS, and non-intrusive interstitials. So despite a page being mobile-friendly, there are five other metrics that are influencing a page’s overall experience.
Question
How can a page’s Core Web Vitals scores be improved?
Answer
Google has plenty of space and material for people to analyze their website’s current performance and ways in which to improve them – for example the website web.dev. Yet keep in mind that in order to improve a website’s metrics a knowledge of web development is necessary.
PS: ArganoUV is one of the world’s leading Core Web Vitals consultancies. Contact us to see how we can work together.
