Website readiness profile · Snapshot 23 October 2026
cloudinary.com
cloudinary.com's public homepage, certificate and DNS checked against 31 practices and compared with 40 Web Hosting & Infrastructure sites.
- Readiness index
- 79/100
- Ahead of
- 65%
- Practices observed
- 22/31
- Popularity band
- Top 50K
Web Hosting & Infrastructure median 74
of measured Web Hosting & Infrastructure sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: cloudinary.com. Thin bar: Web Hosting & Infrastructure peer median.
Enable
95/100
Peers 83
Harden
66/100
Peers 67
Accelerate
88/100
Peers 70
Recover
0/100
Peers 18
Priority fixes for cloudinary.com
Ordered by impact and by how common each practice is among peers.
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.
53% of Web Hosting & Infrastructure peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
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 WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.
50% of Web Hosting & Infrastructure peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 3 · Harden
security.txt published
Observed: No valid /.well-known/security.txt with a Contact field was returned.
What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.
37% of Web Hosting & Infrastructure peers do this.
Priority 4 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from GoDaddy.com, Inc. had a 198-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.
60% of Web Hosting & Infrastructure peers do this.
What cloudinary.com already does well
Practices fewer than half of Web Hosting & Infrastructure peers use.
- HTTP/3 advertisedHTTP/3 advertised.33% of peers
- CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, amazontrust.com and others.43% of peers
What we saw
- Homepage checked
- https://cloudinary.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- GoDaddy, 198-day validity, expiring 2026-12-02
- CDN or edge
- Cloudflare, WordPress VIP
- Platform or framework
- WordPress
- DNS operators
- Amazon Route 53
- DMARC policy
- p=quarantine
- Homepage HTML
- 366 KB, br
- Images on homepage
- 138 (png 150, svg 31, jpg 5)
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
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- CAA records limit who can issue certificates
- DMARC policy enforces quarantine or reject
- 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 cloudinary.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: cloudinary.com. This profile covers configuration only.