Website readiness profile · Snapshot 23 October 2026
awwwards.com
awwwards.com's public homepage, certificate and DNS checked against 31 practices and compared with 356 Design & Content Creation sites.
- Readiness index
- 62/100
- Ahead of
- 26%
- Practices observed
- 19/31
- Popularity band
- Top 50K
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: awwwards.com. Thin bar: Design & Content Creation peer median.
Enable
100/100
Peers 86
Harden
49/100
Peers 57
Accelerate
48/100
Peers 71
Recover
0/100
Peers 3
Priority fixes for awwwards.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
93% of Design & Content Creation peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
94% of Design & Content Creation peers do this.
Priority 3 · Accelerate
Modern image formats in use
Observed: The homepage had 63 images and none used WebP or AVIF.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
56% of Design & Content Creation peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 4 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 30 days, below the one-year benchmark.
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.
37% of Design & Content Creation peers do this.
What awwwards.com already does well
Practices fewer than half of Design & Content Creation peers use.
- CAA records limit who can issue certificatesCAA limits issuance to godaddy.com, letsencrypt.org, sectigo.com.17% 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://www.awwwards.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2
- Certificate
- GoDaddy, 397-day validity, expiring 2027-02-06
- DNS operators
- DNS Made Easy
- HSTS
- max-age 30 days
- DMARC policy
- p=none
- Homepage HTML
- 329 KB, gzip
- Images on homepage
- 63 (jpg 22, png 7)
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 12
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate lifetime of 100 days or less
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- Content Security Policy present
- HTTP/2 negotiated
- HTTP/3 advertised
- Modern image formats in use
- Offscreen images lazy-loaded
- Nameservers spread across providers
Observed 19
- HTTP requests move to HTTPS
- Certificate has more than 14 days left
- CAA records limit who can issue certificates
- X-Content-Type-Options: nosniff
- Framing restricted
- Referrer-Policy set
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- 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 awwwards.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: awwwards.com. This profile covers configuration only.