cohere.com

Mostrando os 10 principais problemas. Auditoria completa com correções no nível do código disponível no plano grátis.

• 01
  FAIL · performance

  Time to First Byte (TTFB)

  Time to First Byte is 3657 ms (3.66 sec) — Google flags this as "poor" (> 1.8 s per web.dev/articles/ttfb). The browser cannot begin rendering until the first byte arrives, so LCP cannot beat 3.66s. Every downstream Core Web Vital (LCP, INP, CLS) inherits this delay, and Page Experience signals trigger a soft demotion in Google + Bing rankings.
  Cadastre-se para ver como corrigir isto
• 02
  FAIL · technical

  Internal link health

  7/10 sampled internal links failed: 0 4xx, 0 5xx, 0 broken redirects, 7 timeouts, 0 errors.
  Cadastre-se para ver como corrigir isto
• 03
  FAIL · performance

  Page Size

  The total HTML page size is 663.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.
  Cadastre-se para ver como corrigir isto
• 04
  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.
  Cadastre-se para ver como corrigir isto
• 05
  FAIL · performance

  Render-Blocking Resources

  Found 8 render-blocking resources (7 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).
  Cadastre-se para ver como corrigir isto
• 06
  FAIL · performance

  HTTP Requests Count

  The page loads 352 external resources — this is too many (7 CSS, 52 JS, 269 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.
  Cadastre-se para ver como corrigir isto
• 07
  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.
  Cadastre-se para ver como corrigir isto
• 08
  FAIL · security

  Security Headers

  Only 3 out of 6 modern security headers found. Missing: 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.
  Cadastre-se para ver como corrigir isto
• 09
  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". This is a significant security risk — attackers gain information about the technology stack for targeted attacks.
  Cadastre-se para ver como corrigir isto
• 10
  WARN · ai-readiness

  Structured Data Completeness

  Only 1 schema type found (Organization). AI search engines benefit from richer structured data to accurately cite your content. Aim for 3+ distinct types.
  Cadastre-se para ver como corrigir isto