STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

icollector.com

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

Readiness index
24/100

E-Commerce & Marketplaces median 71

Ahead of
<1%

of measured E-Commerce & Marketplaces sites

Practices observed
6/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:20:26 UTC from one location. How we measure

Readiness by lane

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

Enable

31/100

Peers 86

Harden

23/100

Peers 60

Accelerate

20/100

Peers 69

Recover

0/100

Peers 11

Priority fixes for icollector.com

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

  1. Priority 1 · Harden

    HTTP requests move to HTTPS

    Observed: A request to http://www.icollector.com/ was not redirected to HTTPS.

    Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

    What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

    On Amazon CloudFront: Set the viewer protocol policy of each cache behaviour to Redirect HTTP to HTTPS.

    96% of E-Commerce & Marketplaces peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

  2. Priority 2 · Enable

    Mobile viewport configured

    Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

    What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

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

  3. Priority 3 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.

    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.

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

What we saw

Homepage checked
https://www.icollector.com/
Homepage response
HTTP 200
TLS
TLSv1.3
Certificate
Amazon, 197-day validity, expiring 2027-01-12
CDN or edge
Amazon CloudFront
DNS operators
Amazon Route 53
DMARC policy
p=none
Homepage HTML
79 KB, br
Images on homepage
46 (png 34, jpg 8, 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

Own icollector.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: icollector.com. This profile covers configuration only.

Compare with other E-Commerce & Marketplaces sites