26.6 sec in total
7.1 sec
19.2 sec
292 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 7.1 sec and then it took 19.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
travelex.co.nz performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value5.7 s
16/100
25%
Value15.9 s
0/100
10%
Value2,680 ms
4/100
30%
Value0.385
27/100
15%
Value14.2 s
9/100
10%
7081 ms
6032 ms
2349 ms
866 ms
4211 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 61% of them (44 requests) were addressed to the original Travelex.co.nz, 6% (4 requests) were made to Cm.g.doubleclick.net and 4% (3 requests) were made to U3s.mathtag.com. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Travelex.co.nz.
Page size can be reduced by 129.7 kB (30%)
426.2 kB
296.5 kB
In fact, the total size of Travelex.co.nz main page is 426.2 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. 20% of websites need less resources to load. Images take 249.4 kB which makes up the majority of the site volume.
Potential reduce by 64.8 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 12.1 kB, which is 15% 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 64.8 kB or 82% of the original size.
Potential reduce by 12.3 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 37.3 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 37.3 kB or 47% of the original size.
Potential reduce by 15.3 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 15.3 kB or 83% of the original size.
Number of requests can be reduced by 54 (89%)
61
7
The browser has sent 61 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 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.travelex.co.nz
7081 ms
css
6032 ms
css-nz
2349 ms
custom-code.css
866 ms
js-head
4211 ms
widgets.js
1787 ms
custom-code.css
1603 ms
common-fix.css
1093 ms
js-body
1845 ms
js-nz
2138 ms
widgetcontrol.js
2062 ms
jquery_custom
4306 ms
travelex-logo.png
469 ms
flags-sprite.png
472 ms
all-sprite.png
481 ms
beach1300darknz.jpg
1462 ms
arrow-cutout.png
243 ms
promo-3.jpg
489 ms
couple-in-europe.png
6028 ms
our-best-rates.jpeg
1460 ms
promo-1.jpg
975 ms
travelex-money-card-new.png
1252 ms
hiw1.png
965 ms
hiw-step1.png
1211 ms
hiw-step2.png
1655 ms
hiw-step3.png
1459 ms
hiw2.png
1465 ms
hiw-step4.jpg
1488 ms
hiw-step5.jpg
3175 ms
hiw-step6.jpg
1638 ms
hiw3.png
1678 ms
hiw-step7.jpg
1699 ms
hiw-step8.jpg
1856 ms
hiw-step9.jpg
1868 ms
mastercard-curved-64px.png
1887 ms
maestro-curved-64px.png
1909 ms
visa-curved-64px.gif
2075 ms
vseal.gif
2086 ms
LatoLatin-Light.woff
3665 ms
LatoLatin-Regular.woff
3706 ms
icomoon-ultimate.woff
2998 ms
hiw-arrow.png
2701 ms
rate-tracker-promo.png
3132 ms
gtm.js
99 ms
activityi;src=1594910;type=count904;cat=01hom748;u11=Travelex.co.uk;ord=1;num=5650738317053.765
97 ms
activityi;src=1594910;type=count904;cat=01hom748;u11=Travelex.co.uk;ord=1;num=3726744551677.257
120 ms
iframe_api
78 ms
multi
1120 ms
activity;xsp=4333730;ord=a
88 ms
analytics.js
67 ms
www-widgetapi.js
54 ms
collect
10 ms
collect
71 ms
quant.js
71 ms
fbevents.js
83 ms
img
78 ms
img
91 ms
rules-p-YBy4WWRDFGfwU.js
35 ms
img
37 ms
715740221903490
49 ms
pixel
48 ms
ps
33 ms
pixel;r=1034036171;labels=_fp.event.Homepage;rf=0;a=p-YBy4WWRDFGfwU;url=https%3A%2F%2F1594910.fls.doubleclick.net%2Factivityi%3Bsrc%3D1594910%3Btype%3Dcount904%3Bcat%3D01hom748%3Bu11%3DTravelex.co.uk%3Bord%3D1%3Bnum%3D3726744551677.257%3F;ref=https%3A%2F%2Fwww.travelex.co.nz%2F;fpan=u;fpa=;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504700475095;tzo=-180;ogl=
69 ms
pixel;r=1307431182;labels=_fp.event.Homepage;rf=0;a=p-YBy4WWRDFGfwU;url=https%3A%2F%2F1594910.fls.doubleclick.net%2Factivityi%3Bsrc%3D1594910%3Btype%3Dcount904%3Bcat%3D01hom748%3Bu11%3DTravelex.co.uk%3Bord%3D1%3Bnum%3D5650738317053.765%3F;ref=https%3A%2F%2Fwww.travelex.co.nz%2F;fpan=u;fpa=;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504700475098;tzo=-180;ogl=
68 ms
52 ms
52 ms
pixel
16 ms
pixel
12 ms
pixel
13 ms
GetAccessToken
220 ms
rendered.png
1791 ms
Lato-Italic.woff
4584 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
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
Form elements do not have associated labels
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
Some elements have a [tabindex] value greater than 0
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
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: