{"id":229,"date":"2026-07-11T21:55:02","date_gmt":"2026-07-11T12:55:02","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/core-web-vitals\/"},"modified":"2026-11-15T18:46:50","modified_gmt":"2026-11-15T09:46:50","slug":"core-web-vitals","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/core-web-vitals\/","title":{"rendered":"Core Web Vitals"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">The three metrics and their thresholds<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Core Web Vitals are metrics Google uses to quantify real users\u2019 page experience along three axes: loading, responsiveness, and stability. LCP covers loading performance, INP covers interaction responsiveness, and CLS covers visual stability. On March 12, 2024, INP officially replaced FID (First Input Delay), and FID was removed from Search Console the same day. <a class=\"jt-src jt-src--official\" href=\"https:\/\/web.dev\/blog\/inp-cwv-march-12\" target=\"_blank\" rel=\"noopener\">web.dev announcement<\/a><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Metric<\/th><th>What it measures<\/th><th>\u201cGood\u201d threshold<\/th><\/tr><\/thead><tbody><tr><td>LCP (Largest Contentful Paint)<\/td><td>Time to render the largest content on screen (usually the hero image or headline)<\/td><td>2.5 seconds or less<\/td><\/tr><tr><td>INP (Interaction to Next Paint)<\/td><td>Delay from a click, tap, or key press to the next screen update<\/td><td>200 ms or less<\/td><\/tr><tr><td>CLS (Cumulative Layout Shift)<\/td><td>How much the layout shifts unexpectedly during loading<\/td><td>0.1 or less<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The verdict is based on real-user data, not lab scores. web.dev advises that &#8220;a good threshold to measure is the 75th percentile of page loads, segmented across mobile and desktop devices.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/web.dev\/articles\/vitals\" target=\"_blank\" rel=\"noopener\">web.dev<\/a> In other words, at least 75% of visits must fall within the thresholds on all three metrics to be rated \u201cgood,\u201d and mobile and desktop are assessed separately.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Impact on search rankings: where official guidance and real-world data diverge<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">How much Core Web Vitals affect rankings is where Google\u2019s official documentation and industry measurements differ most. The bottom line: they are a ranking signal, but they don\u2019t beat content relevance.<\/p>\n\n\n\n<figure class=\"wp-block-table jt-verdict\"><table><tbody><tr><th>Google\u2019s official position<\/th><td>Page experience is a signal Google\u2019s ranking systems consider, but content relevance comes first, and page experience acts more like a tiebreaker between otherwise similar results. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/page-experience\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/td><\/tr><tr><th>Expert measurement results<\/th><td>In an Ahrefs study covering data on 5.2 million pages, the author said there was no way to draw conclusions about a correlation between Core Web Vitals and rankings, because the ranking update overlapped with other changes (2022). <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/core-web-vitals-study\/\" target=\"_blank\" rel=\"noopener\">Ahrefs (data)<\/a><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The gap exists because they measure different things. Google describes a policy (\u201cwe use it as a signal\u201d), while measurements observe that \u201cthe signal doesn\u2019t show up clearly in actual ranking changes.\u201d Google itself wrote in its page experience documentation that &#8220;trying to get a perfect score just for SEO reasons may not be the best use of your time.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/page-experience\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> In practice, rather than tuning these metrics alone and expecting a ranking jump, treating them as fundamentals within the bigger picture of <a href=\"\/en\/seo-glossary\/seo\/\">SEO<\/a> fits both positions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Benefits beyond rankings: speed and conversion rates<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Even if their ranking weight is small, the stronger reason to take these metrics seriously is conversion. The \u201cMilliseconds Make Millions\u201d study, commissioned by Google and conducted by Deloitte and 55, analyzed more than 30 million sessions across 37 brand sites in Europe and the US. A 0.1-second improvement in mobile speed increased retail conversion rates by 8.4% and retail order value by 9.2% (2020). <a class=\"jt-src jt-src--data\" href=\"https:\/\/web.dev\/case-studies\/milliseconds-make-millions\" target=\"_blank\" rel=\"noopener\">Deloitte (data)<\/a> Even at the same ranking, a slow site loses visitors after they arrive.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Lab data vs. field data: the score illusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The PageSpeed Insights screen is actually two reports. According to Google\u2019s documentation, the \u201cDiscover what your real users are experiencing\u201d section at the top is field data collected by CrUX (Chrome User Experience Report) over the previous 28 days, while the 0\u2013100 performance score below is lab data simulated by Lighthouse. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/speed\/docs\/insights\/v5\/about\" target=\"_blank\" rel=\"noopener\">PageSpeed docs<\/a> Because the measurement conditions differ, the two can disagree.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">INP in particular can\u2019t be fully captured by lab tests. web.dev explains that &#8220;some lab tools can&#8217;t report INP because they observe only page loading, without interactions.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/web.dev\/articles\/inp\" target=\"_blank\" rel=\"noopener\">web.dev<\/a> Check field-data pass rates for the whole site in the Core Web Vitals report in <a href=\"\/en\/seo-glossary\/google-search-console\/\">Google Search Console<\/a>; that data also comes from CrUX and is shown separately for mobile and desktop. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/9205520\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Practical checkpoints<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Each item below is based on web.dev\u2019s official optimization guide for that metric.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>LCP &#8211; web.dev explicitly says to &#8220;never lazy-load your LCP image,&#8221; and recommends setting <code>fetchpriority=\"high\"<\/code> on the image expected to be the LCP element and reducing render-blocking CSS\/JS. <a class=\"jt-src jt-src--official\" href=\"https:\/\/web.dev\/articles\/optimize-lcp\" target=\"_blank\" rel=\"noopener\">web.dev<\/a><\/li><li>CLS &#8211; web.dev recommends reserving space for images and videos with <code>width<\/code>\/<code>height<\/code> (or CSS <code>aspect-ratio<\/code>) and reserving space for late-loading ads and embeds with <code>min-height<\/code>. <a class=\"jt-src jt-src--official\" href=\"https:\/\/web.dev\/articles\/optimize-cls\" target=\"_blank\" rel=\"noopener\">web.dev<\/a><\/li><li>INP &#8211; web.dev advises you to &#8220;do as little work as possible in event callbacks,&#8221; breaking up long tasks and running only the logic needed for the next frame\u2019s visual update first. <a class=\"jt-src jt-src--official\" href=\"https:\/\/web.dev\/articles\/optimize-inp\" target=\"_blank\" rel=\"noopener\">web.dev<\/a><\/li><\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;!-- LCP image: declare size (CLS) + load with priority (LCP) - per web.dev --&gt;\n&lt;img src=\"hero.webp\" width=\"1200\" height=\"800\"\n     fetchpriority=\"high\" decoding=\"async\" alt=\"Main visual\"&gt;\n\n&lt;!-- Preload key web font: reduce layout shifts caused by font swapping --&gt;\n&lt;link rel=\"preload\" href=\"\/en\/fonts\/pretendard-sub.woff2\"\n      as=\"font\" type=\"font\/woff2\" crossorigin&gt;<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Common mistakes<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li>Treating a Lighthouse score as a \u201cpass\u201d &#8211; The verdict uses CrUX field data. That data reflects a 28-day collection window, so even after you ship improvements, the numbers move slowly. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/speed\/docs\/insights\/v5\/about\" target=\"_blank\" rel=\"noopener\">PageSpeed docs<\/a><\/li><li>An optimization plugin lazy-loading even the LCP image &#8211; web.dev states that lazy-loading the LCP image &#8220;always&#8221; adds an unnecessary resource load delay and hurts LCP. Always exclude above-the-fold images. <a class=\"jt-src jt-src--official\" href=\"https:\/\/web.dev\/articles\/optimize-lcp\" target=\"_blank\" rel=\"noopener\">web.dev<\/a><\/li><li>Measuring desktop only &#8211; Both web.dev and the Search Console documentation say mobile and desktop are assessed separately. Passing on one alone is not a full pass.<\/li><li>Confusing performance metrics with visibility problems &#8211; If a page doesn\u2019t appear in search at all, look for the cause in <a href=\"\/en\/seo-glossary\/crawling-indexing\/\">crawling and indexing<\/a>.<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">References<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/page-experience\" target=\"_blank\" rel=\"noopener\">Understanding page experience in Google Search results &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/9205520\" target=\"_blank\" rel=\"noopener\">Core Web Vitals report &#8211; Search Console Help<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/speed\/docs\/insights\/v5\/about\" target=\"_blank\" rel=\"noopener\">About PageSpeed Insights &#8211; Google for Developers<\/a><\/li><li><a href=\"https:\/\/web.dev\/articles\/vitals\" target=\"_blank\" rel=\"noopener\">Web Vitals &#8211; web.dev<\/a><\/li><li><a href=\"https:\/\/web.dev\/blog\/inp-cwv-march-12\" target=\"_blank\" rel=\"noopener\">Interaction to Next Paint becomes a Core Web Vital on March 12 &#8211; web.dev<\/a><\/li><li><a href=\"https:\/\/web.dev\/articles\/inp\" target=\"_blank\" rel=\"noopener\">Interaction to Next Paint (INP) &#8211; web.dev<\/a><\/li><li><a href=\"https:\/\/web.dev\/articles\/optimize-lcp\" target=\"_blank\" rel=\"noopener\">Optimize Largest Contentful Paint &#8211; web.dev<\/a><\/li><li><a href=\"https:\/\/web.dev\/articles\/optimize-cls\" target=\"_blank\" rel=\"noopener\">Optimize Cumulative Layout Shift &#8211; web.dev<\/a><\/li><li><a href=\"https:\/\/web.dev\/articles\/optimize-inp\" target=\"_blank\" rel=\"noopener\">Optimize Interaction to Next Paint &#8211; web.dev<\/a><\/li><li><a href=\"https:\/\/web.dev\/case-studies\/milliseconds-make-millions\" target=\"_blank\" rel=\"noopener\">Milliseconds make millions &#8211; web.dev<\/a><\/li><li><a href=\"https:\/\/ahrefs.com\/blog\/core-web-vitals-study\/\" target=\"_blank\" rel=\"noopener\">Core Web Vitals Data Study &#8211; Ahrefs<\/a><\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Core Web Vitals are three key performance metrics (LCP, INP, CLS) Google defined to measure real users\u2019 page experience. They quantify loading speed, interaction responsiveness, and visual stability, and are page experience signals used by Google\u2019s ranking systems. The verdict is based not on lab test scores but on the 75th percentile of real-user data (CrUX).<\/p>\n","protected":false},"template":"","glossary_categories":[21],"class_list":["post-229","seo_glossary","type-seo_glossary","status-publish","hentry","glossary_categories-technical"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/229","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/seo_glossary"}],"version-history":[{"count":1,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/229\/revisions"}],"predecessor-version":[{"id":2314,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/229\/revisions\/2314"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=229"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}