flety.io

Readiness by lane

Green: flety.io. Thin bar: Postage & Courier Services peer median.

Priority fixes for flety.io

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.flety.io.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   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.

   52% of Postage & Courier Services peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

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

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

3. Priority 3 · Accelerate

   Modern image formats in use

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

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.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   39% of Postage & Courier Services peers do this.

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

What flety.io already does well

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

• HTTP/3 advertisedHTTP/3 advertised.22% of peers
• Referrer-Policy setReferrer-Policy present.28% of peers
• Reachable over IPv6IPv6 address published.31% of peers

What we saw

Homepage checked

https://flety.io/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-11-24

CDN or edge

Cloudflare, Netlify

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 365 days

Homepage HTML

23 KB, br

Images on homepage

5

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

• 17track.net73
• lalamove.com73
• lbcexpress.com74
• one-line.com73
• usps.com74

Postage & Courier Services readiness benchmark