Tools & Wizards About Us

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

travelex.co.nz

Currency Exchange & Travel Card at Great Rates | Travelex

Page Load Speed

16.1 sec in total

First Response

410 ms

Resources Loaded

14.9 sec

Page Rendered

792 ms

About Website

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.nz

Key Findings

We 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.

Performance Metrics

travelex.co.nz performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.417

23/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

travelex.co.nz

410 ms

www.travelex.co.nz

3453 ms

css

6834 ms

custom-code.css

609 ms

js-head

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 Optimization Overview & Recommendations

Page size can be reduced by 159.9 kB (20%)

Content Size

800.5 kB

After Optimization

640.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-82%

Potential reduce by 102.0 kB

  • Original 124.0 kB
  • After minification 95.7 kB
  • After compression 22.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.

Image Optimization

-4%

Potential reduce by 24.4 kB

  • Original 581.2 kB
  • After minification 556.8 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.

JavaScript Optimization

-42%

Potential reduce by 26.9 kB

  • Original 63.8 kB
  • After minification 62.8 kB
  • After compression 36.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.

CSS Optimization

-21%

Potential reduce by 6.6 kB

  • Original 31.5 kB
  • After minification 31.5 kB
  • After compression 25.0 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.

Requests Breakdown

Number of requests can be reduced by 33 (56%)

Requests Now

59

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

travelex.co.nz accessibility score

64

Accessibility Issues

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

ARIA tooltip elements do not have accessible names.

High

[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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

travelex.co.nz best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

travelex.co.nz SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: