youtube.com

Показано 10 проблем. Полный аудит с кодом исправлений доступен на бесплатном плане.

• 01
  FAIL · onpage

  Content Length

  Only 12 words were found on the page. This is extremely low for proper indexing. Pages with minimal text content (fewer than 100 words) are considered "thin content" by search engines and rank poorly.
  Войдите, чтобы увидеть как исправить
• 02
  FAIL · onpage

  H1 Heading

  The H1 heading is missing from the page. The <h1> tag is the primary heading and one of the most important on-page ranking factors. Search engines use it to determine the main topic of the page.
  Войдите, чтобы увидеть как исправить
• 03
  FAIL · content

  Thin Content

  The page contains almost no text (12 words). This is critically insufficient for search engine indexing. Text-to-HTML ratio: 0%. Such pages may be classified as doorway pages or empty shells and excluded from search results.
  Войдите, чтобы увидеть как исправить
• 04
  WARN · technical

  HTTP Redirects

  WWW canonicalization is not configured. The site is accessible with both www and non-www addresses simultaneously, which leads to duplicate content issues for search engines.
  Войдите, чтобы увидеть как исправить
• 05
  FAIL · technical

  Viewport Meta Tag

  The viewport meta tag is missing. Without this tag, the page will not render correctly on mobile devices — content will be scaled down to fit a desktop-sized screen. Google uses mobile-first indexing, so a missing viewport tag critically impacts mobile search rankings.
  Войдите, чтобы увидеть как исправить
• 06
  FAIL · technical

  WWW Canonicalization

  WWW/non-www canonicalization is not configured. The site is accessible at both addresses (youtube.com and www.youtube.com), which results in duplicate content. Search engines may index both versions and split link equity between them.
  Войдите, чтобы увидеть как исправить
• 07
  FAIL · performance

  Page Size

  The total HTML page size is 721.1 KB, which significantly exceeds the recommended limit of 100 KB. Heavy pages load slowly, especially on mobile devices and slow internet connections. This negatively impacts Core Web Vitals and search rankings.
  Войдите, чтобы увидеть как исправить
• 08
  WARN · performance

  Time to First Byte (TTFB)

  Time to First Byte is 316 ms (0.32 sec). This is acceptable but there is room for improvement. The optimal value is less than 200 ms. A slow TTFB delays the start of page rendering.
  Войдите, чтобы увидеть как исправить
• 09
  FAIL · performance

  Render-Blocking Resources

  Found 12 render-blocking resources (4 CSS, 8 JS) — this is too many. The browser must download and process all of these files before it can start rendering the page. This critically delays First Contentful Paint (FCP) and Largest Contentful Paint (LCP).
  Войдите, чтобы увидеть как исправить
• 10
  WARN · security

  Security Headers

  Found 6 out of 7 recommended security headers. Missing: referrer-policy. Adding the missing headers is recommended for complete protection.
  Войдите, чтобы увидеть как исправить