{"id":761,"date":"2023-11-12T14:35:44","date_gmt":"2023-11-12T14:35:44","guid":{"rendered":"https:\/\/okonet.kinsta.cloud\/?p=761"},"modified":"2023-11-12T14:35:44","modified_gmt":"2023-11-12T14:35:44","slug":"core-web-vitals-what-they-are-and-why-its-vital","status":"publish","type":"post","link":"https:\/\/cool.co\/publisher-experiences-home\/2023\/11\/12\/core-web-vitals-what-they-are-and-why-its-vital\/","title":{"rendered":"Core Web Vitals: What They Are, And Why It\u2019s \u2018Vital\u2019"},"content":{"rendered":"
\n
\n

If you\u2019ve heard the term \u201cCore Web Vitals<\/a>\u201d thrown around online, your first thought was that it definitely sounded important \u2014 anything \u201ccore\u201d is usually pretty critical, and the term \u201cvitals\u201d pops up in day-to-day life mostly in TV hospital dramas \u2014 but the term, by itself, doesn\u2019t really get into the specifics of what it\u2019s talking about. To the uninitiated, it could mean any number of Important Internet Things, and if you were afraid to ask, we\u2019ve got the answers for you right here.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Simply put,\u00a0your Core Web Vitals (CWV) are performance metrics Google uses to measure your site\u2019s health<\/b>. It\u2019s a measure of how well your site functions and what sort of experience a user can expect, so that Google can factor that into\u00a0how highly they can recommend your page on the Search Engine Results Page<\/a>\u00a0(SERP).<\/p>\n<\/div>\n<\/div>\n

\n
\n

Things like how fast a page loads, how stable it is, and how it responds to user inputs all factor into Google\u2019s Core Web Vitals score. The better the score, the more comfortable Google feels vouching for you in search results. Google web crawlers automatically scan your site to collect this data, and since 2021, Core Web Vitals have been part of the Google search algorithm. If you want to play on Google\u2019s court \u2014 which, of course, we all do, given their current dominance over the industry \u2014 we have to play by their rules.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Your CWV score isn\u2019t just a component of search-engine results \u2014 it’s also a measure of\u00a0how your users will interact with your website<\/a>. Pages that load slowly will suffer from high bounce rates, as impatient users bail before the content you\u2019ve worked so hard on has a chance to load. Pages that don\u2019t respond quickly will be frustrating and sluggish to use. Plus, visually-unstable pages are frustrating to navigate, as anyone who has gone to click on something only for an ad to push everything half an inch to the left can attest. CWV also measure how mobile-friendly your site is, which is something to strive for even if Google weren\u2019t measuring it.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Basically, there\u2019s no reason not to check your vitals, and improve them any way you can.<\/p>\n<\/div>\n<\/div>\n

\n
\n

By The Numbers<\/h2>\n<\/div>\n<\/div>\n
\n
\n

There are three main components of your Core Web Vitals Score:<\/p>\n<\/div>\n<\/div>\n

\n
\n

\n

Largest Contentful Paint:<\/h3>\n

LCP measures\u00a0how long your site\u2019s content takes to load<\/a>\u00a0on the page, particularly the biggest components like your images, videos, and text. Like we said earlier, a slow loading time creates a poor user experience and increases bounce rate. Google recommends an LCP below 2.5 seconds.<\/p>\n

 <\/p>\n<\/div>\n<\/div>\n

\n
\n

\n

First Input Delay:<\/h3>\n

FID clocks\u00a0how long it takes for your page to respond when a user interacts with it for the first time<\/a>\u00a0\u2014 interactions like link clicks, JavaScript actions, and button taps. Much like LCP, a poor FID score makes for a poor user experience. Google\u2019s preference is an FID that comes in below 100 milliseconds.<\/p>\n

 <\/p>\n<\/div>\n<\/div>\n

\n
\n

\n

Cumulative Layout Shift:<\/h3>\n

It\u2019s happened to you: you\u2019ve gone to click or tap on something on a website, but at the last second, the page shifts and you end up clicking on the wrong thing. Or a picture pops in and moves the paragraph you were reading several inches further down. It\u2019s incredibly frustrating, and that\u2019s what CLS measures:\u00a0how long it takes for your pages layout to solidify while loading<\/a>\u00a0. Google wants a CLS score at or below 0.1.<\/p>\n

 <\/p>\n<\/div>\n<\/div>\n

\n
\n

\n

First Contentful Paint:<\/h3>\n

The FCP\u00a0measures how long it takes for anything at all to load on your page<\/a>. The longer a loading page sits on a white void, the more unsettling it is for users \u2014 so Google recommends an FCP of 1.8 seconds or less. While less important than the other three we just went over, you can see how something like that would affect the user experience<\/p>\n

 <\/p>\n<\/div>\n<\/div>\n

\n
\n

The first step to improving your CWV score is obviously finding out what your current score is. There are several ways to figure that out. Google\u2019s developer tools provide you several options for that, including:<\/p>\n<\/div>\n<\/div>\n

\n
\n