correos.es

Readiness by lane

Green: correos.es. Thin bar: Postage & Courier Services peer median.

Priority fixes for correos.es

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 1 hours, 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.

   44% of Postage & Courier Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

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

   31% of Postage & Courier Services peers do this.

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

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 4 external scripts 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

4. Priority 4 · Enable

   At most one redirect to the homepage

   Observed: The homepage was reached after 2 redirects.

   What to do: Point every alternate address (http, www or apex, old paths) straight to the final URL in a single redirect.

   96% of Postage & Courier Services peers do this.

   Guide: Technical SEO Audit: A Practical Owner’s Guide

What correos.es already does well

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

• Referrer-Policy setReferrer-Policy present.28% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.39% of peers
• X-Content-Type-Options: nosniffnosniff header present.45% of peers

What we saw

Homepage checked

https://www.correos.es/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-04-28

CDN or edge

Amazon CloudFront

Platform or framework

Adobe Experience Manager, PrestaShop

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

113 KB, gzip

Images on homepage

15 (jpg 8, svg 7)

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

• chaparnet.com64
• foxpost.hu64
• gls-italy.com65
• jadlog.com.br64
• trackcourier.io65

Postage & Courier Services readiness benchmark