Website readiness profile · Snapshot 23 October 2026
huggingface.co
huggingface.co's public homepage, certificate and DNS checked against 31 practices and compared with 231 Programming & Software sites.
- Readiness index
- 78/100
- Ahead of
- 81%
- Practices observed
- 22/31
- Popularity band
- Top 5K
Programming & Software median 68
of measured Programming & Software sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: huggingface.co. Thin bar: Programming & Software peer median.
Enable
85/100
Peers 81
Harden
69/100
Peers 59
Accelerate
90/100
Peers 65
Recover
0/100
Peers 7
Priority fixes for huggingface.co
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for huggingface.co was p=none, which asks receivers to take no action on failing mail.
Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.
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.
45% of Programming & Software peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.
Priority 2 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 28 images and none used loading="lazy".
What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.
56% of Programming & Software peers do this.
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.
90% of Programming & Software peers do this.
Priority 4 · 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.
73% of Programming & Software peers do this.
What huggingface.co already does well
Practices fewer than half of Programming & Software peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.12% of peers
- security.txt publishedsecurity.txt with a contact found.15% of peers
- Referrer-Policy setReferrer-Policy present.24% of peers
What we saw
- Homepage checked
- https://huggingface.co/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-02-27
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days
- DMARC policy
- p=none
- Homepage HTML
- 178 KB, gzip
- Images on homepage
- 28 (svg 17, png 8, webp 3)
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 9
Observed 22
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DNSSEC signed
- security.txt published
- Framing restricted
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- At most one redirect to the homepage
Own huggingface.co?
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: huggingface.co. This profile covers configuration only.