Spain · Madrid Completed: Apr 16, 2026 16:56 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 77 / 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.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Good content signals with minor gaps.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
'unsafe-eval' found in script source
Security gaps expose your site and users to attacks, eroding trust.
'unsafe-inline' found in script source
Security gaps expose your site and users to attacks, eroding trust.
1 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
2 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
2 image(s) missing alt attribute
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/ba1d4cd5-c90e-4e6b-8567-7a8b11540a68)<a href="https://beavercheck.com/results/ba1d4cd5-c90e-4e6b-8567-7a8b11540a68"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fyoutube.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fyoutube.comThis badge auto-updates with your latest scan result.
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.
9 barrier(s) likely increasing bounce by ~39%.
Page takes 8.1s to load
+12% bounceUsers abandon at ~3s — you're 5.6s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 718ms
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
1 form field(s) without a label
+2% bounceScreen 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% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
No structured data
+2% bounceNo 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, …)
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
No skip-to-content link
+1% bounceKeyboard 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% bounceClicks 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.
€468 investment → €4,992/month returns + EUR 500,000 risk avoided
€468
6h · 5 findings
€4,992 /mo
~€59,906 / year
EUR 500,000
if kept compliant
€85 — 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.
5.5 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€41,667 / month at risk
~€500,004 / year if left unfixed
€500,000
+5 more
€0.30 /mo
3999.9 MB/mo × 0.074 EUR/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
6.04 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
8.10 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
718 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.
6.04 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.16 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| m.youtube.com/static/r/072389cc/scheduler.vflset/scheduler.js | 3.1 KiB | 489 ms |
| m.youtube.com/static/r/072389cc/fetch_polyfill.vflset/fetch_polyfill.js | 2.6 KiB | 489 ms |
| /s/_/ytmweb/_/ss/k=ytmweb.c3_base.Nl539GGld64.L.W.O/am=AA... | 116.6 KiB | 2.0 s |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| youtube.com/ | 841 ms |
| m.youtube.com/ | 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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /s/_/ytmweb/_/ss/k=ytmweb.c3_base.Nl539GGld64.L.W.O/am=AA... | 116.6 KiB | 114.2 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| m.youtube.com/s/player/b174a5bb/player-plasma-es6-en_US.vflset/base.js | 417.1 KiB | 308.3 KiB |
| /s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021.... | 434.8 KiB | 230.8 KiB |
| /s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021.... | 77.3 KiB | 59.4 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.
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.2 s | 918 ms | 120 ms |
| Unattributable | 650 ms | 123 ms | 0.0 ms |
| m.youtube.com/ | 446 ms | 139 ms | 42 ms |
| /s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021.... | 230 ms | 189 ms | 0.7 ms |
| m.youtube.com/s/player/b174a5bb/player-plasma-es6-en_US.vflset/base.js | 167 ms | 56 ms | 108 ms |
| m.youtube.com/static/r/072389cc/scheduler.vflset/scheduler.js | 106 ms | 73 ms | 1.1 ms |
| www.google.com/js/th/cdHZnmAh7yL5wO3Dlc3wxOFdaDuUvCTre1L4S51GVXg.js | 104 ms | 93 ms | 4.9 ms |
| /s/_/ytmweb/_/js/k=ytmweb.c3_base.en_US.4A446WuLG4I.2021.... | 81 ms | 73 ms | 6.7 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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 2.3 s |
| Other | 687 ms |
| Script Parsing & Compilation | 304 ms |
| Style & Layout | 160 ms |
| Garbage Collection | 104 ms |
| Parse HTML & CSS | 104 ms |
| Rendering | 28 ms |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
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 |
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Learn more div.feed-nudge-text-container > div.feed-nudge-subtitle > span.ytAttributedStringHost > a.ytAttributedStringLink |
These are opportunities to improve the legibility of your content.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Afrikaans
Azərbaycan
Bahasa Indonesia
Bahasa Malaysia
Bosanski
Català
Čeština
D… div.custom-language-select > ytm-dropdown-renderer.language-picker-dropdown > ytm-select > select#dropdown:0 |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.12 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.56 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
488 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.027
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.98 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.
5.22 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.gstatic.com/eureka/clank/147/cast_sender.js | 86400.0 s | 13.1 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| youtube.com/ | 278 ms |
| www.youtube.com/ | 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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /s/_/ytmainappweb/_/ss/k=ytmainappweb.kevlar_base.yAlYZ9F... | 271.6 KiB | 262.3 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| 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.3 KiB | 467.1 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.
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.1 s | 821 ms | 166 ms |
| /s/desktop/4329498d/jsbin/web-animations-next-lite.min.vf... | 571 ms | 391 ms | 0.9 ms |
| Unattributable | 414 ms | 141 ms | 0.0 ms |
| www.youtube.com/s/player/b174a5bb/player_es6.vflset/en_US/base.js | 164 ms | 113 ms | 46 ms |
| www.youtube.com/ | 131 ms | 13 ms | 21 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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.8 s |
| Other | 430 ms |
| Script Parsing & Compilation | 243 ms |
| Parse HTML & CSS | 108 ms |
| Style & Layout | 95 ms |
| Garbage Collection | 52 ms |
| Rendering | 12 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
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 |
| ServiceWorker was unregistered while a page was in back/forward cache. | Not actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
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 |
These items highlight common accessibility best practices.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Reject all div.eom-button-row > ytd-button-renderer.style-scope > yt-button-shape > button.yt-spec-button-shape-next |
Accept all div.eom-button-row > ytd-button-renderer.style-scope > yt-button-shape > button.yt-spec-button-shape-next |
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.
Performance issues directly impact user engagement and conversion rates.
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.
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
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.
Send Feedback