Website review, no card needed
westernunion.com website review
Visit site (opens in a new tab)Reviewed 11 October 202643 issues · 94 checks
This review found 43 issues worth fixing on westernunion.com, 15 of them high impact, across 94 checks. The most urgent: audioeye.com adds 2.4 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 3.1 s |
| Apr 25, 2026 | 3.1 s |
| May 2, 2026 | 3.1 s |
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 781 ms |
| Apr 25, 2026 | 790 ms |
| May 2, 2026 | 784 ms |
| May 9, 2026 | 765 ms |
| May 16, 2026 | 757 ms |
| May 23, 2026 | 743 ms |
| May 30, 2026 | 745 ms |
| Jun 6, 2026 | 754 ms |
| Jun 13, 2026 | 760 ms |
| Jun 20, 2026 | 770 ms |
| Jun 27, 2026 | 772 ms |
| Jul 4, 2026 | 770 ms |
| Jul 11, 2026 | 765 ms |
| Jul 18, 2026 | 759 ms |
| Jul 25, 2026 | 746 ms |
| Aug 1, 2026 | 737 ms |
| Aug 8, 2026 | 729 ms |
| Aug 15, 2026 | 739 ms |
| Aug 22, 2026 | 741 ms |
| Aug 29, 2026 | 733 ms |
| Sep 5, 2026 | 722 ms |
| Sep 12, 2026 | 702 ms |
| Sep 19, 2026 | 692 ms |
| Sep 26, 2026 | 683 ms |
| Oct 3, 2026 | 676 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.4 s
2.0 s
2.7 s
3.4 s
4.1 s
4.7 s
5.4 s
Speed
audioeye.com adds 2.4 s
2.4 saudioeye.com costs a phone 2.4 s of main-thread work and 408 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Quantum Metric adds 1.9 s
1.9 sQuantum Metric costs a phone 1.9 s of main-thread work and 145 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 14.6 s
A phone's processor spends 14.6 s on main-thread work while loading, 10.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, Quantum Metric and Google Tag Manager and others), adding 1.9 MB and 6.5 s of main-thread time.
Use efficient cache lifetimes
1.4 MB74 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Reduce unused JavaScript
150 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64 (desktop: 65). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 519 ms
519 msGoogle Tag Manager costs a phone 519 ms of main-thread work and 308 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 485 ms. During a long task the page ignores taps.
Adobe Tag Manager adds 444 ms
444 msAdobe Tag Manager costs a phone 444 ms of main-thread work and 248 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.
Optimizely adds 416 ms
416 msOptimizely costs a phone 416 ms of main-thread work and 424 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.
2,747 HTML elements
The page has 2,747 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
104 KiBPolyfills for old browsers add 104 KiB JavaScript that modern phones do not need.
Reduce unused CSS
33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 25 ms
25 msYour server sent the HTML in 25 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Time to Interactive: 31.5 s
31.5 sThe page becomes fully interactive after 31.5 s. Good is under 3.8 s.
Total Blocking Time: 3.6 s
3.6 sScripts block taps and scrolling for 3.6 s in total while the page loads. Good is under 200 ms.
Real-user INP: 405 ms
405 msReal visitors wait 405 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 889 ms
889 msReal visitors wait 889 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 781 ms to 676 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Send money online from the United States at our best price”.
Cumulative Layout Shift: 0.04
0.04The layout barely moves while loading (CLS 0.04, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 284 requests
3.9 MBYour homepage downloads 3.9 MB in 284 requests on a phone: scripts 2.9 MB (81), fonts 516 KiB (7) and other files 196 KiB (139). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 131.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must be contained by particular parents (1 element)
Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
[role]s do not have all required [aria-*] attributes
[role]s do not have all required [aria-*] attributes (1 element).
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (39 elements)
All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
9 form fields without a label
9 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h6, h2 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
174 internal links, 19 external
The homepage links to 174 pages on westernunion.com and 19 external pages.
8 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Send and receive money transfers from the United States with Western Union. Check exchange rates, track transfers and s…”.
One H1 headline
Your main headline reads: “Send money online from the United States at our best price”.
Title: 41 characters
Your title is a healthy 41 characters: “Send & Receive Money in the United States”.
Canonical URL set
The canonical URL is https://www.westernunion.com/us/en/home.html.
Structured data in place
Structured data found: FAQPage and Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.westernunion.com/sitemap-index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (2,058 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.westernunion.com/llms.txt (195 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.westernunion.com/global-services/find-locations has no <title>, so Google invents the link text in results.
2 pages share a title
https://www.westernunion.com/web/global-service/track-transfer and https://www.westernunion.com/us/en/bill-pay/app/billpay-start all use the title “Money Transfer | Global Money Transfer | Western Union”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://www.westernunion.com/web/global-service/track-transfer, https://www.westernunion.com/us/en/bill-pay/app/billpay-start, https://www.westernunion.com/global-services/find-locations, https://www.westernunion.com/us/en/rewards/home.html and https://www.westernunion.com/us/en/rewards/shop-deals.html have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.westernunion.com/prepaid/PrepaidLandingScreen, whose canonical is https://www.westernunion.com/us/en/prepaid.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.westernunion.com/web/global-service/track-transfer, https://www.westernunion.com/us/en/bill-pay/app/billpay-start and https://www.westernunion.com/global-services/find-locations have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.westernunion.com/us/en/bill-pay/app/billpay-start and https://www.westernunion.com/global-services/find-locations 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
4 broken images
4 images failed to load on a phone, for example https://www.westernunion.com/us/en/home.html.
7 third-party cookies
7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
11 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,020 words of copy
The homepage carries about 1,020 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start now”.
24 calls to action
The homepage has 24 calls to action, for example “Register”, “Contact Us” and “Money Order Refunds”.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, a star rating, 1 trust badge and “112,576+ reviews”.
Analytics in place
Analytics detected: Amplitude.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Amplitude (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
23 cookies set on arrival
23Opening the homepage sets 23 cookies (measured from a US location before any click).
16 other companies contacted
Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at westernunion.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Amplitude
- Hosting
- AWS
Hiring
- Hiring
- 1 open role
- Job board
- greenhouse
- Careers page
- careers.westernunion.com (opens in a new tab)
Company
- Employees
- 11,000
- Founded
- 1851
- Headquarters
- Denver
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on westernunion.com, including 19 speed issues and 1 SEO issue. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.