Tools & Wizards About Us
travelex.com.om screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% 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.com.om

Currency Exchange & Travel Money at Great Rates | Travelex OM

Page Load Speed

2.7 sec in total

First Response

149 ms

Resources Loaded

2.4 sec

Page Rendered

191 ms

travelex.com.om screenshot

About Website

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

Order 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.com.om

Key Findings

We analyzed Travelex.com.om page load time and found that the first response time was 149 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.com.om performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value470 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.493

17/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

travelex.com.om

149 ms

www.travelex.com.om

469 ms

css

148 ms

css-om

831 ms

js-head

297 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 89% of them (40 requests) were addressed to the original Travelex.com.om, 4% (2 requests) were made to Youtube.com and 2% (1 request) were made to Buy.travelex.com.om. The less responsive or slowest element that took the longest time to load (831 ms) belongs to the original domain Travelex.com.om.

Page Optimization Overview & Recommendations

Page size can be reduced by 99.3 kB (12%)

Content Size

819.9 kB

After Optimization

720.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Travelex.com.om main page is 819.9 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 707.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 62.6 kB

  • Original 77.7 kB
  • After minification 64.2 kB
  • After compression 15.1 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.5 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 62.6 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 35.8 kB

  • Original 707.3 kB
  • After minification 671.5 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

-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.com.om has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (48%)

Requests Now

31

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 31 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 10 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.com.om

travelex.com.om

149 ms

www.travelex.com.om

www.travelex.com.om

469 ms

css

css

148 ms

css-om

css-om

831 ms

js-head

js-head

297 ms

widgets.js

widgets.js

401 ms

common-fix.css

common-fix.css

297 ms

ca-footer.css

ca-footer.css

215 ms

slick.css

slick.css

309 ms

rootlevelcssom.css

rootlevelcssom.css

298 ms

currency-page-de.css

currency-page-de.css

294 ms

widgetcontrol.js

widgetcontrol.js

372 ms

js-body

js-body

380 ms

js-om

js-om

411 ms

currency-page-us.css

currency-page-us.css

381 ms

common-fix.css

common-fix.css

452 ms

slickmin.js

slickmin.js

463 ms

nupd-plugin.js

nupd-plugin.js

463 ms

slick.css

slick.css

487 ms

gtm.js

gtm.js

101 ms

20yomanlogo.svg

20yomanlogo.svg

184 ms

flags-sprite.svg

flags-sprite.svg

95 ms

NG.png

NG.png

94 ms

SG.png

SG.png

97 ms

Currency.svg

Currency.svg

182 ms

Top-Up-Card.svg

Top-Up-Card.svg

632 ms

credit_card.svg

credit_card.svg

205 ms

Blank.gif

Blank.gif

182 ms

verisignseal.png

verisignseal.png

189 ms

omanheroimage.jpg

omanheroimage.jpg

250 ms

arrow-cutout.svg

arrow-cutout.svg

211 ms

map-opaque.png

map-opaque.png

246 ms

all-sprite.png

all-sprite.png

195 ms

LatoLatin-Regular.woff

LatoLatin-Regular.woff

241 ms

icomoon-ultimate.woff

icomoon-ultimate.woff

270 ms

Lato-Italic.woff

Lato-Italic.woff

406 ms

LatoLatin-Light.woff

LatoLatin-Light.woff

319 ms

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

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

277 ms

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

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

381 ms

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

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

331 ms

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

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

349 ms

iframe_api

iframe_api

62 ms

multi

multi

344 ms

www-widgetapi.js

www-widgetapi.js

4 ms

rendered.png

rendered.png

76 ms

Accessibility Review

travelex.com.om 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.com.om 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.com.om 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

    AR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Travelex.com.om can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Arabic language. Our system also found out that Travelex.com.om 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.com.om

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: