cekresi.com

Readiness by lane

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

Priority fixes for cekresi.com

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

1. Priority 1 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from Sectigo Limited was due to expire on 2026-10-24 (1 days after the check).

   Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

   98% of Postage & Courier Services peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

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.

   39% of Postage & Courier Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 7 days, 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.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   39% of Postage & Courier Services peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What cekresi.com already does well

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

• HTTP/3 advertisedHTTP/3 advertised.22% of peers
• Modern image formats in useWebP or AVIF images detected.31% of peers
• Content Security Policy presentContent-Security-Policy present.31% of peers

What we saw

Homepage checked

https://cekresi.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Sectigo, 198-day validity, expiring 2026-10-24

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

56 KB, gzip

Images on homepage

16 (png 5, webp 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

Compare with other Postage & Courier Services sites

• bosta.co58
• delhivery.com58
• kuronekoyamato.co.jp58
• novaposhta.ua60
• vintedgo.com60

Postage & Courier Services readiness benchmark