fragrantica.com

Readiness by lane

Green: fragrantica.com. Thin bar: Ratings & Reviews peer median.

Priority fixes for fragrantica.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 24 days, short of the 30-day benchmark.

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   64% of Ratings & Reviews peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   72% of Ratings & Reviews peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   31% of Ratings & Reviews peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for fragrantica.com was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   37% of Ratings & Reviews peers do this.

   Guide: A Practical Website Health Check for Owners

What fragrantica.com already does well

Practices fewer than half of Ratings & Reviews peers use.

• Modern image formats in useWebP or AVIF images detected.37% of peers
• HTTP/3 advertisedHTTP/3 advertised.40% of peers
• Reachable over IPv6IPv6 address published.41% of peers

What we saw

Homepage checked

https://www.fragrantica.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoDaddy, 198-day validity, expiring 2026-11-11

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=none

Homepage HTML

752 KB, br

Images on homepage

273 (jpg 782, avif 238, webp 238, png 11, svg 2)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Ratings & Reviews sites

• appsmais.com62
• ekiten.jp62
• moviepilot.de64
• parfumo.com62
• parfumo.de62

Ratings & Reviews readiness benchmark