nzpost.co.nz

Readiness by lane

Green: nzpost.co.nz. Thin bar: Postage & Courier Services peer median.

Priority fixes for nzpost.co.nz

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.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 180 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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

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

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   44% of Postage & Courier Services peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 32 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 Cloudflare: Cloudflare Polish can convert images to WebP.

   31% of Postage & Courier Services peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

What nzpost.co.nz already does well

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

• Referrer-Policy setReferrer-Policy present.28% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.39% of peers
• Offscreen images lazy-loadedNative lazy loading in use.44% of peers

What we saw

Homepage checked

https://www.nzpost.co.nz/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2026-12-31

CDN or edge

Cloudflare, Acquia

Platform or framework

Drupal

DNS operators

Akamai Edge DNS

HSTS

max-age 180 days

DMARC policy

p=reject

Homepage HTML

209 KB, br

Images on homepage

32 (svg 15, png 14, jpg 3)

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

• correoargentino.com.ar62
• cttexpress.com62
• myhermes.de62
• postaonline.cz62
• shreemaruti.com62

Postage & Courier Services readiness benchmark