vercel.com

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

• 01
  FAIL · security

  Exposed Paths

  Publicly-readable sensitive paths detected: /.svn/entries. These should not be accessible without auth — they often leak source code, credentials, or backups.
  Войдите, чтобы увидеть как исправить
• 02
  FAIL · technical

  Internal link health

  7/10 sampled internal links failed: 7 4xx, 0 5xx, 0 broken redirects, 0 timeouts, 0 errors.
  Войдите, чтобы увидеть как исправить
• 03
  WARN · technical

  Viewport Meta Tag

  The viewport meta tag restricts user zoom capability (maximum-scale=1). This creates accessibility issues — users with visual impairments will not be able to enlarge the content. Google may consider this a degraded user experience.
  Войдите, чтобы увидеть как исправить
• 04
  FAIL · performance

  Page Size

  The total HTML page size is 939.6 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.
  Войдите, чтобы увидеть как исправить
• 05
  WARN · performance

  Time to First Byte (TTFB)

  Time to First Byte is 1480 ms (1.48 sec). Google flags this as "needs improvement" (800 ms – 1.8 s per web.dev). LCP is bounded by TTFB, so reaching the "good LCP" 2.5s threshold becomes harder as TTFB grows.
  Войдите, чтобы увидеть как исправить
• 06
  FAIL · performance

  Render-Blocking Resources

  Found 12 render-blocking resources (11 CSS, 1 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).
  Войдите, чтобы увидеть как исправить
• 07
  FAIL · performance

  Image Lazy Loading

  Only 8 out of 20 images (40%) use lazy loading — this is very low. The browser is forced to load most images immediately, even if they are far outside the visible area.
  Войдите, чтобы увидеть как исправить
• 08
  FAIL · performance

  HTTP Requests Count

  The page loads 118 external resources — this is too many (11 CSS, 66 JS, 19 images). A high number of HTTP requests critically slows down page loading, as browsers are limited to 6 simultaneous connections per domain. This negatively affects all performance metrics.
  Войдите, чтобы увидеть как исправить
• 09
  WARN · security

  Security Headers

  Found 5 out of 6 modern security headers. Missing: permissions-policy. Add the remaining headers to close defense-in-depth gaps. Note: Content-Security-Policy is the highest-impact header — if it is missing the site is exposed to XSS even when other headers are present.
  Войдите, чтобы увидеть как исправить
• 10
  FAIL · security

  Server Signature

  The Server header is present: "Vercel". Although the exact version is not revealed, minimizing server information is recommended. The X-Powered-By header reveals the framework in use: "Next.js, Payload". This is a significant security risk — attackers gain information about the technology stack for targeted attacks.
  Войдите, чтобы увидеть как исправить