# BeaverCheck Audit Report — https://www.youtube.com

**Date:** May 10, 2026  
**URL:** https://www.youtube.com  
**Overall Grade:** C (79/100)  
**Report:** https://beavercheck.com/results/82f6ddf4-f663-4c2f-a415-098488a6440d

## Top Findings

1. **[CRITICAL]** 13 button(s) with no accessible text — Accessibility > Link & Button Quality
2. **[CRITICAL]** 15 link(s) with no accessible text — Accessibility > Link & Button Quality
3. **[CRITICAL]** 2 image-only link(s) without alt text — Accessibility > Link & Button Quality
4. **[CRITICAL]** 4 image-in-link without alt text — Accessibility > Alt Text Quality
5. **[CRITICAL]** 5 image(s) missing alt attribute — Accessibility > Alt Text Quality

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 36 |
| Accessibility | 89 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

### Security Headers (B — 75/100)

*6 of 10 headers properly configured*

- **[WARNING]** HSTS is missing includeSubDomains — Without includeSubDomains, subdomains can still be accessed over HTTP.
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[PASS]** Permissions-Policy is set
- **[PASS]** Content-Security-Policy is present
- **[INFO]** Cross-Origin-Opener-Policy is set but not 'same-origin'
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[PASS]** X-Powered-By header is not present
- **[PASS]** Server header is present without version info
- **[PASS]** Domain is in the Chrome HSTS preload list (status: preloaded)

### Content Security Policy (C — 60/100)

*1 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[WARNING]** default-src directive is missing — default-src provides a fallback for other directives. Set it to restrict default resource loading.
- **[INFO]** No script-src or default-src to check for 'unsafe-inline'
- **[INFO]** No script-src or default-src to check for 'unsafe-eval'
- **[INFO]** No script-src or default-src to check for wildcard
- **[PASS]** object-src falls back to default-src
- **[WARNING]** base-uri directive is missing — Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
- **[WARNING]** frame-ancestors directive is missing — frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
- **[WARNING]** form-action directive is missing — form-action restricts where forms can submit data, preventing form hijacking.
- **[INFO]** upgrade-insecure-requests is not set — This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

### TLS & Certificates (A+ — 100/100)

*TLS 1.3, 7 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[INFO]** HTTP/2 is not negotiated — HTTP/2 provides multiplexing and header compression for better performance.
- **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
- **[PASS]** Certificate is valid (expires in 63 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 137 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

### Cookie Security (A+ — 95/100)

*7 cookies analyzed, 20 checks passed*

- **[PASS]** Cookie '__Secure-YNID' has the Secure flag
- **[PASS]** Cookie '__Secure-YNID' has the HttpOnly flag
- **[PASS]** Cookie '__Secure-YNID' has SameSite=None
- **[PASS]** Cookie 'GPS' has the Secure flag
- **[PASS]** Cookie 'GPS' has the HttpOnly flag
- **[WARNING]** Cookie 'GPS' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[PASS]** Cookie 'YSC' has the Secure flag
- **[PASS]** Cookie 'YSC' has the HttpOnly flag
- **[PASS]** Cookie 'YSC' has SameSite=None
- **[PASS]** Cookie '__Secure-ROLLOUT_TOKEN' has the Secure flag
- **[PASS]** Cookie '__Secure-ROLLOUT_TOKEN' has the HttpOnly flag
- **[PASS]** Cookie '__Secure-ROLLOUT_TOKEN' has SameSite=None
- **[PASS]** Cookie '__Secure-YEC' has the Secure flag
- **[PASS]** Cookie '__Secure-YEC' has the HttpOnly flag
- **[PASS]** Cookie '__Secure-YEC' has SameSite=Lax
- **[PASS]** Cookie 'VISITOR_INFO1_LIVE' has the Secure flag
- **[PASS]** Cookie 'VISITOR_INFO1_LIVE' has the HttpOnly flag
- **[PASS]** Cookie 'VISITOR_INFO1_LIVE' has SameSite=None
- **[PASS]** Cookie 'VISITOR_PRIVACY_METADATA' has the Secure flag
- **[PASS]** Cookie 'VISITOR_PRIVACY_METADATA' has the HttpOnly flag
- **[PASS]** Cookie 'VISITOR_PRIVACY_METADATA' has SameSite=None

### Cookie Hygiene (A+ — 100/100)

*All 7 cookie(s) pass hygiene checks*

- **[PASS]** All 7 cookie(s) pass hygiene checks

### WAF / Bot Protection (B — 75/100)

*No WAF detected via response headers*

- **[INFO]** No WAF detected — Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.

### security.txt (A — 85/100)

*Vulnerability disclosure policy*

- **[PASS]** security.txt found
- **[WARNING]** security.txt: Missing required 'Expires' field (RFC 9116)

### Cross-Origin Tab Safety (A+ — 100/100)

*No new-tab links found -- no tabnabbing surface*

- **[PASS]** No new-tab links present

### CSP Inline-Style Readiness (D — 60/100)

*153 inline style attribute(s) detected*

- **[WARNING]** 153 inline style attribute(s) detected — Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 153 inline style(s) is high. Affected element types include: html, iron-iconset-svg, svg, iframe, ytd-miniplayer. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

### Trusted Types (XSS Sink Hardening) (A+ — 100/100)

*Trusted Types enforced for 'script'*

- **[PASS]** Trusted Types enforced via require-trusted-types-for 'script'

### Bot Challenge Detection (A+ — 100/100)

*Scan reached real page content (no bot-protection interstitial)*

- **[PASS]** No bot-protection interstitial detected -- the rest of the report reflects the real page

### Soft-404 Detection (A+ — 100/100)

*No soft-404 patterns detected in page title or headings*

- **[PASS]** No soft-404 patterns detected in page title or headings

### Empty Page Detection (A+ — 100/100)

*Page has substantive body text and no placeholder / template-leak signals*

- **[PASS]** Page has substantive body text and no placeholder / template-leak signals

### Geo-Restriction Detection (A+ — 100/100)

*No geo-restriction signals detected -- scan reached the page from an allowed region*

- **[PASS]** No geo-restriction detected

### Maintenance Mode Detection (A+ — 100/100)

*No maintenance-mode signals detected -- scan reached a normal page*

- **[PASS]** No maintenance-mode signals detected

### Subresource Integrity Adoption (F — 30/100)

*0% SRI adoption (0/6 third-party resources)*

- **[WARNING]** SRI adoption: 0/6 third-party resources protected (0%) — Of 6 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource.

Missing SRI on (first 5 examples):
  - https://static.doubleclick.net/instream/ad_status.js
  - https://www.gstatic.com/cv/js/sender/v1/cast_sender.js
  - //fonts.googleapis.com/css2?family=Roboto:wght@300;400;500;700&family=YouTube+Sans:wght@300..900&display=swap
  - https://fonts.googleapis.com/css?family=Roboto:300italic,400italic,500italic,700italic
  - https://fonts.googleapis.com/css?family=Roboto+Mono:400

Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

### CORS Depth (A+ — 100/100)

*No CORS response headers -- the resource is same-origin-only by browser default*

- **[PASS]** No CORS response headers -- the resource is same-origin-only by browser default

### Permissions-Policy Granularity (F — 35/100)

*0% high-risk feature coverage (0/10)*

- **[WARNING]** Permissions-Policy covers 0/10 high-risk features (0%) — The Permissions-Policy header explicitly declares policies for 0/10 high-risk features.

Covered: 

Not declared (default-allow): camera, microphone, geolocation, payment, usb, serial, midi, accelerometer, gyroscope, magnetometer

The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them.

### Referrer-Policy Strictness (B — 75/100)

*Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)*

- **[INFO]** Referrer-Policy header not set -- browser default applies — Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior:

```
Referrer-Policy: strict-origin-when-cross-origin
```

This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.

### Source Map Exposure (A+ — 100/100)

*No source maps accessible (probed 7 candidate URL(s))*

- **[PASS]** No source maps accessible across 7 probed candidate(s)

### HTML Version Disclosure (A+ — 100/100)

*No software-version disclosures in HTML*

- **[PASS]** No software-version disclosures in HTML

### Open Redirect Surface (B — 90/100)

*1 link(s) carry redirect-shaped query parameter(s)*

- **[INFO]** 1 link(s) carry redirect-shaped query parameter(s) — Heuristic flag -- whether each endpoint actually permits an arbitrary redirect target depends on server-side validation. Audit the listed paths' redirect-target handling: the endpoint should either (a) restrict to a relative path, (b) restrict to an allowlisted host set, or (c) sign the target. Open redirects power phishing flows (the attacker's URL begins with your trusted domain) and bypass some SSRF-mitigation cookie scoping. Common parameter names flagged: redirect, redirect_uri, redirect_url, redirecturl, return, returnto, return_to, returnurl, return_url, next, nexturl, next_url, continue, goto, dest, destination, forward, target.

### Auth Security (A+ — 100/100)

*Page is not a login form -- auth-security checks are N/A*

- **[PASS]** Page does not appear to be a login form

### Subdomain Inventory Exposure (A+ — 100/100)

*No risky subdomain names in certificate SANs*

- **[PASS]** No risky subdomain names in certificate SANs

---

## Advanced Security

### Subresource Integrity (F — 20/100)

*0 of 6 external resources have SRI*

- **[WARNING]** External script from static.doubleclick.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

### JS Library Vulnerabilities (A+ — 100/100)

*No known vulnerabilities*

- **[PASS]** No known JavaScript library vulnerabilities detected

### Information Leakage (A+ — 100/100)

*No exposures*

- **[PASS]** security.txt is present — good practice
- **[PASS]** No sensitive files exposed

### Email Security (F — 0/100)

*no DMARC, no SPF*

- **[WARNING]** No DMARC record found — Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
- **[WARNING]** No SPF record found — Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

### API Surface (A+ — 100/100)

*No API specs or GraphQL introspection found (probed 11 candidate path(s))*

- **[PASS]** No API specs or GraphQL introspection found (probed 11 path(s))

### Permissions-Policy (C — 60/100)

*9 directives, 5 missing*

- **[INFO]** ch-ua-arch=*
- **[INFO]** ch-ua-bitness=*
- **[INFO]** ch-ua-full-version=*
- **[INFO]** ch-ua-full-version-list=*
- **[INFO]** ch-ua-model=*
- **[INFO]** ch-ua-wow64=*
- **[INFO]** ch-ua-form-factors=*
- **[INFO]** ch-ua-platform=*
- **[INFO]** ch-ua-platform-version=*
- **[INFO]** camera not restricted — Consider adding camera=() to block camera access from embedded content.
- **[INFO]** microphone not restricted — Consider adding microphone=() to block microphone access from embedded content.
- **[INFO]** geolocation not restricted — Consider adding geolocation=() to block geolocation access from embedded content.
- **[INFO]** payment not restricted — Consider adding payment=() to block payment access from embedded content.
- **[INFO]** usb not restricted — Consider adding usb=() to block usb access from embedded content.

### CORS Configuration (B — 80/100)

*No CORS headers*

- **[PASS]** No CORS headers present — secure default

---

## Performance

### Page Weight Budget (B — 77/100)

*1.3 MB transferred, 72 requests*

- **[PASS]** Page weighs 5.3 MB (1.3 MB transferred)
- **[WARNING]** JavaScript is 1005 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** 72 HTTP requests
- **[INFO]** Estimated 0.27 g CO2 per page load

### Third-Party Impact (D — 50/100)

*98% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 98% of page weight (1.3 MiB of 1.3 MiB)
- **[PASS]** Third-party blocking time is low (0 ms)

### Text Compression (A+ — 100/100)

*All text resources are compressed*

- **[PASS]** All text resources are compressed

### Image Optimization (A — 90/100)

*3 images, 0 KB saveable*

- **[PASS]** All images are well-optimized

### JS Execution Cost (F — 20/100)

*4502ms total JS execution*

- **[WARNING]** https://m.youtube.com/s/_/ytmweb/_/js/k=ytmweb.c3_...: 2281ms CPU time
- **[WARNING]** Unattributable: 953ms CPU time
- **[WARNING]** https://m.youtube.com/: 449ms CPU time
- **[WARNING]** https://m.youtube.com/s/player/8fb635c2/player-pla...: 293ms CPU time
- **[INFO]** https://m.youtube.com/s/_/ytmweb/_/js/k=ytmweb.c3_...: 127ms CPU time
- **[WARNING]** Third-party scripts: 4502ms (100% of total)

### Font Loading (A+ — 100/100)

*2 fonts (28 KB)*

- **[INFO]** 2 font(s) use font-display: swap (FOUT risk but functional)

### JS Bundles (F — 20/100)

*11 scripts, 618 KB unused*

- **[WARNING]** https://m.youtube.com/s/player/8fb635c2/player-pla...: 308 KB unused (74%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://m.youtube.com/s/_/ytmweb/_/js/k=ytmweb.c3_...: 223 KB unused (52%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://m.youtube.com/s/_/ytmweb/_/js/k=ytmweb.c3_...: 61 KB unused (77%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://m.youtube.com/s/_/ytmweb/_/js/k=ytmweb.c3_...: 26 KB unused (87%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 618 KB

### Resource Caching (A+ — 100/100)

*All resources properly cached*

- **[PASS]** No caching issues found

### Critical Rendering Path (A+ — 100/100)

*No render-blocking resources*

- **[PASS]** No render-blocking resources detected

### Resource Hints (A+ — 100/100)

*No optimization needed*

- **[PASS]** No resource hint issues

### HTTP/3 (QUIC) (A+ — 100/100)

*HTTP/3 advertised via Alt-Svc*

- **[PASS]** HTTP/3 (QUIC) is supported — First-load mobile users on cellular networks see meaningful latency improvements with HTTP/3. The QUIC transport collapses TLS + TCP handshakes into one and recovers faster from packet loss.

### Compression Algorithm (C — 70/100)

*Main response served uncompressed*

- **[INFO]** Main HTML response has no Content-Encoding (uncompressed) — The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.

### LCP Image Preload (A+ — 100/100)

*LCP preload audit not available*

- **[PASS]** LCP image preload audit not available for this scan

### Main HTML Cache-Control (A+ — 100/100)

*Main HTML uses no-store -- correct for sensitive/dynamic content*

- **[PASS]** Main HTML uses no-store -- correct for sensitive/dynamic content

### Server-Timing Observability (B — 85/100)

*No Server-Timing header found*

- **[INFO]** No Server-Timing header found — Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.

### Server Response Intelligence (A+ — 95/100)

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Sec-CH-Viewport-Width, Sec-CH-DPR, Device-Memory — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
- **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

### Page Weight Inventory (D — 40/100)

*72 resources · 1.3 MB · 618 KB savings available*

- **[WARNING]** Page weight 1.3 MB exceeds 1 MB target by 302 KB
- **[INFO]** ~618 KB of savings available
- **[WARNING]** 67 third-party resources (98% of weight)
- **[INFO]** 2 resources over 200KB

### Render-Blocking Resources (A+ — 100/100)

*No render-blocking resources detected*

- **[PASS]** No render-blocking resources detected in <head>

### Third-Party Resources (A+ — 100/100)

*No third-party resources detected*


### JavaScript Blocking (B — 70/100)

*2 JS blocking issue(s) detected*

- **[WARNING]** 9 render-blocking <script src> tag(s) without async/defer — Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.
- **[WARNING]** Total JS execution time is 4.5 s -- over the 3.5s budget — Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.

### CSS Performance Depth (A — 88/100)

*1 CSS depth issue(s) detected*

- **[WARNING]** 8 render-blocking stylesheet(s) -- recommended: <=3 — Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.

---

## Content Quality

### Links (B — 85/100)

*39 links checked, 36 healthy, 3 broken*

- **[WARNING]** 36 of 39 links are healthy
- **[WARNING]** Broken link: android-app://com.google.android.youtube/http/www.youtube... — Found in <link href>. Get "android-app://com.google.android.youtube/http/www.youtube.com/": unsupported protocol scheme "android-app"
- **[WARNING]** Broken link: ios-app://544007664/vnd.youtube/www.youtube.com/ — Found in <link href>. Get "ios-app://544007664/vnd.youtube/www.youtube.com/": unsupported protocol scheme "ios-app"
- **[WARNING]** Broken link: about:blank — Found in <iframe src>. Get "about:blank": unsupported protocol scheme "about"

### Mixed Content (A+ — 100/100)

*No mixed content detected — all resources use HTTPS.*

- **[PASS]** No mixed content detected — all resources use HTTPS

### Open Graph (D — 65/100)

*Open Graph tags need attention — social sharing previews may be incomplete.*

- **[WARNING]** Missing og:description — The og:description tag controls the description in social sharing previews.
- **[INFO]** og:title is short (7 characters) — Ideal length is 25–60 characters for social sharing previews.
- **[INFO]** Missing og:url — The og:url tag specifies the canonical URL for the shared content.
- **[INFO]** Missing og:type — The og:type tag helps social platforms categorize the content.
- **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social previews.
- **[INFO]** Missing twitter:card — Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

### Open Graph / Twitter Card Depth (A+ — 100/100)

*OG image dimensions and Twitter card configuration look healthy*

- **[PASS]** OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid

### Structured Data (C — 40/100)

*No structured data (JSON-LD) found.*

- **[INFO]** No structured data (JSON-LD) found — Adding structured data helps search engines understand your content and can enable rich results.

### Rich Results Eligibility (C — 75/100)

*No JSON-LD found -- no rich-result eligibility*

- **[INFO]** No JSON-LD structured data on the page — No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.

### Image Optimization (D — 65/100)

*3 issues found across 7 images*

- **[WARNING]** 7 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 7 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** 7 images missing alt text — Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.

### Autoplay Media (A+ — 100/100)

*1 media element(s) found, none autoplay*

- **[PASS]** 1 media element(s) found, none autoplay

---

## Infrastructure

### DNS Records (B — 70/100)

*16 A records, 254 ms lookup*

- **[PASS]** Resolves to 16 IPv4 address(es)
- **[PASS]** Has 4 IPv6 (AAAA) record(s)
- **[WARNING]** CNAME record at zone apex — A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
- **[INFO]** No NS records found
- **[INFO]** No MX records — email not configured via DNS
- **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
- **[WARNING]** DNS resolution is slow (254 ms) — Slow DNS adds latency to every page load. Consider a faster DNS provider.

### Subdomain Takeover (A+ — 100/100)

*No subdomain takeover risk detected*

- **[PASS]** CNAME does not point at a known takeover-able service

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

- **[INFO]** DNSSEC is not deployed — The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

### CAA Records (B — 80/100)

*No CAA records (any CA may issue certificates)*

- **[INFO]** No CAA records published — Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

### Reverse DNS (B — 75/100)

*0/20 IPs match cert SAN*

- **[INFO]** PTR for 172.217.29.142 does not match any cert SAN: gru06s47-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 172.217.28.46 does not match any cert SAN: pngrub-ab-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 172.217.28.174 does not match any cert SAN: pngrub-ae-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 172.217.30.110 does not match any cert SAN: gru06s35-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 172.217.28.78 does not match any cert SAN: pngrub-ac-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 142.251.135.238 does not match any cert SAN: pngrub-aa-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 172.217.29.110 does not match any cert SAN: pngrua-ac-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 172.217.28.206 does not match any cert SAN: pngrub-af-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 142.250.78.110 does not match any cert SAN: bog02s17-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 172.217.28.142 does not match any cert SAN: gru09s09-in-f142.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 172.217.30.78 does not match any cert SAN: pngrua-aj-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 142.250.78.142 does not match any cert SAN: pngrua-by-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 172.217.30.14 does not match any cert SAN: rio01s23-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 172.217.29.238 does not match any cert SAN: pngrua-ag-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 142.250.219.238 does not match any cert SAN: pngrua-al-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 142.250.219.206 does not match any cert SAN: gru06s64-in-f14.1e100.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR lookup failed for 2800:3f0:4001:814::200e: lookup 2800:3f0:4001:814::200e: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2800:3f0:4001:815::200e: lookup 2800:3f0:4001:815::200e: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2800:3f0:4001:80e::200e: lookup 2800:3f0:4001:80e::200e: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2800:3f0:4001:80d::200e: lookup 2800:3f0:4001:80d::200e: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

### Multi-Resolver DNS Speed (B — 80/100)

*Mean 39ms across 3 resolvers (spread 115ms)*

- **[PASS]** Quad9: 1ms
- **[PASS]** Cloudflare: 1ms
- **[PASS]** Google: 116ms

### Redirect Chain (A+ — 100/100)

*No redirects — direct access*

- **[PASS]** No redirects — direct access

### IPv6 Readiness (A+ — 100/100)

*IPv6 reachable (2 ms)*

- **[PASS]** IPv6 is configured and reachable at 2800:3f0:4001:814::200e, 2800:3f0:4001:815::200e, 2800:3f0:4001:80e::200e, 2800:3f0:4001:80d::200e

### Crawlability (A+ — 100/100)

*robots.txt present, sitemap with 20 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 20 entries
- **[PASS]** Sitemap index with 20 child sitemaps
- **[PASS]** robots.txt references sitemap

### URL Variants (A+ — 100/100)

*www/non-www, trailing slash, HTTP→HTTPS*

- **[PASS]** www/non-www redirect configured correctly (preferred: www)
- **[PASS]** HTTP correctly 301-redirects to HTTPS

### Domain Intelligence (A+ — 100/100)

*youtube.com — via MarkMonitor Inc., 21 years, 6 months old*

- **[PASS]** Domain registered until Feb 15, 2027 (9 months remaining)
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[PASS]** Registrar: MarkMonitor Inc.
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

---

## Compliance

### WCAG Compliance (A+ — 100/100)

*No testable criteria*


### Cookie Consent & Privacy (D — 40/100)

*No consent signals detected*

- **[WARNING]** No privacy policy link detected — A privacy policy page is recommended for transparency and may be legally required.
- **[INFO]** No terms of service link detected
- **[INFO]** No cookie consent banner detected
- **[CRITICAL]** 7 non-essential cookie(s) set without consent banner — Unrecognized (treated as non-essential): __Secure-YNID, GPS, YSC, __Secure-ROLLOUT_TOKEN, __Secure-YEC, VISITOR_INFO1_LIVE, VISITOR_PRIVACY_METADATA
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

### Consent UX Depth (A+ — 100/100)

*No consent-UX depth issues detected*

- **[PASS]** No consent-UX depth issues detected

### Tracker Inventory (A+ — 100/100)

*No known trackers detected on this page*

- **[PASS]** No known trackers detected on this page

### Language & i18n (A — 90/100)

*Lang attribute present*

- **[PASS]** <html lang> attribute is present
- **[PASS]** <html lang> value is valid
- **[INFO]** No Content-Language HTTP header
- **[INFO]** Language signals are inconsistent — The <html lang> attribute and Content-Language header should agree.

### Hreflang Configuration (A+ — 100/100)

*No hreflang tags on this page*

- **[PASS]** No hreflang tags found (single-language site)

### Internationalization Extras (A+ — 100/100)

*No additional i18n signals detected*

- **[PASS]** No additional i18n signals detected

### Readability & Typography (A+ — 100/100)

*Font sizes and tap targets checked*


### Viewport Configuration (A+ — 100/100)

*Viewport properly configured*

- **[PASS]** Viewport meta tag is present
- **[PASS]** width=device-width is set
- **[PASS]** User zooming is allowed

### Accessibility Statement (B — 70/100)

*No accessibility statement detected*

- **[WARNING]** No accessibility statement detected — Sites are increasingly expected to publish an accessibility statement. Required by EU Web Accessibility Directive 2016/2102 for public-sector bodies; recommended best practice elsewhere. Common URLs: /accessibility, /accessibility-statement, /a11y.

### GDPR Article 13 Disclosures (F — 25/100)

*0 / 8 Art. 13 categories matched in homepage body*

- **[WARNING]** GDPR Article 13 disclosure coverage: 0 / 8 categories — Scanned the homepage body text for GDPR Article 13 disclosures. Matched 0 of 8 categories: . Missing: Data Protection Officer contact (where applicable), Data retention period, Data subject rights (access, erasure, rectification, etc.), Identity / contact details of the data controller, International data transfers, Legal basis for processing, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Note: this scan does not fetch the privacy policy sub-page; if Article 13 disclosures live there, they are not visible to this check.

### Third-Party Trackers (D — 40/100)

*1 trackers detected*

- **[INFO]** 1 third-party trackers detected — Found 0 analytics, 1 advertising, 0 marketing, 0 tag manager, 0 session-replay, 0 heatmap trackers.
- **[WARNING]** 1 advertising/retargeting trackers detected — Advertising trackers collect user data for ad targeting. Under GDPR, these typically require explicit consent.
- **[WARNING]** Trackers detected but no cookie policy found — This page loads 1 trackers but no cookie policy was detected. GDPR requires disclosure when using tracking cookies.
- **[WARNING]** Trackers detected but no privacy policy found — Most data protection regulations require a privacy policy when collecting user data via trackers.

### Cookie & Tracker Inventory (C — 68/100)

*7 cookies · 1 trackers · 4 pre-consent*

- **[CRITICAL]** 4 tracking cookie(s) set before consent interaction — Under GDPR ePrivacy Art. 5(3), analytics and advertising cookies require explicit opt-in. These cookies appeared in the server response without any consent step — a likely violation.
- **[INFO]** 1 cookie(s) could not be classified
- **[INFO]** 1 third-party tracker(s) detected on page

### Tracking Pixel Inventory (A+ — 100/100)

*No tracking pixels detected*

- **[PASS]** No tracking pixels detected

### Browser Fingerprinting (A+ — 100/100)

*No browser-fingerprinting libraries detected*

- **[PASS]** No browser-fingerprinting libraries detected

### Cross-Site Cookies (SameSite=None) (C — 70/100)

*5 cross-site cookie(s) (3 tracking-shaped, 2 essential)*

- **[WARNING]** 3 tracking-shaped cross-site cookie(s): VISITOR_INFO1_LIVE, VISITOR_PRIVACY_METADATA, YSC — Cookies with SameSite=None travel in cross-site contexts (third-party iframes, cross-origin POSTs, embedded widgets). With third-party cookies dying in Chrome/Firefox, the legitimate use cases narrowed to SSO + payment widgets + federated auth. Each tracking-shaped cookie surfaced here is a cross-site analytics or ad-tech surface that needs explicit privacy-policy disclosure beyond basic cookie banner consent. Audit each: is it conditional on consent? Does the privacy policy name the recipient + purpose? Switching to SameSite=Lax disables the cross-site travel without breaking same-site analytics.

### Beacon Tracking (sendBeacon) (A+ — 100/100)

*No navigator.sendBeacon usage detected in inline scripts*

- **[PASS]** No navigator.sendBeacon usage detected in inline scripts

---

## Legal

### Legal Page Ecosystem (F — 0/100)

*0 of 7 expected legal pages detected*

- **[WARNING]** Privacy Policy not detected — No link matching common Privacy Policy URL patterns or link text was found. Most websites are expected to have a Privacy Policy, especially those collecting user data.
- **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

### Copyright Notice (C — 55/100)

*No copyright notice detected*

- **[INFO]** No copyright notice detected — No copyright notice detected in the page content. While not legally required in most jurisdictions (copyright exists automatically), a notice is standard practice and signals site ownership.

### Regulatory Indicators

*0 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** No specific regulatory indicators detected — No strong signals for GDPR, CCPA, ADA, PCI, HIPAA, or COPPA were found. This does not mean these regulations don't apply — it means we didn't detect common technical indicators.

### Third-Party Data Sharing

*0 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** No recognized third-party data-sharing services detected — This page does not appear to load external tracking, analytics, or advertising scripts.

### Compliance Badges (C — 55/100)

*0 compliance badge(s) detected*

- **[INFO]** No compliance badges detected — No recognized compliance certification badges or seals were found. This is common — many sites do not display compliance badges.

---

## Availability

### CDN & Delivery (D — 50/100)

*No CDN detected*

- **[WARNING]** No CDN detected — A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

### HTTP Caching (D — 40/100)

*no-store (uncacheable)*

- **[INFO]** Cache-Control: no-store prevents all caching — Intentional for dynamic content, but increases server load for every page view.
- **[INFO]** No ETag or Last-Modified header — Conditional requests (304 Not Modified) are not possible without validators.

### Operational Status Page (B — 80/100)

*No status page link detected*

- **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

### Transport Security (A+ — 100/100)

*HTTP/3, HSTS, and TLS version analysis*

- **[PASS]** HTTP/3 (QUIC) supported — The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.
- **[PASS]** HSTS enabled (base policy)
- **[INFO]** HSTS missing includeSubDomains — Without includeSubDomains, HSTS only protects the exact domain.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

### Health Check Endpoint (A+ — 100/100)

*Health endpoint at https://www.youtube.com/health (HTTP 200)*

- **[PASS]** Public health endpoint at https://www.youtube.com/health

### CDN Cache Observability (B — 85/100)

*No CDN cache-status headers in the response*

- **[INFO]** No CDN cache-status headers in the response — Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

---

## Accessibility

### Landmark Structure (B — 70/100)

*6 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 2 <nav> landmark(s) found
- **[WARNING]** 2 of 2 <nav> elements are unlabeled — Multiple navigations need aria-label to distinguish them for screen readers.
- **[INFO]** No contentinfo (footer) landmark
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
- **[PASS]** Search landmark present

### Heading Hierarchy (C — 60/100)

*7 headings*

- **[WARNING]** Multiple H1 headings (4 found) — A page should have only one H1. Multiple H1s dilute the document outline.
- **[WARNING]** 6 empty heading(s) — Empty headings appear in the document outline but provide no information.

### Heading Text Quality (A+ — 100/100)

*All 7 heading(s) have substantive, well-formed text*

- **[PASS]** Heading text quality is clean -- no placeholder, length, or styling issues

### Alt Text Quality (F — 30/100)

*5 of 7 images have issues*

- **[CRITICAL]** 5 image(s) missing alt attribute — Images without alt text are invisible to screen readers.
- **[CRITICAL]** 4 image-in-link without alt text — An image inside a link with no alt creates an empty link.
- **[PASS]** 2 decorative image(s) correctly marked

### Form Accessibility (A — 92/100)

*1 of 2 controls have issues*

- **[WARNING]** 1 control(s) rely on placeholder only — Placeholder text disappears on focus and is not a reliable label.
- **[PASS]** 1 control(s) properly labeled

### Link & Button Quality (F — 27/100)

*28 issue(s) across 20 links and 47 buttons*

- **[CRITICAL]** 15 link(s) with no accessible text — Links without text are announced as raw URLs by screen readers.
- **[CRITICAL]** 2 image-only link(s) without alt text — Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
- **[WARNING]** 1 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[CRITICAL]** 13 button(s) with no accessible text — Icon-only buttons need an aria-label so screen readers can announce them.
- **[PASS]** 2 link(s) with descriptive text

### Form Input Types (A+ — 95/100)

*1 input(s) using type=text where a specific type would help*

- **[INFO]** Input "search_query" should use type="search" (currently type="text") — Field name "search_query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

### Form Input Quality (A+ — 100/100)

*2 form control(s) checked, no input-semantic issues*

- **[PASS]** All form input semantics look correct

### Mobile Keyboard & Autofill (A+ — 100/100)

*No autofill-eligible form controls*

- **[PASS]** No autofill-eligible form controls (no name/email/tel/address fields)

### Document Language (A+ — 100/100)

*Lang attribute set to "en"*

- **[PASS]** <html lang="en"> is set and valid

### Tabindex Anti-Patterns (A+ — 100/100)

*19 explicit tabindex attribute(s) checked, no anti-patterns*

- **[PASS]** No tabindex anti-patterns detected

### Iframe Accessibility (B — 80/100)

*2/2 iframe(s) missing title; 0 placeholder(s)*

- **[WARNING]** <iframe> missing title attribute (src="https://accounts.google.com/ServiceLogin?service=youtube&uilel=3&passive=true&c…") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="about:blank") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

### Tap Target Adequacy (A+ — 100/100)

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

- **[PASS]** All tap targets meet WCAG 2.5.5 (44x44px) sizing

### Mobile-Readable Font Sizes (C — 75/100)

*80% of visible text renders at >= 12 CSS px (1 below threshold)*

- **[WARNING]** 1 text node(s) render below 12 CSS pixels on mobile — Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("BR").

---

## UX

### 404 Error Page (C — 55/100)

*HTTP 404, custom page*

- **[PASS]** Correct 404 status code returned
- **[PASS]** Custom styled 404 page

### Favicon & Branding (C — 65/100)

*14 icon(s) detected*

- **[PASS]** favicon.ico present at site root
- **[PASS]** HTML icon links detected
- **[INFO]** No apple-touch-icon detected — iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
- **[PASS]** Multiple icon sizes detected

### Web Manifest (A+ — 95/100)

*PWA-ready*

- **[PASS]** Meets PWA install criteria
- **[PASS]** Name present: YouTube
- **[PASS]** 192x192 icon present
- **[PASS]** 512x512 icon present
- **[PASS]** Display mode: minimal-ui

### PWA Depth (A+ — 100/100)

*No PWA depth issues detected*

- **[PASS]** No PWA depth issues detected

### Dark Mode Support (D — 40/100)

*No dark mode signals*

- **[INFO]** No dark mode signals detected — Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

### Print Stylesheet (D — 40/100)

*No print styles*

- **[INFO]** No print-specific styles detected — When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

### Navigation UX (D — 40/100)

*1 navigation pattern(s)*

- **[PASS]** Search functionality detected
- **[PASS]** 2 navigation landmark(s) detected
- **[PASS]** Hamburger menu detected (responsive design)

### Mobile UX Depth (A+ — 97/100)

*2 mobile-depth signal(s) detected*

- **[INFO]** No `<meta name="theme-color">` -- browser chrome falls back to default — Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
- **[PASS]** Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices — The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

---

## SEO

### Canonical URL (A+ — 100/100)

*Properly configured*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[PASS]** Canonical target returns 200

### Meta Tags (A — 90/100)

*Title: 7 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 7 characters — consider expanding
- **[PASS]** Meta description length (126 chars) is optimal

### Title Style Depth (A+ — 100/100)

*Title style is clean -- consistent separator, no stale year, no keyword stuffing*

- **[PASS]** Title style is clean

### Content Depth (F — 25/100)

*112 words, Standard*

- **[WARNING]** Page has 112 words — thin content — Most well-ranking pages have 300+ words of substantive content.
- **[INFO]** Text-to-HTML ratio is 0% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Standard (grade 9)
- **[WARNING]** Thin content — only 112 words

### Internal Links (A — 85/100)

*19 internal, 1 external*

- **[PASS]** 19 internal links (95%)
- **[WARNING]** Only 25% of links use descriptive anchor text — Generic text like 'click here' wastes an opportunity to tell search engines what the linked page is about.
- **[INFO]** 19 internal / 1 external links

### Image SEO (B — 75/100)

*7 images, 0 descriptive filenames*

- **[WARNING]** 100% of images have non-descriptive filenames — Search engines use filenames as a signal. Rename to descriptive names like 'team-photo.jpg'.
- **[INFO]** 5 image(s) missing alt text — see Accessibility tab

### Hreflang

*0 hreflang tags*


### Hreflang URL Quality (A+ — 100/100)

*No hreflang tags on the page*

- **[PASS]** No hreflang tags on the page

### Hreflang Completeness (A+ — 100/100)

*No hreflang tags on this page -- check is N/A (single-language site or unannotated)*

- **[PASS]** No hreflang tags found -- completeness check is N/A

### Sitemap Freshness (C — 70/100)

*Sitemap exists but no <lastmod> entries*

- **[INFO]** Sitemap has no <lastmod> entries — Without lastmod, Google can't tell which URLs have changed since the last crawl -- it falls back to crawling everything periodically. Adding lastmod (date or ISO 8601 timestamp) on each <url> entry signals freshness so the crawler prioritizes recently-modified pages.

### Sitemap × Robots Consistency (A+ — 100/100)

*No sitemap-vs-robots conflicts detected*

- **[PASS]** Sitemap URLs are not blocked by robots.txt

### Sitemap Hygiene (A+ — 100/100)

*Sitemap structure / size look healthy (20 URLs, 2 KB)*

- **[PASS]** Sitemap structure / size look healthy (20 URLs)

### Markup Quality (A — 90/100)

*1 markup-quality issue(s) detected*

- **[WARNING]** No `<meta charset>` declaration in HTML — The page has no `<meta charset="...">` tag. Browsers fall back to a default encoding (typically UTF-8 in modern browsers, but not guaranteed). Add `<meta charset="utf-8">` as the first child of `<head>` to make the encoding explicit.

---

## Sustainability

### CO2 Per Page Load (A — 85/100)

*0.31g CO2 per view*

- **[PASS]** 0.31g CO2 per page view — This page transfers 1.3 MB, producing an estimated 0.31g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.01g, network 0.06g, end-user device 0.24g.
- **[INFO]** At 10,000 monthly views: 36.8 kg CO2/year — With 10,000 page views per month, this page would generate approximately 36.8 kg of CO2 annually — equivalent to charging 4596 smartphones.
- **[PASS]** Green hosting reduces data center emissions

### Green Hosting (B — 80/100)

*Green (hosting)*

- **[PASS]** Google Cloud uses renewable energy
- **[INFO]** Google Cloud: Verified by the Green Web Foundation
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

### Repeat Visit Weight (A+ — 100/100)

*95% cached*

- **[PASS]** 95% reduction on repeat visits — Returning visitors download only 63 KB (vs 1325 KB first visit). 70 of 72 resources are served from browser cache, saving 0.29g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.31g)

### Carbon Budget (A — 85/100)

*20th percentile*

- **[PASS]** 0.31g CO2 — below the sustainability target of 0.50g — Cleaner than an estimated 80% of websites analyzed. This page meets the Web Sustainability Guidelines target.
- **[INFO]** Estimated 20th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

### Transfer Efficiency (D — 40/100)

*53% efficient*

- **[WARNING]** Transfer efficiency: 53% — An estimated 618 KB (47%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 618 KB of unused JavaScript. This wasted data produces 0.14g of unnecessary CO2 per page view.

### Web Font Weight Variants (C — 70/100)

*10 font weights loaded across 3 famil(y/ies)*

- **[WARNING]** 10 font weights loaded -- likely 100+ KB of unused payload — Loading 10 font weights typically transfers 200-400 KB just for fonts. Most pages legitimately use 2-3 weights (regular + bold, maybe medium). Audit which weights your stylesheet actually applies and trim the Google Fonts URL accordingly. Affected families: Roboto, Roboto Mono, YouTube Sans.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/82f6ddf4-f663-4c2f-a415-098488a6440d*