calendarr.com

Readiness by lane

Green: calendarr.com. Thin bar: Web Tools peer median.

Priority fixes for calendarr.com

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   69% of Web Tools peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Control Third-Party Scripts Before They Control Your Page

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

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

   23% of Web Tools peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Enable

   Page language declared

   Observed: The homepage <html> element had no lang attribute.

   What to do: Set lang on the html element (for example lang="en") and on any sections in another language.

   94% of Web Tools peers do this.

   Guide: Website Accessibility Checklist for Owners

4. Priority 4 · 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.

   56% of Web Tools peers do this.

   Guide: CDN Guide for Website Owners

What calendarr.com already does well

Practices fewer than half of Web Tools peers use.

• HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.30% of peers
• X-Content-Type-Options: nosniffnosniff header present.44% of peers
• Framing restrictedFraming controls present.48% of peers

What we saw

Homepage checked

https://www.calendarr.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-06

DNS operators

Amazon Route 53

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

279 KB, gzip

Images on homepage

2 (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 Web Tools sites

• callbomber.in71
• cuttty.com71
• storiesig.info72
• vidgap.com72
• wheelofnames.com72

Web Tools readiness benchmark