STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

dietnavi.com

dietnavi.com's public homepage, certificate and DNS checked against 31 practices and compared with 343 Uncategorized sites.

Readiness index
38/100

Uncategorized median 62

Ahead of
3.5%

of measured Uncategorized sites

Practices observed
10/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:42:02 UTC from one location. How we measure

Readiness by lane

Green: dietnavi.com. Thin bar: Uncategorized peer median.

Enable

62/100

Peers 80

Harden

29/100

Peers 54

Accelerate

30/100

Peers 58

Recover

0/100

Peers 12

Priority fixes for dietnavi.com

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

  1. Priority 1 · Accelerate

    HTML compressed

    Observed: The homepage HTML (70 KB) was delivered without gzip, Brotli or zstd compression.

    Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

    What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

    92% of Uncategorized peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Enable

    Mobile viewport configured

    Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

    What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

    97% of Uncategorized peers do this.

  3. Priority 3 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

    90% of Uncategorized peers do this.

  4. Priority 4 · Harden

    HSTS kept for at least a year

    Observed: The homepage response did not include a Strict-Transport-Security header.

    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.

    34% of Uncategorized peers do this.

What dietnavi.com already does well

Practices fewer than half of Uncategorized peers use.

  • No render-blocking scripts in <head>Head scripts load without blocking.37% of peers

What we saw

Homepage checked
https://dietnavi.com/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.2, HTTP/2
Certificate
Amazon, 197-day validity, expiring 2027-02-03
DNS operators
Amazon Route 53
DMARC policy
p=none
Homepage HTML
70 KB, uncompressed
Images on homepage
64 (png 25, gif 18, jpg 8)

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

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

Compare with other Uncategorized sites