Website readiness profile · Snapshot 23 October 2026
figma.com
figma.com's public homepage, certificate and DNS checked against 31 practices and compared with 356 Design & Content Creation sites.
- Readiness index
- 88/100
- Ahead of
- 99%
- Practices observed
- 25/31
- Popularity band
- Top 5K
Design & Content Creation median 69
of measured Design & Content Creation sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: figma.com. Thin bar: Design & Content Creation peer median.
Enable
95/100
Peers 86
Harden
88/100
Peers 57
Accelerate
88/100
Peers 71
Recover
0/100
Peers 3
Priority fixes for figma.com
Ordered by impact and by how common each practice is among peers.
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
Priority 2 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
72% of Design & Content Creation peers do this.
Priority 3 · Enable
Reachable over IPv6
Observed: No IPv6 (AAAA) address was published for www.figma.com.
What to do: Enable IPv6 at your CDN or host and publish the AAAA record it provides.
54% of Design & Content Creation peers do this.
Priority 4 · Harden
DNSSEC signed
Observed: No DS record was found for figma.com at its parent zone, so its DNS answers are not DNSSEC-signed.
What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
On Amazon Route 53: Enable DNSSEC signing for the hosted zone and establish the chain of trust at the registrar.
8.2% of Design & Content Creation peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
What figma.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 amazonaws.com, letsencrypt.org, pki.goog.17% of peers
- Content Security Policy presentContent-Security-Policy present.29% of peers
What we saw
- Homepage checked
- https://www.figma.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-02-03
- CDN or edge
- Amazon CloudFront, Netlify
- Platform or framework
- Next.js
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=quarantine
- Homepage HTML
- 1,749 KB, br
- Images on homepage
- 88 (png 76, svg 52, jpg 6)
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
Not observed 6
Observed 25
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- CAA records limit who can issue certificates
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own figma.com?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: figma.com. This profile covers configuration only.