myfrido.com

Readiness by lane

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

Priority fixes for myfrido.com

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

1. Priority 1 · Accelerate

   Modern image formats in use

   Observed: The homepage had 297 images and none used WebP or AVIF.

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   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 Shopify: Shopify's image CDN can serve modern formats; follow Shopify's web performance guidance for themes.

   47% of E-Commerce & Marketplaces peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

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

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

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

   Guide: HTTPS and TLS Guide for Website 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.

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

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

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

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What myfrido.com already does well

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

• Referrer-Policy setReferrer-Policy present.20% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
• HTTP/3 advertisedHTTP/3 advertised.47% of peers

What we saw

Homepage checked

https://myfrido.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-03-19

CDN or edge

Amazon CloudFront

Platform or framework

Shopify, Next.js

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

1,096 KB, gzip

Images on homepage

297 (png 1737, jpg 216, svg 99, gif 1)

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

• modasena.com73
• moodo.pl73
• mundimotos.com73
• novey.com.pa73
• nurserylive.com73

E-Commerce & Marketplaces readiness benchmark