faymas.in

Readiness by lane

Green: faymas.in. Thin bar: Design & Content Creation peer median.

Priority fixes for faymas.in

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

1. Priority 1 · Harden

   HSTS kept for at least a year

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

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   37% of Design & Content Creation peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

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

   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.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   49% of Design & Content Creation peers do this.

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

3. Priority 3 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   29% of Design & Content Creation peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for faymas.in, 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.

   On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

   17% of Design & Content Creation peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What faymas.in already does well

Practices fewer than half of Design & Content Creation peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.8.2% of peers
• Referrer-Policy setReferrer-Policy present.26% of peers
• X-Content-Type-Options: nosniffnosniff header present.39% of peers

What we saw

Homepage checked

https://faymas.in/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-03

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Cloudflare

DMARC policy

p=quarantine

Homepage HTML

626 KB, br

Images on homepage

20 (webp 20)

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 Design & Content Creation sites

• desktophut.com83
• joliecarte.com82
• unlucid.ai82
• veed.io84
• whatfontis.com84

Design & Content Creation readiness benchmark