wise.com website review

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

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

3 images could be 586 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

Your mobile performance score is 30 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

20 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.

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

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

8 third-party services load with your homepage (Google Tag Manager, The Trade Desk and Mixpanel and others), adding 436 KiB and 701 ms of main-thread time.

Google Tag Manager costs a phone 479 ms of main-thread work and 281 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.

The page has 2,377 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Real visitors wait 871 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Send securely to 140+ countriesSee our fees and speeds to:G…”.

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

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

1 image 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 561 ms to 543 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.5 MB in 169 requests on a phone: media 4.0 MB (3), scripts 2.5 MB (65) and images 1.3 MB (26). Under 2 MB keeps phones on slow connections fast.

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

Some list items are not inside a list.

1 element hidden from screen readers can still receive keyboard focus.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Your title is 76 characters, so Google will cut it off around 60: “Wise: The international account | Money without borders | Wise United States”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 127 pages on wise.com and 17 external pages.

There is no /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.

/us/pricing and /us/business/manage-team have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5990948&tm=gtm002&Ver=2&mid=dfdc9d1e-9127-488d-b3a4-4c9d2cd9d7be&bo=1&sid=7b44c010c5c211f1a36adbe5ebc868f1&vid=7b44cf00c5c211f1872cd724d33a4414&vids=1&msclkid=N&pi=918.

4 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Content security policy”).

1 link go through two or more redirects, for example https://wise-app.sng.link/Apnl5/0r11?_dl=tw%3A%2F%2F&_smtype=3.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

Your security.txt expired on 2026-08-29, so researchers may not trust its contact details.

wise.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

wise.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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.

The homepage carries about 1,164 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Mixpanel and 2 mores (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 26 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.