STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

sprzedajemy.pl

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

Readiness index
46/100

E-Commerce & Marketplaces median 71

Ahead of
3.6%

of measured E-Commerce & Marketplaces sites

Practices observed
12/30

1 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 11:52:24 UTC from one location. How we measure

Readiness by lane

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

Enable

72/100

Peers 86

Harden

29/100

Peers 60

Accelerate

53/100

Peers 69

Recover

0/100

Peers 11

Priority fixes for sprzedajemy.pl

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.

  2. Priority 2 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

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

  3. Priority 3 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

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

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

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

What sprzedajemy.pl already does well

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

  • Modern image formats in useWebP or AVIF images detected.47% of peers

What we saw

Homepage checked
https://sprzedajemy.pl/
Homepage response
HTTP 200
TLS
TLSv1.2
Certificate
GlobalSign, 396-day validity, expiring 2027-02-10
DNS operators
Amazon Route 53
DMARC policy
p=none
Homepage HTML
224 KB, gzip
Images on homepage
113 (jpg 107, webp 7, png 3)

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 12

  • HTTP requests move to HTTPS
  • Certificate has more than 14 days left
  • HTML compressed
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • robots.txt published
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Not measured 1

  • Static files cached for 30 days or more

Own sprzedajemy.pl?

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: sprzedajemy.pl. This profile covers configuration only.

Compare with other E-Commerce & Marketplaces sites