SEOWebsiteTool
82Grade B

kamorel.com

L'élégance d'un parfum, l'émotion d'une signature.

1 failed · 7 warnings · 21 passed

Audited Sat, 11 Jul 2026 20:52:06 GMT · https://kamorel.com/

Meta & Head

19.4/25

Title, description, canonical, social tags — what search engines read first.

  • Meta descriptionhigh impactlow effort

    Meta description is "Découvrez KAMOREL, votre boutique spécialisée dans les parfums d'inspiration pour homme et femme. Des fragrances inspirées des plus grands classiques, offrant une excellente tenue, une qualité premium et une expérience olfactive exceptionnelle. Livraison rapide en 24 à 48h partout au Maroc avec paiement à la livraison." (325 characters)

    Search engines truncate descriptions past roughly 160 characters, and very short ones waste the snippet space that persuades searchers to pick your listing over the next one. Rewrite it to 70–160 characters: state what the page offers, work the primary keyword in naturally (matching words get bolded in results), and end with a benefit or call to action. Don't cram in keywords — the description influences clicks, not rankings, so write it for humans.

  • Canonical URLmedium impactlow effort

    No <link rel="canonical"> found

    When the same page is reachable at several URLs — tracking parameters, trailing-slash variants, http vs https — search engines may split ranking signals across the duplicates. A canonical tag names the one version that should get all the credit. Add <link rel="canonical" href="https://www.example.com/page/"> to the <head>, pointing at the page's preferred absolute URL. Double-check it's self-referencing on the primary version: a canonical that points at the wrong page can quietly de-index the right one.

  • Open Graph tagsmedium impactlow effort

    Missing Open Graph tags: og:url

    Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:url tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.

  • Twitter card taglow impactlow effort

    No twitter:card meta tag found

    X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.

5 passing checks
  • Title tag<title> is "L'élégance d'un parfum, l'émotion d'une signature." (50 characters)
  • Viewport meta tagViewport is "width=device-width, initial-scale=1"
  • Character encoding declaredCharacter encoding is declared
  • FaviconA <link rel="icon"> is present
  • Page allows indexingNo restrictive robots meta tag

Content & Structure

20.3/25

Headings, copy depth, images, structured data, internal linking.

  • Single H1 headinghigh impactlow effort

    0 h1 headings found

    The h1 is the visible headline of the page and one of the clearest signals to search engines of what it's about; with none present, engines lean on surrounding text and may misread the topic. Add exactly one h1 near the top that states the main topic in plain language and includes the primary keyword, e.g. <h1>Merge PDF Files Online</h1>. Don't fake it with a styled <div> — the semantic tag itself is what crawlers and screen readers actually read.

7 passing checks
  • Heading hierarchy22 headings in order without skipped levels
  • Word count6610 words of visible text
  • Image alt text24 of 24 images have alt text
  • Structured data (JSON-LD)JSON-LD types found: WebPage
  • HTML lang attribute<html lang="fr">
  • JavaScript-dependent contentvisible text ~9955 chars in the initial HTML
  • Internal linking42 internal, 2 external links

Technical

21.6/25

HTTPS, redirects, robots, sitemap, speed, crawlability.

  • Fast time to first bytehigh impactmedium effort

    1056 ms

    Time to first byte is the floor under every other speed metric — the browser can't parse, render, or fetch anything until the first byte arrives, so a slow TTFB drags down all Core Web Vitals and tests crawlers' patience. Add caching in front of the origin: full-page caching at a CDN (Cloudflare, Fastly) helps most, followed by server-side caches (Redis, object caching) and indexes on slow database queries. Measure from locations near your actual users — tuning only your fastest region leaves distant visitors just as slow.

  • XML sitemap availablemedium impactlow effort

    sitemap.xml is valid but robots.txt does not reference it

    Your sitemap is valid, but robots.txt never mentions it, so crawlers you haven't manually notified may never find it — the robots.txt reference is the universal discovery mechanism. Add one line to robots.txt: "Sitemap: https://www.example.com/sitemap.xml", using the full absolute URL (a relative path is invalid here). The line can go anywhere in the file, and you can list several sitemaps. Also submit it in Google Search Console to get indexing-coverage reporting on top of discovery.

  • Response compression enabledlow impactlow effort

    no content-encoding header

    This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.

9 passing checks
  • Served over HTTPSfinal URL uses https://
  • HTTP redirects to HTTPShttp:// redirects to https://
  • No mixed content0 http:// subresource references
  • Short redirect chainno redirects; URL resolves directly
  • robots.txt present and permissiverobots.txt exists and allows crawling
  • Reasonable HTML size455.4 KB
  • Missing pages return 404missing paths return HTTP 404/410
  • www and non-www resolve consistentlywww and non-www converge on the same host
  • HTML5 doctype<!DOCTYPE html> present

Performance

Core Web Vitals scoring via Google PageSpeed is coming soon.

Share your score

Embed this live badge on your site — it updates whenever the audit is re-run.

SEO score badge for kamorel.com

More “k” sitesRecent audits