YouTube stopped being a place people visit just to kill time a while ago. It's the second-largest search engine on the internet, right behind Google itself. If you're putting out content there and simply hoping the algorithm notices, that approach runs out of steam fast.
What actually moves the needle is YouTube SEO — a deliberate set of practices that help your videos surface in search, get pulled into recommendations, and earn real visibility over time. This guide breaks down exactly what that means in practice and how to apply it step by step, whether you're starting from zero or trying to revive a channel that's gone quiet.
Why Core Web Vitals Still Matter
They are a confirmed ranking signal, but a light one. A fast page does not outrank a more relevant slow page, and treating Core Web Vitals as a ranking lever usually disappoints.
The commercial case is stronger than the ranking case. Conversion rates fall measurably with each additional second of load time, and mobile users on poor connections abandon before the page renders.
They also affect crawling. A slow server limits how much Googlebot will fetch, which on a large site becomes an indexing problem rather than a speed problem.
Largest Contentful Paint
LCP measures how long the largest visible element takes to render — usually the hero image or the main heading block. It approximates when the page becomes useful.
Good is 2.5 seconds or less at the 75th percentile of real visits. Above 4 seconds is poor.
The most common causes are an unoptimised hero image, render-blocking CSS and JavaScript in the head, and slow server response. The most common self-inflicted cause is lazy loading the hero image, which directly delays the exact element being measured.
Interaction to Next Paint
INP replaced First Input Delay as the responsiveness metric. It measures the delay between a user interacting and the page visibly responding, across the whole visit rather than just the first interaction.
Good is 200 milliseconds or less. Above 500 is poor.
It is almost always a JavaScript problem — long tasks blocking the main thread, heavy event handlers, or third-party scripts doing work while the user is trying to interact. Third-party tags are frequently the single largest contributor.
Cumulative Layout Shift
CLS measures unexpected movement of content during loading. It is the metric behind the experience of reaching for a button and having it jump away.
Good is 0.1 or less. Above 0.25 is poor.
Causes are predictable and fixable: images and iframes without width and height attributes, ads or embeds injected without reserved space, and web fonts that reflow text when they load. Setting explicit dimensions solves most of it.
Lab Data and Field Data Are Different
Lighthouse gives you lab data — a simulated load under controlled conditions. It is excellent for diagnosis because it is repeatable.
Google ranks on field data, collected from real Chrome users. That is what appears in the Core Web Vitals report in Search Console, and it is what actually counts.
Chasing a perfect Lighthouse score while field data stays poor is common and pointless. Diagnose in the lab, judge in the field.
What Usually Causes Poor Scores
Images. Almost always the largest contributor to page weight, and usually the LCP element.
Third-party scripts. Tag managers, chat widgets, analytics, heatmaps and advertising tags accumulate, and each one costs main-thread time.
Render-blocking resources in the head that delay first paint.
Slow server response. If time to first byte is 1.5 seconds, no front-end optimisation rescues the page — every other metric starts after that.
Where to Spend Your Effort
Start with the field data in Search Console rather than a lab score, and start with the pages that receive the most traffic rather than the worst scores.
Fix images first: correct format, correct dimensions, explicit width and height, preload the hero, lazy load everything below the fold.
Then audit third-party scripts honestly. Most sites carry tags for tools nobody uses any more, and removing them is the cheapest performance win available.
Then server response. Caching and a CDN usually deliver the largest improvement for the least work.
Frequently Asked Questions
Yes, but a light one. Their effect on conversion and crawl efficiency is usually larger than their effect on ranking position.
2.5 seconds or less at the 75th percentile of real user visits. Above 4 seconds is poor. Never lazy load the LCP element, as that directly delays the metric.
Almost always JavaScript — long tasks blocking the main thread, heavy event handlers, and third-party scripts working while the user tries to interact.
Diagnose with Lighthouse lab data because it is repeatable, but judge by the field data in Search Console, since that is collected from real users and is what Google actually uses.