STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

jm101.com

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

Readiness index
38/100

E-Commerce & Marketplaces median 71

Ahead of
1%

of measured E-Commerce & Marketplaces sites

Practices observed
8/28

3 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:42:57 UTC from one location. How we measure

Readiness by lane

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

Enable

44/100

Peers 86

Harden

38/100

Peers 60

Accelerate

33/100

Peers 69

Recover

0/100

Peers 11

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

    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 · Enable

    robots.txt published

    Observed: No robots.txt file was returned at the site root.

    What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

    95% 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 we saw

Homepage checked
https://jm101.com/
Homepage response
HTTP 200
TLS
TLSv1.3
Certificate
GoDaddy, 397-day validity, expiring 2026-11-09
DNS operators
GoDaddy DNS
Homepage HTML
11 KB, gzip
Images on homepage
2 (png 2)

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

Compare with other E-Commerce & Marketplaces sites