STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

friendquiz.me

friendquiz.me's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.

Readiness index
48/100

Web Tools median 67

Ahead of
6.1%

of measured Web Tools sites

Practices observed
11/26

5 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:29:44 UTC from one location. How we measure

Readiness by lane

Green: friendquiz.me. Thin bar: Web Tools peer median.

Enable

71/100

Peers 84

Harden

33/100

Peers 55

Accelerate

54/100

Peers 69

Recover

0/100

Peers 6

Priority fixes for friendquiz.me

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

  1. Priority 1 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

    Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

    What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

    92% of Web Tools peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  2. Priority 2 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    73% of Web Tools peers do this.

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

    30% of Web Tools peers do this.

  4. Priority 4 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.friendquiz.me.

    What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

    23% of Web Tools peers do this.

What we saw

Homepage checked
https://friendquiz.me/
Homepage response
HTTP 200
TLS
TLSv1.3, http/1.1
Certificate
Let's Encrypt, 89-day validity, expiring 2026-12-01
DNS operators
1 self-run or other nameserver domain
Homepage HTML
8 KB, gzip
Images on homepage
0

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 11

  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • HTML compressed
  • No render-blocking scripts in <head>
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Not measured 5

  • HTTP requests move to HTTPS
  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • robots.txt published

Own friendquiz.me?

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: friendquiz.me. This profile covers configuration only.

Compare with other Web Tools sites