C — https://youtu.be | BeaverCheck Audit

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Missing signals may be hurting your search visibility.

Solid infrastructure — fast server responses across the board.

Several regulatory requirements are not yet met.

Good content signals with minor gaps.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Google Domains sites average 75

At average

Better than 4% of Google Domains sites See full Google Domains benchmark →

Google Font API sites average 73

At average

Better than 24% of Google Font API sites See full Google Font API benchmark →

Top Priorities (5)

'unsafe-inline' found in script source

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

1 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

1 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility

2 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality

2 image-in-link without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fyoutu.be)](https://beavercheck.com/results/effbbd49-5469-42fb-a7bd-c020c1f6f470)

HTML

<a href="https://beavercheck.com/results/effbbd49-5469-42fb-a7bd-c020c1f6f470"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fyoutu.be" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fyoutu.be

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

1 security gap detected — browsers may warn visitors about your site.

4 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 critical 7 warning

10 barrier(s) likely increasing bounce by ~38%.

Speed (2)

Page takes 8.3s to load

+12% bounce

Users abandon at ~3s — you're 5.8s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

High main-thread blocking time

+2% bounce

Page is non-interactive for 347ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Content (2)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

3 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€520 investment → €5,084/month returns + EUR 120,500,000 risk avoided

Payback period: < 1 month First-year ROI: +11632%

Investment

€520

6h · 5 findings

Monthly returns

€5,084 /mo

~€61,008 / year

Conversions recovered €5,084
Bandwidth savings €0.29

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
AVG EUR 20,000,000
EAA EUR 500,000

Payback period

0 12mo 24mo

€40 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€520

6.5 developer hours at €80/hr

Based on Belgium rates (€80/hr)

Quick wins

€40 1 fixes in ~30 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,004 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveAVGEAA

No privacy policy link detected
AVG: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
AVG: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
AVG: EUR 10,000 – EUR 20,000,000

+17 more

Bandwidth Waste

€0.29 /mo

3981.9 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~398 KB per page load
Saves €0.29/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

7.11 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

8.25 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

347 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

7.11 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

11.54 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021....	434.9 KiB	3.6 s
m.youtube.com/static/r/072389cc/fetch_polyfill.vflset/fetch_polyfill.js	2.6 KiB	463 ms
/s/_/ytmweb/_/ss/k=ytmweb.c3_base.Nl539GGld64.L.W.O/am=AA...	116.6 KiB	2.0 s
m.youtube.com/static/r/072389cc/scheduler.vflset/scheduler.js	3.1 KiB	463 ms

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
static.doubleclick.net/instream/ad_status.js	900.0 s	495 B

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.6 s

URL	Time Spent
youtu.be/	810 ms
www.youtube.com/?feature=youtu.be	767 ms
m.youtube.com/?feature=youtu.be	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 750 ms 175.0 KiB

URL	Transfer Size	Est Savings
/s/_/ytmweb/_/ss/k=ytmweb.c3_base.Nl539GGld64.L.W.O/am=AA...	116.6 KiB	115.0 KiB
m.youtube.com/s/player/b174a5bb/mobile-polymer-player-svg-ias-mweb.css	60.1 KiB	60.0 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 1.2 s 602.1 KiB

URL	Transfer Size	Est Savings
m.youtube.com/s/player/b174a5bb/player-plasma-es6-en_US.vflset/base.js	417.1 KiB	308.2 KiB
/s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021....	434.8 KiB	234.7 KiB
/s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021....	77.3 KiB	59.2 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021....	1.6 s	1.3 s	178 ms
Unattributable	853 ms	163 ms	0.0 ms
m.youtube.com/?feature=youtu.be	478 ms	130 ms	51 ms
m.youtube.com/s/player/b174a5bb/player-plasma-es6-en_US.vflset/base.js	257 ms	84 ms	168 ms
m.youtube.com/static/r/072389cc/scheduler.vflset/scheduler.js	151 ms	114 ms	1.4 ms
/s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021....	145 ms	92 ms	8.6 ms
/s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021....	127 ms	74 ms	42 ms
www.google.com/js/th/dTFo-KUuYlGOusziVr8u65jmcwADr_G5apr-mnW3AGs.js	97 ms	88 ms	7.9 ms
/s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021....	50 ms	44 ms	1.3 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	3.0 s
Other	893 ms
Script Parsing & Compilation	463 ms
Style & Layout	162 ms
Parse HTML & CSS	136 ms
Garbage Collection	107 ms
Rendering	20 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,296 KiB

●User Timing marks and measures 28 user timings

●Avoid long main-thread tasks 20 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 60 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 60 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search YouTube `ytm-search-bar-entry-point-view-model > div.search-bar-entry-point-buttons > div.search-bar-entry-point-button > span.search-bar-entry-point-text`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Elements with the `role=text` attribute do not have focusable descendents.

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○Links have a discernible name

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
m.youtube.com/s/player/b174a5bb/player-plasma-es6-en_US.vflset/base.js
/s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021....
www.google.com/js/th/dTFo-KUuYlGOusziVr8u65jmcwADr_G5apr-mnW3AGs.js

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Ensure CSP is effective against XSS attacks

○Mitigate clickjacking with XFO or CSP

○Mitigate DOM-based XSS with Trusted Types

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.22 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.96 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

774 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.028

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.05 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

4.95 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.437 source:map[column:483 line:93 type:source-location url:https://www.youtube.com/s/desktop/4329498d/jsbin/web-animations-next-lite.min.vflset/web-animations-next-lite.min.js urlProvider:network]] map[reflowTime:0.154 source:map[column:92 line:94 type:source-location url:https://www.youtube.com/s/desktop/4329498d/jsbin/web-animations-next-lite.min.vflset/web-animations-next-lite.min.js urlProvider:network]] map[reflowTime:0.322 source:map[column:11795 line:18 type:source-location url:https://www.youtube.com/?feature=youtu.be urlProvider:network]] map[reflowTime:16.566 source:map[column:23684 line:20 type:source-location url:https://www.youtube.com/?feature=youtu.be urlProvider:network]] map[reflowTime:59.705 source:map[type:text value:[unattributed]]] map[reflowTime:0.494 source:map[column:159 line:3120 type:source-location url:https://www.youtube.com/s/_/ytmainappweb/_/js/k=ytmainappweb.kevlar_base.en_US.IFuzsR39iKY.es5.O/am=AAAACAAAIAE/d=1/br=1/rs=AGKMywHnZQMy8qGo0LmnUsfARzmVoEeYhw/m=kevlar_base_module,kevlar_main_module urlProvider:network]] map[reflowTime:0.083 source:map[column:245 line:3120 type:source-location url:https://www.youtube.com/s/_/ytmainappweb/_/js/k=ytmainappweb.kevlar_base.en_US.IFuzsR39iKY.es5.O/am=AAAACAAAIAE/d=1/br=1/rs=AGKMywHnZQMy8qGo0LmnUsfARzmVoEeYhw/m=kevlar_base_module,kevlar_main_module urlProvider:network]] map[reflowTime:0.871 source:map[column:394 line:28226 type:source-location url:https://www.youtube.com/s/_/ytmainappweb/_/js/k=ytmainappweb.kevlar_base.en_US.IFuzsR39iKY.es5.O/am=AAAACAAAIAE/d=1/br=1/rs=AGKMywHnZQMy8qGo0LmnUsfARzmVoEeYhw/m=kevlar_base_module,kevlar_main_module urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:184.96 label:Time to first byte subpart:timeToFirstByte] map[duration:2461.266 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-H2

nodeLabel: Try searching to get started

path: 1,HTML,1,BODY,4,YTD-APP,8,DIV,4,YTD-PAGE-MANAGER,3,YTD-BROWSE,13,YTD-TWO-COLUMN-BROWSE-RESULTS-RENDERER,3,DIV,0,YTD-RICH-GRID-RENDERER,7,DIV,0,YTD-RICH-SECTION-RENDERER,3,DIV,0,YTD-FEED-NUDGE-RENDERER,3,DIV,1,DIV,1,DIV,0,H2

selector: div#dismissible > div#content-wrapper > div#text-container > h2#title-container

snippet: <h2 id="title-container" class="style-scope ytd-feed-nudge-renderer" aria-label="Try searching to get started">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/s/desktop/4329498d/jsbin/www-i18n-constants-en_US.vflset...	1.5 KiB
/s/desktop/4329498d/jsbin/intersection-observer.min.vflse...	2.0 KiB
www.youtube.com/s/desktop/4329498d/jsbin/scheduler.vflset/scheduler.js	3.1 KiB
/s/_/ytmainappweb/_/ss/k=ytmainappweb.kevlar_base.yAlYZ9F...	272.1 KiB	480 ms
/css2?family=Roboto:wght@300;400;500;700&family=YouTube+S...	15.4 KiB	277 ms
/s/desktop/4329498d/jsbin/webcomponents-sd.vflset/webcomp...	21.0 KiB
www.youtube.com/s/desktop/4329498d/jsbin/spf.vflset/spf.js	11.9 KiB
www.youtube.com/s/desktop/4329498d/jsbin/network.vflset/network.js	4.9 KiB
/s/desktop/4329498d/jsbin/custom-elements-es5-adapter.vfl...	809 B
/s/desktop/4329498d/jsbin/web-animations-next-lite.min.vf...	13.9 KiB
/s/desktop/4329498d/cssbin/www-main-desktop-watch-page-sk...	1.4 KiB
www.youtube.com/s/desktop/4329498d/cssbin/www-onepick.css	315 B
/s/desktop/4329498d/cssbin/www-main-desktop-home-page-ske...	1.3 KiB

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
www.gstatic.com/eureka/clank/146/cast_sender.js	86400.0 s	13.1 KiB
static.doubleclick.net/instream/ad_status.js	900.0 s	494 B

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 270 ms

URL	Time Spent
youtu.be/	270 ms
www.youtube.com/?feature=youtu.be	0.0 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 240 ms 334.5 KiB

URL	Transfer Size	Est Savings
/s/_/ytmainappweb/_/ss/k=ytmainappweb.kevlar_base.yAlYZ9F...	271.7 KiB	262.9 KiB
www.youtube.com/s/player/b174a5bb/www-player.css	56.6 KiB	56.6 KiB
/css2?family=Roboto:wght@300;400;500;700&family=YouTube+S...	14.9 KiB	14.9 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 920 ms 1.6 MiB

URL	Transfer Size	Est Savings
/s/_/ytmainappweb/_/js/k=ytmainappweb.kevlar_base.en_US.I...	1.8 MiB	1.1 MiB
www.youtube.com/s/player/b174a5bb/player_es6.vflset/en_US/base.js	639.4 KiB	476.2 KiB
www.youtube.com/s/player/b174a5bb/player_es6.vflset/en_US/remote.js	34.3 KiB	26.8 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/s/_/ytmainappweb/_/js/k=ytmainappweb.kevlar_base.en_US.I...	1.9 s	1.5 s	280 ms
/s/desktop/4329498d/jsbin/web-animations-next-lite.min.vf...	460 ms	372 ms	1.6 ms
Unattributable	445 ms	129 ms	0.0 ms
www.youtube.com/?feature=youtu.be	260 ms	25 ms	27 ms
www.youtube.com/s/player/b174a5bb/player_es6.vflset/en_US/base.js	171 ms	72 ms	75 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.5 s
Other	406 ms
Script Parsing & Compilation	402 ms
Style & Layout	196 ms
Parse HTML & CSS	177 ms
Garbage Collection	66 ms
Rendering	17 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/s/_/ytmainappweb/_/js/k=ytmainappweb.kevlar_base.en_US.I...	1.8 MiB
www.youtube.com/s/player/b174a5bb/player_es6.vflset/en_US/base.js	639.4 KiB
/s/_/ytmainappweb/_/ss/k=ytmainappweb.kevlar_base.yAlYZ9F...	272.1 KiB
www.youtube.com/?feature=youtu.be	76.5 KiB
www.youtube.com/s/player/b174a5bb/www-player.css	56.6 KiB
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	36.7 KiB
www.youtube.com/s/player/b174a5bb/player_es6.vflset/en_US/remote.js	34.3 KiB
/s/youtubesans/v32/Qw38ZQNGEDjaO2m6tqIqX5E-AVS5_rSejo46_P...	31.5 KiB
www.google.com/js/th/dTFo-KUuYlGOusziVr8u65jmcwADr_G5apr-mnW3AGs.js	23.2 KiB
www.youtube.com/s/player/b174a5bb/player_es6.vflset/en_US/offline.js	23.1 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Font display

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 33 user timings

●Avoid long main-thread tasks 6 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 70 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 70 ms

●Avoid large layout shifts 5 layout shifts found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-primary > a`
Press `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-primary > a`
Copyright `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-primary > a`
Contact us `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-primary > a`
Creators `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-primary > a`
Developers `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-primary > a`
Terms `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-secondary > a`
Privacy `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-secondary > a`
How YouTube works `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-secondary > a`
Test new features `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-secondary > a`
NFL Sunday Ticket `ytd-guide-renderer#guide-renderer > div#footer > div#guide-links-secondary > a`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Elements with the `role=text` attribute do not have focusable descendents.

●ARIA `tooltip` elements have accessible names

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○ARIA toggle fields have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
/videoplayback?expire=7112915130&ei=4D6qsqUFw7ENbZFESEpwM...	`Failed to load resource: the server responded with a status of 403 ()`
/videoplayback?expire=7112915130&ei=4D6qsqUFw7ENbZFESEpwM...	`Failed to load resource: the server responded with a status of 403 ()`
/videoplayback?expire=7112915130&ei=4D6qsqUFw7ENbZFESEpwM...	`Failed to load resource: the server responded with a status of 403 ()`
/videoplayback?expire=7112915130&ei=4D6qsqUFw7ENbZFESEpwM...	`Failed to load resource: the server responded with a status of 403 ()`
/videoplayback?expire=7112915130&ei=4D6qsqUFw7ENbZFESEpwM...	`Failed to load resource: the server responded with a status of 403 ()`
/videoplayback?expire=7112915130&ei=4D6qsqUFw7ENbZFESEpwM...	`Failed to load resource: the server responded with a status of 403 ()`

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
www.youtube.com/s/player/b174a5bb/player_es6.vflset/en_US/base.js
/s/_/ytmainappweb/_/js/k=ytmainappweb.kevlar_base.en_US.I...
www.youtube.com/?feature=youtu.be
/s/desktop/4329498d/jsbin/webcomponents-sd.vflset/webcomp...	/s/desktop/4329498d/jsbin/webcomponents-sd.vflset/blaze-o...
/s/desktop/4329498d/jsbin/web-animations-next-lite.min.vf...	/s/desktop/4329498d/jsbin/web-animations-next-lite.min.vf...
/s/desktop/4329498d/jsbin/custom-elements-es5-adapter.vfl...	/s/desktop/4329498d/jsbin/custom-elements-es5-adapter.vfl...
www.google.com/js/th/dTFo-KUuYlGOusziVr8u65jmcwADr_G5apr-mnW3AGs.js

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Ensure CSP is effective against XSS attacks

○Mitigate clickjacking with XFO or CSP

○Mitigate DOM-based XSS with Trusted Types

SEO

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
div.ytp-title-expanded-overlay > div.ytp-title-expanded-heading > div.ytp-title-expanded-title > a `div.ytp-title-expanded-overlay > div.ytp-title-expanded-heading > div.ytp-title-expanded-title > a`
div.ytp-chrome-top > div.ytp-title > div.ytp-title-text > a.ytp-title-link `div.ytp-chrome-top > div.ytp-title > div.ytp-title-text > a.ytp-title-link`
div.ytp-overlays-container > div.ytp-overlay-top-left > div.ytp-paid-content-overlay > a.ytp-paid-content-overlay-link `div.ytp-overlays-container > div.ytp-overlay-top-left > div.ytp-paid-content-overlay > a.ytp-paid-content-overlay-link`
div#ytp-id-6 > div.ytp-playlist-menu-header > div.ytp-playlist-menu-title > a.ytp-playlist-menu-title-name `div#ytp-id-6 > div.ytp-playlist-menu-header > div.ytp-playlist-menu-title > a.ytp-playlist-menu-title-name`
div#movie_player > div#ytp-id-9 > div.ytp-share-panel-inner-content > a.ytp-share-panel-link `div#movie_player > div#ytp-id-9 > div.ytp-share-panel-inner-content > a.ytp-share-panel-link`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes

Results for https://youtu.be

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Usability (2)

Content (2)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best practices

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Crawling and Indexing

Keyboard Shortcuts