slack.com

Affichage des 10 principaux problèmes. Audit complet avec corrections au niveau du code disponible sur le forfait gratuit.

• 01
  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.
  Inscrivez-vous pour voir comment corriger ceci
• 02
  FAIL · ai-readiness

  AI Bot Live Accessibility Test

  Your site is visible to 7 of 13 AI engines. Blocked: ChatGPT-User, Claude-User, Perplexity-User, Google-Extended, Amazonbot, DuckAssistBot.
  Inscrivez-vous pour voir comment corriger ceci
• 03
  WARN · onpage

  Meta Description

  The meta description is long (173 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.
  Inscrivez-vous pour voir comment corriger ceci
• 04
  FAIL · performance

  Render-Blocking Resources

  Found 11 render-blocking resources (8 CSS, 3 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).
  Inscrivez-vous pour voir comment corriger ceci
• 05
  FAIL · onpage

  Image Alt Attributes

  37 out of 85 images are missing the alt attribute (only 56% have alt). A significant portion of images is inaccessible to search engines and users with disabilities.
  Inscrivez-vous pour voir comment corriger ceci
• 06
  FAIL · performance

  Browser Caching

  Caching headers are completely absent. Without Cache-Control, Expires, ETag, and Last-Modified, the browser will reload all resources on every visit, significantly increasing load time and consuming user bandwidth.
  Inscrivez-vous pour voir comment corriger ceci
• 07
  WARN · performance

  Time to First Byte (TTFB)

  Time to First Byte is 1470 ms (1.47 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.
  Inscrivez-vous pour voir comment corriger ceci
• 08
  FAIL · performance

  HTTP Requests Count

  The page loads 219 external resources — this is too many (8 CSS, 15 JS, 85 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.
  Inscrivez-vous pour voir comment corriger ceci
• 09
  FAIL · security

  Security Headers

  Only 3 out of 6 modern security headers found. Missing: x-content-type-options, content-security-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.
  Inscrivez-vous pour voir comment corriger ceci
• 10
  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.
  Inscrivez-vous pour voir comment corriger ceci