Website readiness profile · Snapshot 23 October 2026
fragment.com
fragment.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 63/100
- Ahead of
- 27%
- Practices observed
- 16/29
- Popularity band
- Top 50K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: fragment.com. Thin bar: E-Commerce & Marketplaces peer median.
Enable
59/100
Peers 86
Harden
65/100
Peers 60
Accelerate
67/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for fragment.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.
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. Limit: Only the standard location was requested, once, at the time of the check.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 2 · 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.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 3 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 4 days, short of the 30-day benchmark.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
60% of E-Commerce & Marketplaces peers do this.
Priority 4 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.fragment.com.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
39% of E-Commerce & Marketplaces peers do this.
What fragment.com already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.32% of peers
- Reachable over IPv6IPv6 address published.40% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.44% of peers
What we saw
- Homepage checked
- https://fragment.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2027-01-16
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- HSTS
- max-age 365 days, includeSubDomains, preload
- Homepage HTML
- 804 KB, br
- Images on homepage
- 0
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
Not observed 13
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- robots.txt published
- XML sitemap discoverable
- Structured data present
- Page language declared
- Nameservers spread across providers
Observed 16
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- X-Content-Type-Options: nosniff
- Framing restricted
- HTTP/2 negotiated
- HTML compressed
- No render-blocking scripts in <head>
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own fragment.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: fragment.com. This profile covers configuration only.