2.8 sec in total
184 ms
2.2 sec
374 ms
Welcome to travelex.de homepage info - get ready to check Travelex best content for Germany right away, or after learning these important things about travelex.de
Kaufen Sie Ihre Devisen online und holen Sie sie bequem in einer unserer Filialen ab. Nutzen Sie unseren Währungsrechner, um Wechselkurse von Reisezahlungsmitteln zu vergleichen.
Visit travelex.deWe analyzed Travelex.de page load time and found that the first response time was 184 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.
travelex.de performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value14.5 s
0/100
25%
Value10.6 s
7/100
10%
Value2,160 ms
6/100
30%
Value0.391
26/100
15%
Value15.3 s
7/100
10%
184 ms
677 ms
294 ms
316 ms
603 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 79% of them (45 requests) were addressed to the original Travelex.de, 7% (4 requests) were made to Api.travelex.net and 5% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (677 ms) belongs to the original domain Travelex.de.
Page size can be reduced by 196.7 kB (12%)
1.6 MB
1.4 MB
In fact, the total size of Travelex.de 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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 101.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 18.8 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 101.5 kB or 78% of the original size.
Potential reduce by 94.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.
Potential reduce by 204 B
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.
Potential reduce by 216 B
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.de has all CSS files already compressed.
Number of requests can be reduced by 18 (39%)
46
28
The browser has sent 46 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 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
travelex.de
184 ms
www.travelex.de
677 ms
css
294 ms
css-dede
316 ms
js-head
603 ms
widgets.js
373 ms
otSDKStub.js
31 ms
de-footer.css
276 ms
de-common.css
280 ms
custom-taglines.css
347 ms
exchange-with-confidence.css
352 ms
exchanging-currency-is-easy.css
366 ms
todays-best-exchange-rates.css
372 ms
tber-de.js
379 ms
js-body
138 ms
js-dede
170 ms
widgetcontrol.js
123 ms
gtm.js
128 ms
07e8750a-31d9-4806-bb22-ca99c5154b59.json
48 ms
XBF31D9D83FE2447C3C6099C13E5C9975.js
444 ms
travelex-logo-old.svg
117 ms
flags-sprite.svg
119 ms
NG.png
113 ms
SG.png
121 ms
all-sprite.png
118 ms
Currency.svg
264 ms
Top-Up-Card.svg
264 ms
credit_card.svg
264 ms
Blank.gif
256 ms
verisignseal.png
257 ms
home-hero-desktop-1280x485.jpg
244 ms
arrow-cutout.svg
241 ms
otBannerSdk.js
45 ms
map-opaque.png
293 ms
exchange-with-confidence-bg.jpg
368 ms
germany-sprite-img.png
294 ms
LatoLatin-Regular.woff
295 ms
icomoon-ultimate.woff
294 ms
Lato-Italic.woff
374 ms
LatoLatin-Light.woff
367 ms
tvx-hp-argument-box-612-x-408-1.png
433 ms
rueckkaufgarantie.jpg
292 ms
tvx-hp-argument-box-612-x-408-5.png
360 ms
homedelivery.jpg
364 ms
usa-white.png
372 ms
london-white.png
369 ms
canada-white.png
372 ms
online-reisemagazine-virtuelle-reisen.jpg
439 ms
online-reisemagazine-reisen-haelt-gesund.jpg
444 ms
online-reisemagazine-reiseinspirationen.jpg
447 ms
online-reisemagazine-online-reisefuehrer.jpg
449 ms
iframe_api
87 ms
multi
430 ms
current
421 ms
current
423 ms
current
423 ms
www-widgetapi.js
5 ms
travelex.de 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
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
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.de 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.de SEO score
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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Travelex.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Travelex.de 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.de
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: