xoom.com website review

49 files are served with short cache lifetimes, so returning visitors download them again (764 KiB).

22 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

Your mobile performance score is 61 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

6 third-party services load with your homepage (PayPal, Segment and datadoghq-browser-agent.com and others), adding 1.8 MB and 726 ms of main-thread time.

About 267 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

PayPal costs a phone 477 ms of main-thread work and 1,020 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

7 images could be 301 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

A phone's processor spends 2.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

ctfassets.net costs a phone 0 ms of main-thread work and 624 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

7 long tasks block the main thread while loading, the longest for 134 ms. During a long task the page ignores taps.

Polyfills for old browsers add 56 KiB JavaScript that modern phones do not need.

29 KiB could be saved by minifying JavaScript.

Desktop scores 94 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Transfer to bank accounts and debit cards”.

The page becomes fully interactive after 12.0 s. Good is under 3.8 s.

The first text or image appears after 3.5 s on a phone. Good is under 1.8 s.

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 930 ms for your server to start answering (75th percentile). Good is under 800 ms.

Visually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 271 ms in total while the page loads. Good is under 200 ms.

3 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 101 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 images further down the page (426 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

5 images are downloaded at several times the size a phone draws them, for example send-cash_05x.webp at 960 px wide, shown at 318 px. Resized copies would save about 5 KiB.

1 image (81 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 0.53 g of CO₂e: 63.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://www.xoom.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 40 pages on xoom.com and 9 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.xoom.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.xoom.com/sign-up and https://www.xoom.com/en-us/usd/send-money/transfer/select-country are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://www.xoom.com/money-transfer all use the title “Xoom, a PayPal Service | Send Money Online”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.xoom.com/sign-up and https://www.xoom.com/xoom-locations have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.xoom.com/en-us/usd/send-money/transfer/select-country, https://www.xoom.com/online-security-and-privacy-at-xoom, https://www.xoom.com/protect-your-money, https://www.xoom.com/manage-cookies and https://www.xoom.com/legal use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.xoom.com/xoom-locations, whose canonical is https://www.xoom.com/go/xoom-partner-locations. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.xoom.com/en-us/usd/send-money/transfer/select-country, https://www.xoom.com/about, https://www.xoom.com/site-map, https://www.xoom.com/online-security-and-privacy-at-xoom, https://www.xoom.com/protect-your-money and https://www.xoom.com/legal/filing-complaints and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.xoom.com/xoom-locations and https://www.xoom.com/legal/filing-complaints have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 236 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Segment (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 17 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.