STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

f1jouhou2.com

f1jouhou2.com's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.

Readiness index
44/100

News & Media median 68

Ahead of
2%

of measured News & Media sites

Practices observed
12/29

2 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:46:25 UTC from one location. How we measure

Readiness by lane

Green: f1jouhou2.com. Thin bar: News & Media peer median.

Enable

69/100

Peers 89

Harden

40/100

Peers 56

Accelerate

24/100

Peers 68

Recover

n/a/100

Peers 11

Priority fixes for f1jouhou2.com

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

  1. Priority 1 · Enable

    Mobile viewport configured

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

    Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

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

    98% of News & Media 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

    HTTP/2 negotiated

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

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

    94% of News & Media 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.

    93% of News & Media 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.

    35% of News & Media peers do this.

What f1jouhou2.com already does well

Practices fewer than half of News & Media peers use.

  • Content Security Policy presentContent-Security-Policy present.29% of peers

What we saw

Homepage checked
https://f1jouhou2.com/
Homepage response
HTTP 200
TLS
TLSv1.2, http/1.1
Certificate
Let's Encrypt, 89-day validity, expiring 2027-01-11
Homepage HTML
179 KB, gzip
Images on homepage
276 (png 191, jpg 37, gif 12)

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 12

  • HTTP requests move to HTTPS
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • Content Security Policy present
  • HTML compressed
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Not measured 2

  • Static files cached for 30 days or more
  • Nameservers spread across providers

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

Compare with other News & Media sites