solar.com.pl

Readiness by lane

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

Priority fixes for solar.com.pl

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

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

   Offscreen images lazy-loaded

   Observed: The homepage had 26 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

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

   Guide: Lazy Loading Without Broken Pages

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 4 external scripts 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.

   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.

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

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

What solar.com.pl already does well

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

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers
• Reachable over IPv6IPv6 address published.40% of peers
• Modern image formats in useWebP or AVIF images detected.47% of peers

What we saw

Homepage checked

https://www.solar.com.pl/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-28

CDN or edge

Cloudflare

Platform or framework

Magento / Adobe Commerce

DNS operators

Cloudflare

DMARC policy

p=quarantine

Homepage HTML

221 KB, br

Images on homepage

26 (webp 21, jpg 21, svg 5)

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

• sklepmartes.pl72
• slikk.club72
• snagtights.com72
• sonderpreis-baumarkt.de72
• taokids.com72

E-Commerce & Marketplaces readiness benchmark