ine.mx

Readiness by lane

Green: ine.mx. Thin bar: Government Services peer median.

Priority fixes for ine.mx

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

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

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Amazon CloudFront: Set frame options in a response headers policy.

   68% of Government Services peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 7 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.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   39% of Government Services peers do this.

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

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 41 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 WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.

   15% of Government Services peers do this.

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

What ine.mx already does well

Practices fewer than half of Government Services peers use.

• Structured data presentJSON-LD structured data found.15% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers
• Social preview image setog:image present.36% of peers

What we saw

Homepage checked

https://www.ine.mx/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 394-day validity, expiring 2026-11-14

CDN or edge

Amazon CloudFront

Platform or framework

WordPress

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

206 KB, gzip

Images on homepage

41 (png 69, jpg 8, svg 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 Government Services sites

• europa.eu65
• gba.gob.ar65
• gov.uz65
• prefeitura.sp.gov.br65
• prix-carburants.gouv.fr65

Government Services readiness benchmark