jds.fr

Readiness by lane

Green: jds.fr. Thin bar: Events & Online Ticketing peer median.

Priority fixes for jds.fr

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

1. Priority 1 · Enable

   Mobile viewport configured

   Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

   Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

   What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

   97% of Events & Online Ticketing peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Responsive Web Design Checklist for Real Devices

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for jds.fr 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.

   44% of Events & Online Ticketing peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   24% of Events & Online Ticketing peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for jds.fr, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   11% of Events & Online Ticketing peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What jds.fr already does well

Practices fewer than half of Events & Online Ticketing peers use.

• Content Security Policy presentContent-Security-Policy present.30% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.35% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.42% of peers

What we saw

Homepage checked

https://www.jds.fr/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-03

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

230 KB, gzip

Images on homepage

103 (webp 99, svg 4)

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 Events & Online Ticketing sites

• eventbrite.com77
• eventbrite.it77
• gsc.com.my77
• vide-greniers.org77
• vividseats.com77

Events & Online Ticketing readiness benchmark