eonnext.com

Readiness by lane

Green: eonnext.com. Thin bar: Energy, Electricity & Gas peer median.

Priority fixes for eonnext.com

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

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

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   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.

   64% of Energy, Electricity & Gas peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 25 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 Vercel: Vercel Image Optimization serves modern formats.

   36% of Energy, Electricity & Gas 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 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.

   30% of Energy, Electricity & Gas peers do this.

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

4. Priority 4 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   On Amazon CloudFront: Enable it in a response headers policy (security headers section).

   73% of Energy, Electricity & Gas peers do this.

   Guide: A Practical Website Health Check for Owners

What eonnext.com already does well

Practices fewer than half of Energy, Electricity & Gas peers use.

• security.txt publishedsecurity.txt with a contact found.7.9% of peers
• Structured data presentJSON-LD structured data found.36% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.41% of peers

What we saw

Homepage checked

https://www.eonnext.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 393-day validity, expiring 2026-12-29

CDN or edge

Amazon CloudFront, Vercel

Platform or framework

Next.js

DNS operators

Amazon Route 53

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

528 KB, br

Images on homepage

25 (svg 205, png 27)

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 Energy, Electricity & Gas sites

• edfenergy.com73
• eniplenitude.com77
• octopus.energy73
• octopusenergy.it73
• totalenergies.fr78

Energy, Electricity & Gas readiness benchmark