fnp.com

Readiness by lane

Green: fnp.com. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for fnp.com

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.

   94% of E-Commerce & Marketplaces 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 · Accelerate

   Modern image formats in use

   Observed: The homepage had 123 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 Next.js: The next/image component serves optimized formats automatically.

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

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

3. Priority 3 · Harden

   HSTS kept for at least a year

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

   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 Next.js: Add the header in the headers() option of next.config.js for all routes.

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

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for fnp.com 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.

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

   Guide: A Practical Website Health Check for Owners

What fnp.com already does well

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

• Reachable over IPv6IPv6 address published.40% of peers
• HTTP/3 advertisedHTTP/3 advertised.47% of peers

What we saw

Homepage checked

https://www.fnp.com/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

DigiCert, 371-day validity, expiring 2027-01-05

Platform or framework

Next.js

DNS operators

Akamai Edge DNS

HSTS

max-age 1 days

DMARC policy

p=none

Homepage HTML

1,064 KB, gzip

Images on homepage

123 (jpg 53, svg 35, png 35)

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 E-Commerce & Marketplaces sites

• easy.com.ar59
• expert.it59
• farmaciasdesimilares.com59
• graniph.com59
• honor.com59

E-Commerce & Marketplaces readiness benchmark