heygen.com

Readiness by lane

Green: heygen.com. Thin bar: Design & Content Creation peer median.

Priority fixes for heygen.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.

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

   49% of Design & Content Creation 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

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Cloudflare: Add the header with a response header transform rule.

   48% of Design & Content Creation peers do this.

   Guide: A Practical Website Health Check for Owners

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

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   On Cloudflare: Add the header with a response header transform rule.

   39% of Design & Content Creation peers do this.

   Guide: A Practical Website Health Check for Owners

What heygen.com already does well

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

• security.txt publishedsecurity.txt with a contact found.9.1% of peers
• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, amazontrust.com and others.17% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age.37% of peers

What we saw

Homepage checked

https://www.heygen.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-09

CDN or edge

Cloudflare, Vercel

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 730 days

DMARC policy

p=reject

Homepage HTML

452 KB, gzip

Images on homepage

109 (svg 65, jpg 4, png 1)

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

• 1001fonts.com84
• fish.audio84
• magichour.ai86
• novelai.net84
• pixelbin.io84

Design & Content Creation readiness benchmark