cleantobe.md

Es werden die wichtigsten 10 Probleme angezeigt. Das vollständige Audit mit Korrekturen auf Code-Ebene ist im kostenlosen Plan verfügbar.

• 01
  FAIL · technical

  Internal link health

  2/10 sampled internal links failed: 0 4xx, 0 5xx, 0 broken redirects, 2 timeouts, 0 errors.
  Registrieren Sie sich, um zu sehen, wie sich das beheben lässt
• 02
  FAIL · content

  Keyword Cannibalization

  3 pairs of pages compete for overlapping keywords. Google will pick ONE to rank for each query, suppressing the rest. Highest-similarity pair: "Cleaning Services in Chisinau | CLEANTOBE Cleanin…" ↔ "Warehouse Cleaning Services in Chisinau | CLEANTO…" (67%).
  Registrieren Sie sich, um zu sehen, wie sich das beheben lässt
• 03
  FAIL · security

  Security Headers Grade (Mozilla Observatory)

  Security grade D- (40/100 baseline, Mozilla Observatory rubric). Top issues: Content-Security-Policy header missing (-25); X-Frame-Options + CSP frame-ancestors both missing (-20); X-Content-Type-Options: nosniff missing (-5)
  Registrieren Sie sich, um zu sehen, wie sich das beheben lässt
• 04
  FAIL · performance

  Page Size

  The total HTML page size is 1.46 MB, 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.
  Registrieren Sie sich, um zu sehen, wie sich das beheben lässt
• 05
  FAIL · ai-readiness

  AI Bot Live Accessibility Test

  Your site is visible to all 4 of 13 AI engines tested. (9 probes errored.)
  Registrieren Sie sich, um zu sehen, wie sich das beheben lässt
• 06
  FAIL · performance

  Browser Caching

  Only 1 out of 4 caching headers found (Cache-Control). Missing: Expires, ETag, Last-Modified. Caching is virtually unconfigured, causing resources to be reloaded on every visit.
  Registrieren Sie sich, um zu sehen, wie sich das beheben lässt
• 07
  WARN · performance

  Time to First Byte (TTFB)

  Time to First Byte is 1271 ms (1.27 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.
  Registrieren Sie sich, um zu sehen, wie sich das beheben lässt
• 08
  FAIL · performance

  HTTP Requests Count

  The page loads 77 external resources — this is too many (4 CSS, 23 JS, 45 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.
  Registrieren Sie sich, um zu sehen, wie sich das beheben lässt
• 09
  FAIL · security

  Security Headers

  Only 1 out of 6 modern security headers found. Missing: x-frame-options, x-content-type-options, content-security-policy, referrer-policy, permissions-policy. The site is exposed to XSS (no CSP), clickjacking (no X-Frame-Options / CSP frame-ancestors), MIME-sniffing (no X-Content-Type-Options), and HTTPS-stripping MITM (no HSTS). Mozilla Observatory grades sites with <4 headers as D or F.
  Registrieren Sie sich, um zu sehen, wie sich das beheben lässt
• 10
  WARN · ai-readiness

  Knowledge Panel Readiness

  Partial knowledge-panel readiness — score 50/100. Missing components: Wikidata Q-number, Organization JSON-LD with ≥5 sameAs anchors. Each missing piece reduces the chance of appearing in Google Knowledge Panel and AI-search citation anchors.
  Registrieren Sie sich, um zu sehen, wie sich das beheben lässt