The core network life cycle is a speed indicator, which is part of Google’s “page experience” signal and is used to measure user experience. These indicators use the most informative paint (LCP), through cumulative layout shift ((CLS), and with the “first input delay” (FID).
The page experience and accompanying Core Web Vital metrics will be officially used for page ranking in June 2021.
The easiest way to view your website metrics is to use “Core Network Vitality” report in Google Search Console. With this report, you can easily check whether your page is classified as a “bad URL”, a “URL that needs improvement” or a “good URL”.
In the report, you can find more detailed information about a specific issue and a list of affected pages.
Fact 1: These metrics are divided between desktop and mobile devices, but only mobile device signals are used to rank web pages. Google is switching to 100% mobile first index In March, it makes sense to use the mobile speed signal because the index page will also be based on the mobile version.
Fact 2: The data comes from the Chrome User Experience Report (CrUX), which records data from selected Chrome users. The indicator will be evaluated at the 75th percentile of users, so if you have 70% of users in the “good” category and 5% of users in the “needs to improve” category, your page is still judged as “need to improve”.
Fact three: The metrics will be evaluated for each page, but if there is not enough data, then John Mueller status The signals from various parts of the website or the entire website may be used.
Fact 4: By adding these new indicators, ampere It has been removed from the “Top Stories” feature on the phone and has been deleted. Since the new story will not actually contain data about speed metrics, it may use metrics from larger categories of pages or even entire domains.
Fact five: A single-page application cannot measure several metrics. FID with LCP, Through page conversion. We will discuss these in a minute.
Fact six: Metrics may change over time, and thresholds may also change. Over the years, Google has changed the metrics used to measure the speed of its tools and the threshold for measuring whether it has reached a fast state. This is likely to change again in the future. In fact, last year we did some work to improve the previous indicators, but we need to do some work again to improve the new indicators.
Just to set expectations, remember that there are more than 200 Ranking factor. Improving the core Web Vitals will not bring much improvement. It is not clear how much they will affect rankings, but this is unlikely to be a strong signal, especially considering that Google has used many on-page experience components to determine rankings.
Let’s understand each core web element in more detail.
These are the three current components of Core Web Vitals:
The largest satisfactory paint (LCP)-loading
LCP It is the largest single visible element loaded in the viewport.
The biggest element is usually a featured image or
Label, but it can be any of the following:
- Background image with url() function
- Text block
May be added in the future
How to see LCP
in PageSpeed insights, This LCP The elements will be specified in the “Diagnostics” section. For the test page, LCP It is a selected image from a blog post.
In Chrome DevTools, follow these steps:
- Performance>Check “Screenshot”
- Click “Start analysis and reload page”
- LCP On the timing diagram
- Click on the node; this is the element LCP
Follow us LCP The elements on this page and many other pages are selected images. We can preload the image or inline the entire image to make the image and HTML Code. Basically, we want to load the image faster than now.
Cumulative layout shift (CLS)—Visual stability
CLS Measure how the elements move or the stability of the page layout. It takes into account the size of the content and the distance it moves. One of the main problems with metrics is that even after the initial page load, it will continue to measure. Google is providing feedback on this specific metric, so we may see some changes to it in the future.
This can be annoying if you try to click on something that has changed on the page and end up clicking on something you didn’t want. It happens to me all the time. I clicked on one thing, and all of a sudden, I clicked on an ad, not even on the same website. As a user, this is frustrating.
Common cause CLS include:
- Picture without size
- No size ads, embeds and iframes
- Apply fonts or styles after loading
How to see CLS
Under “Diagnostics” in PageSpeed Insights, you will find a list of elements to be converted.
use WebPageTest. In the Filmstrip view, use the following options:
- Highlight layout shift
- Thumbnail size: huge
- Thumbnail interval: 0.1 seconds
Please note how our fonts can be re-styled between 5.1s-5.2s and change the layout when applying custom fonts.
You might want to try Layout shift GIF generator.
Smash magazine They also shared an interesting technique that outlines everything with a 3px solid red line and recorded a video to understand the changes that are taking place in the page layout.
For our test page, what we might want to do is to preload our custom font, delete the custom font completely (which would be suspicious), or use the default font for the initial page load, and then load it only on subsequent pages When loading our font. These need to be weighed in terms of brand, style, consistency, etc. We will have to decide the best way forward.
First input delay (FID)—Interactivity
FID The time from when the user interacts with your page to when the page can respond. You can also think of it as responsiveness. This does not include scrolling or zooming.
- Click on link or button
- Enter text in the blank field
- Select a drop-down menu
- Click a check box.
Trying to click on something on the page without any content can be frustrating.
Not all users will interact with the page, so they may not FID value. This is also the reason why the laboratory test tool does not interact with the page and is of no value. Use total block time (Technical barriers to trade) Instead.
the reason FID
When the task is running, the page cannot respond to user input. This is the perceived delay. The longer the task, the longer the delay experienced by the user. Interruptions between tasks are opportunities for the page to switch to user input tasks and respond to what they want to do.
The difference between laboratory data and field data is that field data is for real users, network conditions, equipment, caches, etc., and laboratory data is tested consistently based on the same conditions, and it is hoped that the test results are repeatable.
I like this report GSC Because you can see data for many pages at once, but the data is a bit delayed and the rolling average is 28 days, it may take some time for the changes to appear in the report.In Chrome 88, Google is Add Core Web Vitals in DevTools.
You can also find Scoring weight View the lighthouse at any time, and view historical changes.
You want to improve Core Web Vitals to make your users have a better experience.What impact they will have on themselves remains to be seen Search Engine OptimizationBut as I am My page speed article, They should help you record more data in your analysis, which “feels” like growth.
Work with your developers; they are the experts here. Page speed can be very complicated.If you are alone, you may need to rely on plugins or services to handle this issue, such as Wettable powder Rocket or NitroPack.