Tools & Wizards About Us
travelex.bh screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

travelex.bh

Currency Exchange & Travel Money at Great Rates | Travelex BH

Page Load Speed

2.7 sec in total

First Response

145 ms

Resources Loaded

2.4 sec

Page Rendered

205 ms

travelex.bh screenshot

About Website

Click here to check amazing Travelex content. Otherwise, check out these important facts you probably never knew about travelex.bh

Buy your foreign currency online here, then pick-up at your nearest Travelex store. Our currency converter can also help you easily compare exchange rates.

Visit travelex.bh

Key Findings

We analyzed Travelex.bh page load time and found that the first response time was 145 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

travelex.bh performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value1,130 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.492

17/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

travelex.bh

145 ms

www.travelex.bh

466 ms

css

151 ms

css-enbh

252 ms

js-head

296 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 87% of them (40 requests) were addressed to the original Travelex.bh, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (753 ms) belongs to the original domain Travelex.bh.

Page Optimization Overview & Recommendations

Page size can be reduced by 341.4 kB (22%)

Content Size

1.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Travelex.bh main page is 1.6 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. 45% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 63.2 kB

  • Original 78.7 kB
  • After minification 65.2 kB
  • After compression 15.5 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 13.4 kB, which is 17% 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 63.2 kB or 80% of the original size.

Image Optimization

-19%

Potential reduce by 277.4 kB

  • Original 1.5 MB
  • After minification 1.2 MB

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. Obviously, Travelex needs image optimization as it can save up to 277.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 493 B

  • Original 21.1 kB
  • After minification 21.1 kB
  • After compression 20.6 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.

CSS Optimization

-3%

Potential reduce by 345 B

  • Original 13.7 kB
  • After minification 13.6 kB
  • After compression 13.4 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.bh has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (50%)

Requests Now

32

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 32 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 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

travelex.bh

travelex.bh

145 ms

www.travelex.bh

www.travelex.bh

466 ms

css

css

151 ms

css-enbh

css-enbh

252 ms

js-head

js-head

296 ms

widgets.js

widgets.js

403 ms

js

js

64 ms

common-fix.css

common-fix.css

753 ms

ca-footer.css

ca-footer.css

237 ms

slick.css

slick.css

338 ms

rootlevelcssom.css

rootlevelcssom.css

335 ms

currency-page-de.css

currency-page-de.css

335 ms

widgetcontrol.js

widgetcontrol.js

376 ms

js-body

js-body

398 ms

js-enbh

js-enbh

426 ms

currency-page-us.css

currency-page-us.css

427 ms

common-fix.css

common-fix.css

449 ms

slickmin.js

slickmin.js

479 ms

nupd-plugin.js

nupd-plugin.js

497 ms

slick.css

slick.css

500 ms

gtm.js

gtm.js

43 ms

20th-anniversary.svg

20th-anniversary.svg

166 ms

flags-sprite.svg

flags-sprite.svg

98 ms

NG.png

NG.png

98 ms

SG.png

SG.png

96 ms

Currency.svg

Currency.svg

635 ms

Top-Up-Card.svg

Top-Up-Card.svg

163 ms

credit_card.svg

credit_card.svg

185 ms

Blank.gif

Blank.gif

172 ms

verisignseal.png

verisignseal.png

164 ms

bhn-manama1280.png

bhn-manama1280.png

384 ms

arrow-cutout.svg

arrow-cutout.svg

213 ms

map-opaque.png

map-opaque.png

245 ms

all-sprite.png

all-sprite.png

203 ms

LatoLatin-Regular.woff

LatoLatin-Regular.woff

225 ms

icomoon-ultimate.woff

icomoon-ultimate.woff

276 ms

Lato-Italic.woff

Lato-Italic.woff

354 ms

LatoLatin-Light.woff

LatoLatin-Light.woff

310 ms

qatar-website-260-215-px-10.png

qatar-website-260-215-px-10.png

329 ms

qatar-website-260-215-px-9.png

qatar-website-260-215-px-9.png

322 ms

qatar-website-260-215-px-15.png

qatar-website-260-215-px-15.png

339 ms

qatar-website-260-215-px-6.png

qatar-website-260-215-px-6.png

401 ms

iframe_api

iframe_api

81 ms

multi

multi

440 ms

www-widgetapi.js

www-widgetapi.js

4 ms

rendered.png

rendered.png

76 ms

Accessibility Review

travelex.bh accessibility score

66

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

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

SEO Factors

travelex.bh SEO score

80

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

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

High

Tap targets are not sized appropriately

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

travelex.bh

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: