STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

encount.press

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

Readiness index
49/100

News & Media median 68

Ahead of
4.5%

of measured News & Media sites

Practices observed
12/31

0 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 11:52:08 UTC from one location. How we measure

Readiness by lane

Green: encount.press. Thin bar: News & Media peer median.

Enable

79/100

Peers 89

Harden

38/100

Peers 56

Accelerate

38/100

Peers 68

Recover

0/100

Peers 11

Priority fixes for encount.press

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

  1. Priority 1 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

    Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

    What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

    On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

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

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

    On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

    35% of News & Media peers do this.

  3. Priority 3 · Accelerate

    Modern image formats in use

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

    44% of News & Media peers do this.

  4. Priority 4 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.encount.press.

    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.

    37% of News & Media peers do this.

What we saw

Homepage checked
https://encount.press/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 197-day validity, expiring 2027-02-08
CDN or edge
Amazon CloudFront
Platform or framework
WordPress
DNS operators
Amazon Route 53
Homepage HTML
51 KB, gzip
Images on homepage
47 (jpg 35, svg 10, png 2)

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 encount.press?

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: encount.press. This profile covers configuration only.

Compare with other News & Media sites