STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

fardayetaze.ir

fardayetaze.ir's public homepage, certificate and DNS checked against 31 practices and compared with 306 Online Publishing sites.

Readiness index
77/100

Online Publishing median 64

Ahead of
90%

of measured Online Publishing sites

Practices observed
23/31

0 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

Measured 2026-10-23 11:39:50 UTC from one location. How we measure

Readiness by lane

Green: fardayetaze.ir. Thin bar: Online Publishing peer median.

Enable

87/100

Peers 84

Harden

69/100

Peers 51

Accelerate

85/100

Peers 65

Recover

0/100

Peers 5

Priority fixes for fardayetaze.ir

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 60 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.

    27% of Online Publishing 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 65 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 WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.

    38% of Online Publishing peers do this.

  3. Priority 3 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.fardayetaze.ir.

    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.

    20% of Online Publishing peers do this.

  4. Priority 4 · Enable

    Social preview image set

    Observed: The homepage had no og:image, so shared links may show without a preview image.

    What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

    67% of Online Publishing peers do this.

What fardayetaze.ir already does well

Practices fewer than half of Online Publishing peers use.

  • security.txt publishedsecurity.txt with a contact found.1.3% of peers
  • Content Security Policy presentContent-Security-Policy present.18% of peers
  • Referrer-Policy setReferrer-Policy present.20% of peers

What we saw

Homepage checked
https://www.fardayetaze.ir/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Let's Encrypt, 89-day validity, expiring 2027-01-04
Platform or framework
WordPress
DNS operators
1 self-run or other nameserver domain
HSTS
max-age 60 days, includeSubDomains, preload
Homepage HTML
275 KB, br
Images on homepage
65

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 23

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • security.txt published
  • 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
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Page language declared
  • At most one redirect to the homepage

Own fardayetaze.ir?

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: fardayetaze.ir. This profile covers configuration only.

Compare with other Online Publishing sites