blackpyramidstours.com

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

• 01
  WARN · onpage

  Meta Description

  The meta description is long (162 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
• 02
  FAIL · onpage

  Image Alt Attributes

  8 out of 18 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
• 03
  FAIL · performance

  HTTP Requests Count

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

  Security Headers

  Found 5 out of 6 modern security headers. Missing: content-security-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.
  Inscrivez-vous pour voir comment corriger ceci
• 05
  WARN · ai-readiness

  Structured Data Completeness

  Only 1 schema type found (TravelAgency). AI search engines benefit from richer structured data to accurately cite your content. Aim for 3+ distinct types.
  Inscrivez-vous pour voir comment corriger ceci
• 06
  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.
  Inscrivez-vous pour voir comment corriger ceci