Website readiness profile · Snapshot 23 October 2026
xoom.com
xoom.com's public homepage, certificate and DNS checked against 31 practices and compared with 157 Online Payment & Wallets sites.
- Readiness index
- 76/100
- Ahead of
- 70%
- Practices observed
- 21/30
- Popularity band
- Top 50K
Online Payment & Wallets median 64
of measured Online Payment & Wallets sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: xoom.com. Thin bar: Online Payment & Wallets peer median.
Enable
82/100
Peers 72
Harden
80/100
Peers 63
Accelerate
62/100
Peers 61
Recover
100/100
Peers 6
Priority fixes for xoom.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
62% of Online Payment & Wallets peers do this. Limit: Only the standard location was requested, once, at the time of the check.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 2 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 5 external scripts without async or defer.
What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.
On Next.js: Use the next/script component with an appropriate loading strategy.
49% of Online Payment & Wallets peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 3 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 9 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.
63% of Online Payment & Wallets peers do this.
Priority 4 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
35% of Online Payment & Wallets peers do this.
What xoom.com already does well
Practices fewer than half of Online Payment & Wallets peers use.
- Nameservers spread across providersNameservers spread across more than one operator.6.4% of peers
- DNSSEC signedDNSSEC delegation (DS record) present.8.3% of peers
- Structured data presentJSON-LD structured data found.38% of peers
What we saw
- Homepage checked
- https://www.xoom.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 198-day validity, expiring 2027-01-31
- CDN or edge
- Cloudflare
- Platform or framework
- Next.js
- DNS operators
- Vercara UltraDNS, plus 1 self-run or other nameserver domain
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=reject
- Homepage HTML
- 217 KB, gzip
- Images on homepage
- 9 (webp 6, svg 2, png 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
Not observed 9
Observed 21
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- Modern image formats in use
- robots.txt published
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Not measured 1
- Static files cached for 30 days or more
Own xoom.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: xoom.com. This profile covers configuration only.