{"id":17342,"date":"2023-01-12T19:32:26","date_gmt":"2023-01-12T19:32:26","guid":{"rendered":"https:\/\/www.searchenginejournal.com\/google-chrome-team-shares-tips-for-optimizing-core-web-vitals\/476379\/"},"modified":"2023-01-12T19:32:26","modified_gmt":"2023-01-12T19:32:26","slug":"google-chrome-team-shares-tips-for-optimizing-core-web-vitals-via-sejournal-mattgsouthern","status":"publish","type":"post","link":"https:\/\/marketingnewsbox.com\/?p=17342","title":{"rendered":"Google Chrome Team Shares Tips For Optimizing Core Web Vitals via @sejournal, @MattGSouthern"},"content":{"rendered":"
<\/div>\n

Google is sharing an updated set of recommendations for optimizing Core Web Vitals to help you decide what to prioritize when time is limited.<\/p>\n

Core Web Vitals are three metrics measuring loading time, interactivity, and visual stability.<\/p>\n

Google considers these metrics essential to providing a positive experience and uses them to rank websites in its search results.<\/p>\n

Throughout the years, Google has provided numerous suggestions for improving Core Web Vitals scores.<\/p>\n

Although each of Google\u2019s recommendations is worth implementing, the company realizes it\u2019s unrealistic to expect anyone to do it all.<\/p>\n

If you don\u2019t have much experience with optimizing website performance, it can be challenging to figure out what will have the most significant impact.<\/p>\n

You may not know where to start with limited time to dedicate to improving Core Web Vitals. That\u2019s where Google\u2019s revised list of recommendations comes in.<\/p>\n

In a blog post, Google says the Chrome team spent a year trying to identify the most<\/strong> important advice it can give regarding Core Web Vitals.<\/p>\n

The team put together a list of recommendations that are realistic for most developers, applicable to most websites, and have a meaningful real-world impact.<\/p>\n

Here\u2019s what Google\u2019s Chrome team advises.<\/p>\n

Optimizing Largest Contentful Paint (LCP)<\/h2>\n

The Largest Contentful Paint (LCP) metric measures the time it takes for the primary content of a page to become visible to users.<\/p>\n

Google states that only about half of all websites meet the recommended LCP threshold.<\/p>\n

These are Google\u2019s top recommendations for improving LCP.<\/p>\n

Make Sure The LCP Resource Is Easily Found In The HTML Source<\/h3>\n

According to the 2022 Web Almanac by HTTP Archive, 72% of mobile webpages have an image as the main content. To improve LCP, websites must ensure images load quickly.<\/p>\n

It may be impossible to meet Google\u2019s LCP threshold if a page waits for CSS or JavaScript files to be fully downloaded, parsed, and processed before the image can start loading.<\/p>\n

As a general rule, if the LCP element is an image, the image\u2019s URL should always be discoverable from the HTML source.<\/p>\n

Make Sure The LCP Resource Is Prioritized<\/h3>\n

In addition to having the LCP resource in the HTML code, Google recommends prioritizing it and not delaying behind other less critical resources.<\/p>\n

Even if you have included your LCP image in the HTML source using a standard <img> tag, if there are several <script> tags in the <head> section of your webpage before the < img> tag, it can delay the loading time of your image resource.<\/p>\n

You should also avoid any actions that may lower the priority of the LCP image, such as adding the loading=\u201dlazy\u201d attribute.<\/p>\n

Be careful with using any image optimization tools that automatically apply lazy-loading to all images.<\/p>\n

Use A Content Delivery Network (CDN) To Reduce Time To First Bite (TTFB)<\/h3>\n

A browser must receive the first byte of the initial HTML document response before loading any additional resources.<\/p>\n

The measure of this time is called Time to First Byte (TTFB), and the faster this happens, the sooner other processes can begin.<\/p>\n

To minimize TTFB, serve your content from a location near your users and utilize caching for frequently requested content.<\/p>\n

The best way to do both things, Google says, is to use a content delivery network (CDN).<\/p>\n

Optimizing Cumulative Layout Shift (CLS)<\/h3>\n

Cumulative Layout Shift (CLS) is a metric used to evaluate how stable the visual layout of a website is. According to Google, around 25% of websites do not meet the recommended standard for this metric.<\/p>\n

These are Google\u2019s top recommendations for improving CLS.<\/p>\n

Set Explicit Sizes For On Page Content<\/h3>\n

Layout shifts can occur when content on a website changes position after it has finished loading. It is important to reserve space in advance as much as possible to prevent this from happening.<\/p>\n

One common cause of layout shifts is unsized images, which can be addressed by explicitly setting the width and height attributes or equivalent CSS properties.<\/p>\n

Images aren\u2019t the only factor that can cause layout shifts on webpages. Other content, such as third-party ads or embedded videos that load later can contribute to CLS.<\/p>\n

One way to address this issue is by using the aspect-ratio property in CSS. This property is relatively new and allows developers to set an aspect ratio for images and non-image elements.<\/p>\n

Providing this information allows the browser to automatically calculate the appropriate height when the width is based on the screen size, similar to how it does for images with defined dimensions.<\/p>\n

Ensure Pages Are Eligible For Bfcache<\/h3>\n

Browsers use a feature called the back\/forward cache, or bfcache for short, which allows pages to be loaded instantly from earlier or later in the browser history by using a memory snapshot.<\/p>\n

This feature can significantly improve performance by eliminating layout shifts during page load.<\/p>\n

Google recommends checking whether your pages are eligible for the bfcache using Chrome DevTools and working on any reasons why they are not.<\/p>\n

Avoid Animations\/Transitions<\/h3>\n

A common cause of layout shifts is the animation of elements on the website, such as cookie banners or other notification banners, that slide in from the top or bottom.<\/p>\n

These animations can push other content out of the way, impacting CLS. Even when they don\u2019t, animating them can still impact CLS.<\/p>\n

Google says pages that animate any CSS property that could affect layout are 15% less likely to have \u201cgood\u201d CLS.<\/p>\n

To mitigate this, it\u2019s best to avoid animating or transitioning any CSS property that requires the browser to update the layout unless it is in response to user input, such as a tap or key press.<\/p>\n

It is recommended to use the CSS transform property for transitions and animations when possible.<\/p>\n

Optimizing First Input Delay (FID)<\/h2>\n

First Input Delay (FID) is a metric that measures how quickly a website responds to user interactions.<\/p>\n

Although most websites currently perform well in this area, Google suggests that there is room for improvement.<\/p>\n

Google\u2019s new metric, Interaction to Next Paint (INP), is a potential replacement for FID, and the recommendations provided below are relevant to both FID and INP.<\/p>\n

Avoid Or Break Up Long Tasks<\/h3>\n

Tasks are any piece of discrete work that the browser performs, including rendering, layout, parsing, and compiling and executing scripts.<\/p>\n

When tasks take a long time, more than 50 milliseconds, they block the main thread and make it difficult for the browser to respond quickly to user inputs.<\/p>\n

To avoid this, it is helpful to break up long tasks into smaller ones by giving the main thread more opportunities to process critical user-visible work.<\/p>\n

This can be achieved by yielding to the main thread often so that rendering updates and other user interactions can occur more quickly.<\/p>\n

Avoid Unnecessary JavaScript<\/h3>\n

A website with a large amount of JavaScript can lead to tasks competing for the main thread\u2019s attention, which can negatively affect the website\u2019s responsiveness.<\/p>\n

To identify and remove unnecessary code from your website\u2019s resources, you can use the coverage tool in Chrome DevTools.<\/p>\n

By decreasing the size of the resources required during the loading process, the website will spend less time parsing and compiling code, resulting in a more seamless user experience.<\/p>\n

Avoid Large Rendering Updates<\/h3>\n

JavaScript isn\u2019t the only thing that can impact a website\u2019s responsiveness. Rendering can be costly and interfere with the website\u2019s ability to respond to user inputs.<\/p>\n

Optimizing rendering work can be complex and depends on the specific goal. However, there are some ways to ensure that rendering updates are manageable and don\u2019t turn into long tasks.<\/p>\n

Google recommends the following:<\/p>\n