16.1 sec in total
410 ms
14.9 sec
792 ms
Click here to check amazing Travelex content for New Zealand. Otherwise, check out these important facts you probably never knew about travelex.co.nz
Buy your foreign currency online and pick up in one of our convenient store locations. Use our Currency converter to compare travel money exchange rates.
Visit travelex.co.nzWe analyzed Travelex.co.nz page load time and found that the first response time was 410 ms and then it took 15.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
travelex.co.nz performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value12.4 s
0/100
25%
Value15.3 s
1/100
10%
Value1,280 ms
18/100
30%
Value0.417
23/100
15%
Value16.4 s
5/100
10%
410 ms
3453 ms
6834 ms
609 ms
3952 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 74% of them (50 requests) were addressed to the original Travelex.co.nz, 3% (2 requests) were made to Youtube.com and 3% (2 requests) were made to Adservice.google.com. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Travelex.co.nz.
Page size can be reduced by 159.9 kB (20%)
800.5 kB
640.6 kB
In fact, the total size of Travelex.co.nz main page is 800.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 581.2 kB which makes up the majority of the site volume.
Potential reduce by 102.0 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. This page needs HTML code to be minified as it can gain 28.3 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 102.0 kB or 82% of the original size.
Potential reduce by 24.4 kB
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. Travelex images are well optimized though.
Potential reduce by 26.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 26.9 kB or 42% of the original size.
Potential reduce by 6.6 kB
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. Travelex.co.nz needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 21% of the original size.
Number of requests can be reduced by 33 (56%)
59
26
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Travelex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
travelex.co.nz
410 ms
www.travelex.co.nz
3453 ms
css
6834 ms
custom-code.css
609 ms
js-head
3952 ms
widgets.js
1002 ms
tp.widget.bootstrap.min.js
14 ms
stylemin.css
557 ms
localization.js
600 ms
opentag-123868-1743878.js
291 ms
flex-microform.min.js
61 ms
js-body
2060 ms
widgetcontrol.js
207 ms
dd25cbb4d3.js
174 ms
rates-table-nz.js
203 ms
gtm.js
127 ms
travelex-logo-simple.svg
520 ms
flags-sprite.svg
775 ms
NG.png
268 ms
SG.png
260 ms
san-fran-722.jpg
479 ms
arrow-cutout.svg
521 ms
Currency.svg
1354 ms
Top-Up-Card.svg
1361 ms
credit_card.svg
2076 ms
liberty.jpg
721 ms
US.png
724 ms
bank-note-solo-copy.png
930 ms
tmc-card-solo.png
927 ms
JP.png
976 ms
au.png
1132 ms
EU.png
1133 ms
tmc-card.png
1182 ms
curr-conv-nz-hp.jpg
1337 ms
subscribe-email-au-hp.jpg
1533 ms
follow-us-ig-nz-hp.jpg
1386 ms
travel-tracker-nz-hp.jpg
1541 ms
mc-20x32.png
1555 ms
visa-mc-verified-20x56.png
1563 ms
visa-20x59.png
1589 ms
vseal.gif
1736 ms
au-hp-square-2-v2.jpg
1698 ms
newtmcapp-hp-tile-2.jpg
1724 ms
all-sprite.png
1724 ms
LatoLatin-Light.woff
3052 ms
LatoLatin-Regular.woff
4217 ms
icomoon-ultimate.woff
2166 ms
sg.png
1821 ms
activityi;src=1594910;type=count904;cat=01hom748;u11=Travelex.co.uk;ord=1;num=5489382431842.387
163 ms
iframe_api
82 ms
multi
312 ms
www-widgetapi.js
4 ms
activity;xsp=4333730;ord=a
155 ms
src=1594910;type=count904;cat=01hom748;u11=Travelex.co.uk;ord=1;num=5489382431842.387
98 ms
bounce
35 ms
quant.js
27 ms
fbevents.js
51 ms
ps
29 ms
src=8012379;type=invmedia;cat=wxoebjb1;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1
68 ms
bounce
20 ms
rendered.png
1340 ms
radio-btns.svg
1804 ms
custom-code.css
203 ms
custom-code.css
203 ms
common-fix.css
203 ms
common-fix.css
207 ms
home-page.css
209 ms
home-page.css
204 ms
travelex.co.nz accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
ARIA tooltip elements do not have accessible names.
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
Links do not have a discernible 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
travelex.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
travelex.co.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Travelex.co.nz 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 Travelex.co.nz 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.
travelex.co.nz
Open Graph description is not detected on the main page of Travelex. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: