sallykuter.com

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

• 01
  FAIL · security

  Security Headers

  Only 0 out of 6 modern security headers found. Missing: x-frame-options, x-content-type-options, strict-transport-security, 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.
  Войдите, чтобы увидеть как исправить
• 02
  WARN · ai-readiness

  Structured Data Completeness

  Only 2 schema types found (FAQPage, Person). AI search engines benefit from richer structured data to accurately cite your content. Aim for 3+ distinct types.
  Войдите, чтобы увидеть как исправить
• 03
  FAIL · security

  Security Headers Grade (Mozilla Observatory)

  Security grade F (25/100 baseline, Mozilla Observatory rubric). Top issues: Content-Security-Policy header missing (-25); Strict-Transport-Security missing (-20); X-Frame-Options + CSP frame-ancestors both missing (-20)
  Войдите, чтобы увидеть как исправить
• 04
  FAIL · ai-readiness

  Knowledge Panel Readiness

  Low knowledge-panel readiness — score 25/100. AI search engines and Google Knowledge Panel cannot confidently identify this brand. The cheapest, fastest fixes are: (1) add Organization JSON-LD with a sameAs chain (Wikipedia, Wikidata, LinkedIn, Crunchbase, GitHub, social), (2) make NAP (Name/Address/Phone) visible in the footer or contact page, (3) create a Wikidata entry (low notability bar), then (4) pursue Wikipedia once notability is established.
  Войдите, чтобы увидеть как исправить
• 05
  WARN · onpage

  Meta Description

  The meta description is long (178 chars). Google + Bing truncate around 155–160 chars on desktop and ~120 chars on mobile — anything past that is invisible in classic SERPs (though ChatGPT / Claude / Perplexity may still cite the full text). Trailing text often contains the CTA, which gets cut off.
  Войдите, чтобы увидеть как исправить
• 06
  FAIL · technical

  HTTP Redirects

  HTTP-to-HTTPS redirect is not configured. Users accessing the site via the insecure protocol (http://) are not being redirected to the HTTPS version. 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.
  Войдите, чтобы увидеть как исправить
• 07
  FAIL · technical

  WWW Canonicalization

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

  Browser Caching

  Only 1 out of 4 caching headers found (Last-Modified). Missing: Cache-Control, Expires, ETag. Caching is virtually unconfigured, causing resources to be reloaded on every visit.
  Войдите, чтобы увидеть как исправить
• 09
  WARN · performance

  Time to First Byte (TTFB)

  Time to First Byte is 1082 ms (1.08 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.
  Войдите, чтобы увидеть как исправить