STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

jtexpress.com.br

jtexpress.com.br's public homepage, certificate and DNS checked against 31 practices and compared with 185 Postage & Courier Services sites.

Readiness index
44/100

Postage & Courier Services median 60

Ahead of
14%

of measured Postage & Courier Services sites

Practices observed
9/29

2 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:02:59 UTC from one location. How we measure

Readiness by lane

Green: jtexpress.com.br. Thin bar: Postage & Courier Services peer median.

Enable

26/100

Peers 75

Harden

54/100

Peers 56

Accelerate

50/100

Peers 53

Recover

0/100

Peers 12

Priority fixes for jtexpress.com.br

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

  1. Priority 1 · Enable

    robots.txt published

    Observed: No robots.txt file was returned at the site root.

    Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.

    What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

    81% of Postage & Courier Services peers do this. Limit: Only the standard location was requested, once, at the time of the check.

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

    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.

    39% of Postage & Courier Services peers do this.

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

    69% of Postage & Courier Services peers do this.

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

    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.

    44% of Postage & Courier Services peers do this.

What jtexpress.com.br already does well

Practices fewer than half of Postage & Courier Services peers use.

  • Framing restrictedFraming controls present.50% of peers

What we saw

Homepage checked
https://www.jtexpress.com.br/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
DigiCert, 183-day validity, expiring 2026-12-26
CDN or edge
Amazon CloudFront
DNS operators
Alibaba Cloud DNS
HSTS
max-age 60 days
DMARC policy
p=quarantine
Homepage HTML
3 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

Own jtexpress.com.br?

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

Compare with other Postage & Courier Services sites