7 sec in total
437 ms
3.1 sec
3.4 sec
Click here to check amazing Wise content for United States. Otherwise, check out these important facts you probably never knew about wise.com
Banks charge a lot for overseas transfers. We don't. Transfer money abroad easily and quickly with our low cost money transfers.
Visit wise.comWe analyzed Wise.com page load time and found that the first response time was 437 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
wise.com performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value4.0 s
50/100
25%
Value7.6 s
25/100
10%
Value2,220 ms
6/100
30%
Value0
100/100
15%
Value17.5 s
4/100
10%
437 ms
181 ms
551 ms
122 ms
173 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 71% of them (110 requests) were addressed to the original Wise.com, 6% (10 requests) were made to Dq8dwmysp7hk1.cloudfront.net and 3% (4 requests) were made to Gtm.wise.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source S.yimg.jp.
Page size can be reduced by 421.1 kB (19%)
2.2 MB
1.8 MB
In fact, the total size of Wise.com main page is 2.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 417.4 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 417.4 kB or 82% of the original size.
Potential reduce by 2 B
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Wise images are well optimized though.
Potential reduce by 3.7 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 19 B
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Wise.com has all CSS files already compressed.
Number of requests can be reduced by 112 (75%)
149
37
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wise. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
wise.com
437 ms
cookie-consent.js
181 ms
wisetag
551 ms
9c6340296eeef4aa.css
122 ms
55092385a356a23a.css
173 ms
dfdde1b07bd8e161.css
181 ms
84887e16f01714f2.css
175 ms
60a064ba01a124ad.css
179 ms
polyfills-c67a75d1b6f99dc8.js
437 ms
49559f63-7f2ae85b6f2f3c26.js
485 ms
2e46638e.f389ce79045c4671.js
479 ms
551bb5a3.71034620812dc911.js
475 ms
5367-a63dcd913ec9c9e6.js
498 ms
9053.14458a0271f81f7f.js
472 ms
8708-fc7810b341b05365.js
543 ms
3148-190c1df91fe3ab94.js
534 ms
2612.fe85e7c6b21076b2.js
534 ms
belowFold.71cae0cf070709c0.js
532 ms
webpack-36a493a561f6eedd.js
550 ms
framework-5d87c96a828a416a.js
560 ms
main-0ab5801fa5321f16.js
548 ms
_app-5d661e575a25da48.js
553 ms
0b8754db-a6dc7bb8c88d90a7.js
555 ms
9939b33b-e00eafbee607aca2.js
557 ms
75fc9c18-776d1f15d3802f96.js
752 ms
2641-bb001ef872efc001.js
757 ms
6481-1f0444772ee19317.js
879 ms
2828-b66815bedead036a.js
877 ms
7222-174525b3b113e249.js
888 ms
3177-c8f2951de94cb5f2.js
889 ms
index-30b50a4316cf824e.js
895 ms
_buildManifest.js
898 ms
_ssgManifest.js
912 ms
western-union.svg
57 ms
brand_logo_inverse.svg
869 ms
brand_flag.svg
879 ms
multi_currency_account_v2.svg
871 ms
en.svg
883 ms
xe.svg
48 ms
remitly.svg
50 ms
ofx.svg
56 ms
bank-of-america.svg
53 ms
xoom.svg
66 ms
moneygram.svg
126 ms
chase.svg
225 ms
wells-fargo.svg
223 ms
paypal.svg
227 ms
en.svg
864 ms
send.2e93977b.jpg
764 ms
spend.e6d7cf61.jpg
766 ms
receive.0aafdf71.jpg
761 ms
hold.5fa2b877.jpg
763 ms
abroad_section.08671aad.jpeg
670 ms
shopping.7ed13814.jpg
669 ms
TW-Averta-Regular.8e8db741.woff
524 ms
TW-Averta-Semibold.c170753c.woff
523 ms
TW-Averta-Bold.5fd4f63f.woff
519 ms
card_section.d768cf8d.jpg
502 ms
receive_section.0ac14889.jpeg
471 ms
property_section.95e250f2.jpeg
485 ms
customer_support.8c55be17.jpg
471 ms
safeguarded_leading_banks.svg
466 ms
regulated_by_fcg.svg
480 ms
segragated_accounts.svg
471 ms
secure_transations.svg
460 ms
data_protection.svg
477 ms
dedicated_fraud_team.svg
479 ms
usd.png
479 ms
eur.png
289 ms
gbp.png
282 ms
aud.png
178 ms
nzd.png
181 ms
sgd.png
173 ms
ron.png
172 ms
cad.png
164 ms
huf.png
363 ms
try.png
361 ms
aed.png
159 ms
ars.png
158 ms
bdt.png
155 ms
bgn.png
166 ms
bwp.png
152 ms
chf.png
326 ms
clp.png
328 ms
cny.png
331 ms
crc.png
324 ms
czk.png
326 ms
dkk.png
328 ms
egp.png
323 ms
gel.png
326 ms
ghs.png
273 ms
hkd.png
267 ms
hrk.png
269 ms
idr.png
268 ms
ils.png
265 ms
inr.png
376 ms
jpy.png
365 ms
kes.png
363 ms
krw.png
359 ms
lkr.png
349 ms
mad.png
345 ms
mxn.png
349 ms
myr.png
344 ms
ngn.png
341 ms
nok.png
341 ms
npr.png
329 ms
php.png
327 ms
pkr.png
328 ms
pln.png
328 ms
rub.png
427 ms
sek.png
326 ms
thb.png
424 ms
tzs.png
322 ms
uah.png
335 ms
ugx.png
311 ms
uyu.png
222 ms
vnd.png
219 ms
xof.png
217 ms
zar.png
216 ms
zmw.png
613 ms
flags.0e8bef8f.jpg
357 ms
uwt.js
183 ms
analytics.js
233 ms
scevent.min.js
524 ms
bat.js
491 ms
pixel
209 ms
mixpanel-2-latest.min.js
584 ms
ytag.js
1244 ms
pixel.js
511 ms
ping.min.js
665 ms
up_loader.1.1.0.js
509 ms
tv2track.js
710 ms
2613fe4c-10d3-4553-b916-fbd27f462422-latest.js
506 ms
spef.min.js
973 ms
js
243 ms
230 ms
adsct
598 ms
adsct
596 ms
collect
266 ms
collect
483 ms
collect
345 ms
5990948.js
175 ms
219 ms
tracker-latest.min.js
113 ms
rp.gif
241 ms
151 ms
pdst-events-prod-sink
158 ms
5a28e627
111 ms
5a28e627
108 ms
5a28e627
98 ms
tv2track.php
57 ms
ga-audiences
104 ms
_set_cookie
36 ms
41 ms
piwik.php
182 ms
wise.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
wise.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
wise.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wise.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wise.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
wise.com
Open Graph data is detected on the main page of Wise. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: