STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

hema.nl

hema.nl's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.

Readiness index
84/100

E-Commerce & Marketplaces median 71

Ahead of
94%

of measured E-Commerce & Marketplaces sites

Practices observed
25/31

0 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 12:18:47 UTC from one location. How we measure

Readiness by lane

Green: hema.nl. Thin bar: E-Commerce & Marketplaces peer median.

Enable

100/100

Peers 86

Harden

71/100

Peers 60

Accelerate

88/100

Peers 69

Recover

100/100

Peers 11

Priority fixes for hema.nl

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

  1. Priority 1 · Harden

    Framing restricted

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

    Why it matters: Without it, another site can load your pages in a hidden frame and trick visitors into clicking buttons (clickjacking).

    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.

    70% of E-Commerce & Marketplaces peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

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

    44% of E-Commerce & Marketplaces peers do this.

  3. Priority 3 · Harden

    Content Security Policy present

    Observed: The homepage response did not include a Content-Security-Policy header.

    What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

    On Next.js: Next.js documents nonce-based CSP with middleware.

    48% of E-Commerce & Marketplaces peers do this.

  4. Priority 4 · Harden

    Certificate lifetime of 100 days or less

    Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.

    What to do: Move to automated issuance and renewal now, while you still have time to test it.

    70% of E-Commerce & Marketplaces peers do this.

What hema.nl already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

  • DNSSEC signedDNSSEC delegation (DS record) present.7.7% of peers
  • Nameservers spread across providersNameservers spread across more than one operator.11% of peers
  • Referrer-Policy setReferrer-Policy present.20% of peers

What we saw

Homepage checked
https://www.hema.nl/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 197-day validity, expiring 2026-12-15
CDN or edge
Amazon CloudFront
Platform or framework
Next.js
DNS operators
2 self-run or other nameserver domains
HSTS
max-age 730 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
1,770 KB, gzip
Images on homepage
138 (png 351, jpg 161, avif 9, svg 9)

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

Observed 25

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DNSSEC signed
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage
  • Nameservers spread across providers

Own hema.nl?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: hema.nl. This profile covers configuration only.

Compare with other E-Commerce & Marketplaces sites