Google Chrome Team Shares Tips For Optimizing Core Web Vitals

Google Chrome Team Shares Tips For Optimizing Core Web Vitals

Google provides updated Core Web Vitals suggestions that most website owners and developers can implement. 

To assist you in choosing what to prioritize when you have limited time, Google is offering an updated set of recommendations for optimizing Core Web Vitals. 

Three measures called Core Web Vitals assess loading speed, interaction, and visual stability. 

Google utilizes these indicators to rank websites in its search results because it believes they are crucial to delivering a great user experience. 

Google has made multiple recommendations throughout the years to raise Core Web Vitals ratings. 

Google understands it’s impractical to expect everyone to execute all of its recommendations, even though they are all worthwhile.

Finding what will have the biggest impact can be difficult if you don’t have much experience with website performance optimization. 

If you only have a short amount of time to devote to Core Web Vitals, you might not know where to begin. 

Google’s updated list of suggestions enters the picture here. 

Google claims in a blog post that the Chrome team spent a year attempting to determine the most crucial guidance it can provide on Core Web Vitals. 

The group created a list of suggestions that are practical for the majority of developers, appropriate for the majority of websites, and have a substantial real-world impact.

Here are some tips from Google chrome Team:

Optimizing the Largest Contentful Paint (LCP)

The time it takes for a page’s main content to become visible to users is measured by the Largest Contentful Paint (LCP) metric. 

Only about half of all websites, according to Google, match the suggested LCP criterion. 

The following are Google’s top suggestions for enhancing LCP.

Make Sure The HTML Source Contains The LCP Resource Clearly 

72% of mobile webpages, according to the 2022 Web Almanac by HTTP Archive, include an image as the primary content. 

Websites must make sure that images load rapidly to increase LCP. 

If a page waits for CSS or JavaScript files to fully download, parse, and execute before the picture can start loading, it can be hard to exceed Google’s LCP requirement. 

Generally speaking, the URL for an image that is the LCP element must always be accessible from the HTML source.

Ascertain the priority of the LCP resource

Google advises prioritizing the LCP resource and not lagging behind other less crucial resources in addition to including it in the HTML code. 

Even if you have used the conventional img> tag to include your LCP image in the HTML source, it may still take longer for your image resource to load if there are numerous script> elements in the head> portion of your webpage before the img> tag. 

It would be great if you avoided taking any measures that could make the LCP image less important, like adding the loading=”lazy” attribute. 

Use caution while utilizing any image optimization solutions that apply lazy loading automatically to all images.

Reduce Time To First Bite by Using A Content Delivery Network (CDN) (TTFB

Before loading any more resources, a browser must first get the first byte of the response for the original HTML content. 

Time to First Byte (TTFB), a measurement of this process’s speed, indicates when subsequent processes can start. 

Use caching for commonly requested content and offer your content from a location close to your users to reduce TTFB. 

According to Google, using a content delivery network is the best method to accomplish both goals (CDN).

Cumulative Layout Shift Optimization (CLS) 

A statistic called Cumulative Layout Shift (CLS) is used to assess how stable a website’s visual layout is. Google estimates that about 25% of websites do not adhere to the suggested criteria for this statistic. 

The following are Google’s top suggestions for enhancing CLS. 


Configure Explicit Sizes For On Page Content 

When the content on a website moves after it has finished loading, this is known as a layout shift. 

To avoid this, it’s crucial to reserve space in advance as much as feasible. 

Unsized images are a frequent reason for layout changes, but they may be fixed by explicitly setting the width and height attributes or corresponding CSS properties. 

Not all elements can alter the layout of web pages, including images. 

Make Sure Pages Are Bfcache-Eligible 

The back/forward cache, or cache for short, function in browsers enables instantaneous page loading from earlier or later in the browser history using a memory snapshot. 

By preventing layout changes during page loading, this feature can dramatically boost performance. 

Google advises utilizing Chrome DevTools to determine whether your pages qualify for the cache and address any issues that may prevent them. 

Avoid transitions and animations 

The animation of website elements, such as cookie banners or other notification banners that glide in from the top or bottom, is a common reason for layout changes. 

These animations may push other information aside, which could affect CLS. 

The reduction of first input delay (FID) 

A website’s first input delay (FID) is a metric that gauges how quickly it reacts to user input. 

Although the majority of websites do well in this area, Google thinks there is still potential for development. 

The guidelines given below apply to both FID and Google’s new statistic, Interaction to Next Paint (INP), which may replace FID. 

Avoid or divide up lengthy tasks 

Any discrete task the browser completes, such as rendering, layout, parsing, and building and running scripts, is referred to as a task. 

Tasks that take more than 50 milliseconds to complete block the main thread and prevent the browser from responding to user inputs promptly. 

It’s helpful to divide lengthy jobs into smaller ones to prevent this.

AVOID USING Unnecessary Java Script 

The responsiveness of a website that uses a lot of JavaScript may suffer as a result of processes fighting for the attention of the main thread. 

Use the coverage tool in Chrome DevTools to find and delete unused code from the resources on your website. 

The website will take less time to parse and compile code if the size of the resources needed during loading is reduced, which would improve user experience. 

Don’t use big rendering updates 

Other factors besides JavaScript might affect how responsive a website is. The process of rendering might be expensive and hinder a website’s ability to react to user input. 

The complexity of optimizing the rendering process varies on the particular objective.

According to Google, do the following: 

RequestAnimationFrame() should not be used for any non-visual tasks. 

A modest DOM size is preferred. 

CSS confinement is used. 


An essential measure for delivering a great user experience and ranking in Google search results is Core Web Vitals. 

Although it would be a good idea to apply every one of Google’s suggestions, this concise list is practical, applicable to the majority of websites, and has the potential to make a significant difference. 

Making sites eligible for cache, leveraging a CDN to reduce TTFB, specifying specified sizes for on-page content to enhance CLS, reducing superfluous JavaScript, and avoiding animations and transitions for FID are a few examples of what is covered in this. 

You may maximize the utilization of your website and make better use of your time by adhering to these suggestions.

READ ALSO: 12 Types Of Passive Income That Aren’t Taxable

One thought on “Google Chrome Team Shares Tips For Optimizing Core Web Vitals

Leave a Reply

Your email address will not be published. Required fields are marked *