STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

morningstar.com

morningstar.com's public homepage, certificate and DNS checked against 31 practices and compared with 233 Data & Analytics sites.

Readiness index
75/100

Data & Analytics median 63

Ahead of
80%

of measured Data & Analytics sites

Practices observed
22/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:43:40 UTC from one location. How we measure

Readiness by lane

Green: morningstar.com. Thin bar: Data & Analytics peer median.

Enable

77/100

Peers 78

Harden

68/100

Peers 56

Accelerate

85/100

Peers 63

Recover

100/100

Peers 8

Priority fixes for morningstar.com

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

  1. Priority 1 · Harden

    HSTS kept for at least a year

    Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

    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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

    34% of Data & Analytics peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Accelerate

    Modern image formats in use

    Observed: The homepage had 53 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.

    On Nuxt: Nuxt Image can output WebP and AVIF.

    31% of Data & Analytics peers do this.

  3. Priority 3 · Enable

    Canonical URL declared

    Observed: The homepage did not declare a canonical URL.

    What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

    65% of Data & Analytics peers do this.

  4. Priority 4 · Harden

    Certificate lifetime of 100 days or less

    Observed: The certificate from Amazon had a 394-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.

    65% of Data & Analytics peers do this.

What morningstar.com already does well

Practices fewer than half of Data & Analytics peers use.

  • Nameservers spread across providersNameservers spread across NS1 and Vercara UltraDNS.7.8% of peers
  • Content Security Policy presentContent-Security-Policy present.24% of peers
  • Referrer-Policy setReferrer-Policy present.33% of peers

What we saw

Homepage checked
https://www.morningstar.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 394-day validity, expiring 2027-01-17
CDN or edge
Amazon CloudFront
Platform or framework
Nuxt
DNS operators
NS1, Vercara UltraDNS
HSTS
max-age 0 days, includeSubDomains
DMARC policy
p=reject
Homepage HTML
817 KB, gzip
Images on homepage
53 (png 180, jpg 145, svg 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

Observed 22

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Static files cached for 30 days or more
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage
  • Nameservers spread across providers

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

Compare with other Data & Analytics sites