Website readiness profile · Snapshot 23 October 2026
microsoft.com
microsoft.com's public homepage, certificate and DNS checked against 31 practices and compared with 231 Programming & Software sites.
- Readiness index
- 69/100
- Ahead of
- 52%
- Practices observed
- 19/31
- Popularity band
- Top 1K
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: microsoft.com. Thin bar: Programming & Software peer median.
Enable
92/100
Peers 81
Harden
71/100
Peers 59
Accelerate
48/100
Peers 65
Recover
0/100
Peers 7
Priority fixes for microsoft.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 26 days, short of the 30-day benchmark.
Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.
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.
50% of Programming & Software peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Accelerate
Modern image formats in use
Observed: The homepage had 41 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.
42% of Programming & Software peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 3 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 6 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.
51% of Programming & Software peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
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.
47% of Programming & Software peers do this.
What microsoft.com already does well
Practices fewer than half of Programming & Software peers use.
- security.txt publishedsecurity.txt with a contact found.15% of peers
- CAA records limit who can issue certificatesCAA record present.23% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.40% of peers
What we saw
- Homepage checked
- https://www.microsoft.com/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Microsoft Corporation, 360-day validity, expiring 2027-01-17
- CDN or edge
- Azure Front Door/CDN
- Platform or framework
- Adobe Experience Manager
- DNS operators
- Azure DNS
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 277 KB, gzip
- Images on homepage
- 41 (png 1)
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
- Certificate lifetime of 100 days or less
- DNSSEC signed
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- No render-blocking scripts in <head>
- Social preview image set
- Nameservers spread across providers
Observed 19
- 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
- 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
- Page language declared
- At most one redirect to the homepage
Own microsoft.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: microsoft.com. This profile covers configuration only.