salesforce.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 3086 ms (3.09 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.09s. 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 · onpage

  Image Alt Attributes

  12 out of 35 images are missing the alt attribute (only 66% have alt). A significant portion of images is inaccessible to search engines and users with disabilities.
  Cadastre-se para ver como corrigir isto
• 03
  FAIL · performance

  HTTP Requests Count

  The page loads 64 external resources — this is too many (2 CSS, 20 JS, 35 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
• 04
  WARN · security

  Security Headers

  Found 4 out of 6 modern security headers. Missing: content-security-policy, 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.
  Cadastre-se para ver como corrigir isto
• 05
  FAIL · content

  Keyword Stuffing

  Keyword stuffing detected. The following words appear excessively often: "und" — 41 times (5.2%), "sie" — 32 times (4%). The acceptable keyword density is 1-2%. Exceeding the 3% threshold may result in search engine penalties.
  Cadastre-se para ver como corrigir isto
• 06
  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
• 07
  FAIL · ai-readiness

  AI Bot Live Accessibility Test

  Your site is visible to 0 of 13 AI engines. Blocked: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended, Amazonbot, DuckAssistBot, Meta-ExternalAgent.
  Cadastre-se para ver como corrigir isto
• 08
  WARN · technical

  Indexability

  Canonicalized to another URL — <link rel="canonical"> points to a different URL: https://www.salesforce.com/de/. Search engines will index that URL, not this one.
  Cadastre-se para ver como corrigir isto
• 09
  FAIL · performance

  Scripts Inventory

  Inventoried 30 <script> elements (10 inline, 14 third-party). 4 third-party scripts block(s) initial render (no async/defer). Approx 231 KB of third-party JavaScript measured. No third-party scripts use Subresource Integrity (SRI) hashes.
  Cadastre-se para ver como corrigir isto
• 10
  WARN · onpage

  Meta Title

  The <title> tag is long (70 chars). Google has no hard character limit, but SERPs truncate by pixel width (~600px on desktop, ~78px less on mobile). Wide letters (W, M, capitals) push the cutoff lower — 30–65 chars is the safe zone across Google + Bing + Yandex. Beyond ~70 chars, the tail keyword is invisible in classic SERPs (still cited fully by ChatGPT / Claude / Perplexity).
  Cadastre-se para ver como corrigir isto