STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

planity.com

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

Readiness index
58/100

E-Commerce & Marketplaces median 71

Ahead of
15%

of measured E-Commerce & Marketplaces sites

Practices observed
15/30

1 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:21:17 UTC from one location. How we measure

Readiness by lane

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

Enable

92/100

Peers 86

Harden

48/100

Peers 60

Accelerate

41/100

Peers 69

Recover

0/100

Peers 11

Priority fixes for planity.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.

    On Amazon CloudFront: Choose HTTP/2 (or HTTP/2 and HTTP/3) as supported versions on the distribution.

    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

    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.

  3. Priority 3 · Accelerate

    Offscreen images lazy-loaded

    Observed: The homepage had 16 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.

  4. Priority 4 · Harden

    Framing restricted

    Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

    What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

    On Amazon CloudFront: Set frame options in a response headers policy.

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

What planity.com already does well

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

  • DMARC policy enforces quarantine or rejectDMARC policy p=reject.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.planity.com/
Homepage response
HTTP 200
TLS
TLSv1.3
Certificate
Amazon, 197-day validity, expiring 2027-02-02
CDN or edge
Amazon CloudFront
DNS operators
Amazon Route 53
DMARC policy
p=reject
Homepage HTML
796 KB, gzip
Images on homepage
16 (jpg 15)

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 15

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • HTML compressed
  • Modern image formats in use
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • 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 planity.com?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: planity.com. This profile covers configuration only.

Compare with other E-Commerce & Marketplaces sites