ine.es

Readiness by lane

Green: ine.es. Thin bar: Data & Analytics peer median.

Priority fixes for ine.es

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   86% of Data & Analytics peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. Priority 2 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   91% of Data & Analytics 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 4 hours, 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.

   49% of Data & Analytics peers do this.

   Guide: Browser Caching Guide for Website Owners

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

   34% of Data & Analytics peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What ine.es already does well

Practices fewer than half of Data & Analytics peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.8.2% of peers
• CAA records limit who can issue certificatesCAA limits issuance to camerfirma.com, fnmt.es, izenpe.com.15% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.38% of peers

What we saw

Homepage checked

https://www.ine.es/

Homepage response

HTTP 200

TLS

TLSv1.2

Certificate

FNMT-RCM, 198-day validity, expiring 2026-12-17

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

76 KB, gzip

Images on homepage

67 (png 32, svg 21, jpg 14)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Data & Analytics sites

• 0lin.com47
• 2osb.com46
• ebird.org49
• kworb.net46
• steamcharts.com50

Data & Analytics readiness benchmark