zapier.com

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

• 01
  FAIL · technical

  Internal link health

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

  HTTP Requests Count

  The page loads 138 external resources — this is too many (3 CSS, 20 JS, 77 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.
  Войдите, чтобы увидеть как исправить
• 03
  WARN · security

  Security Headers

  Found 4 out of 6 modern security headers. Missing: x-frame-options, 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.
  Войдите, чтобы увидеть как исправить
• 04
  FAIL · content

  Keyword Stuffing

  Keyword stuffing detected. The following words appear excessively often: "zapier" — 60 times (4.9%). The acceptable keyword density is 1-2%. Exceeding the 3% threshold may result in search engine penalties.
  Войдите, чтобы увидеть как исправить
• 05
  FAIL · ai-readiness

  Structured Data Completeness

  No structured data (JSON-LD / Schema.org) found. AI search engines rely heavily on structured data to understand and cite content. Without it, your pages are much less likely to appear in AI-generated answers.
  Войдите, чтобы увидеть как исправить
• 06
  WARN · ai-readiness

  Knowledge Panel Readiness

  Partial knowledge-panel readiness — score 50/100. Missing components: Organization JSON-LD with ≥5 sameAs anchors, visible NAP (name/address/phone). Each missing piece reduces the chance of appearing in Google Knowledge Panel and AI-search citation anchors.
  Войдите, чтобы увидеть как исправить
• 07
  FAIL · performance

  Page Size

  The total HTML page size is 691.5 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 1103 ms (1.10 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.
  Войдите, чтобы увидеть как исправить
• 09
  FAIL · performance

  Image Lazy Loading

  Only 34 out of 77 images (44%) 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.
  Войдите, чтобы увидеть как исправить