elsevier.es

Readiness by lane

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

Priority fixes for elsevier.es

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 37 days, below the one-year benchmark.

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

   34% of Data & Analytics 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

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for elsevier.es was p=none, which asks receivers to take no action on failing mail.

   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.

   38% of Data & Analytics 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 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.

   54% of Data & Analytics 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 Data & Analytics peers do this.

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

What elsevier.es already does well

Practices fewer than half of Data & Analytics peers use.

• CAA records limit who can issue certificatesCAA limits issuance to digicert.com, globalsign.com, pki.goog and others.15% of peers
• Content Security Policy presentContent-Security-Policy present.24% of peers
• Modern image formats in useWebP or AVIF images detected.31% of peers

What we saw

Homepage checked

https://www.elsevier.es/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 396-day validity, expiring 2027-03-06

CDN or edge

Cloudflare, Amazon CloudFront

Platform or framework

Next.js

DNS operators

Amazon Route 53

HSTS

max-age 37 days

DMARC policy

p=none

Homepage HTML

392 KB, gzip

Images on homepage

36 (jpg 92, svg 9, webp 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 Data & Analytics sites

• amarstock.com69
• dextools.io70
• dolphinradar.com69
• dubaicityofgold.com68
• einforma.com68

Data & Analytics readiness benchmark