STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

netlify.com

netlify.com's public homepage, certificate and DNS checked against 31 practices and compared with 40 Web Hosting & Infrastructure sites.

Readiness index
70/100

Web Hosting & Infrastructure median 74

Ahead of
33%

of measured Web Hosting & Infrastructure sites

Practices observed
20/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:01:19 UTC from one location. How we measure

Readiness by lane

Green: netlify.com. Thin bar: Web Hosting & Infrastructure peer median.

Enable

100/100

Peers 83

Harden

65/100

Peers 67

Accelerate

48/100

Peers 70

Recover

100/100

Peers 18

Priority fixes for netlify.com

Ordered by impact and by how common each practice is among peers.

  1. Priority 1 · Accelerate

    Modern image formats in use

    Observed: The homepage had 23 images and none used WebP or AVIF.

    Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

    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.

    65% of Web Hosting & Infrastructure peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

  2. Priority 2 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for 0 seconds, short of the 30-day benchmark.

    What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

    65% of Web Hosting & Infrastructure peers do this.

  3. Priority 3 · Accelerate

    No render-blocking scripts in <head>

    Observed: The homepage <head> loaded 2 external scripts 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.

    50% of Web Hosting & Infrastructure peers do this.

  4. Priority 4 · 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.

    68% of Web Hosting & Infrastructure peers do this.

What netlify.com already does well

Practices fewer than half of Web Hosting & Infrastructure peers use.

  • Nameservers spread across providersNameservers spread across more than one operator.18% of peers
  • CAA records limit who can issue certificatesCAA limits issuance to amazon.com, digicert.com.43% of peers
  • Reachable over IPv6IPv6 address published.43% of peers

What we saw

Homepage checked
https://www.netlify.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
DigiCert, 364-day validity, expiring 2027-02-05
CDN or edge
Netlify
Platform or framework
Astro
DNS operators
NS1, plus 1 self-run or other nameserver domain
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
401 KB, br
Images on homepage
23 (svg 23)

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

Observed 20

  • 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
  • DMARC policy enforces quarantine or reject
  • HTTP/2 negotiated
  • HTML compressed
  • Offscreen images lazy-loaded
  • 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
  • Nameservers spread across providers

Own netlify.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: netlify.com. This profile covers configuration only.

Compare with other Web Hosting & Infrastructure sites