6.5 sec in total
1.6 sec
4.5 sec
413 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 1.6 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
travelex.de performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value8.1 s
2/100
25%
Value8.6 s
17/100
10%
Value2,300 ms
5/100
30%
Value0.88
3/100
15%
Value16.4 s
5/100
10%
1618 ms
1122 ms
1060 ms
1371 ms
536 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 42% of them (33 requests) were addressed to the original Travelex.de, 9% (7 requests) were made to F.fontdeck.com and 8% (6 requests) were made to Cfms.mopinion.nl. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Travelex.de.
Page size can be reduced by 698.8 kB (56%)
1.3 MB
557.8 kB
In fact, the total size of Travelex.de main page is 1.3 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. Javascripts take 641.1 kB which makes up the majority of the site volume.
Potential reduce by 65.2 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 14.2 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 65.2 kB or 79% of the original size.
Potential reduce by 13.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.
Potential reduce by 458.4 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 458.4 kB or 71% of the original size.
Potential reduce by 161.7 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.de needs all CSS files to be minified and compressed as it can save up to 161.7 kB or 83% of the original size.
Number of requests can be reduced by 37 (54%)
68
31
The browser has sent 68 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 23 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.travelex.de
1618 ms
css
1122 ms
js-head
1060 ms
widgets.js
1371 ms
opentag-123868-2157633.js
536 ms
574760015.js
219 ms
de-footer.css
513 ms
custom-taglines.css
390 ms
exchange-with-confidence.css
390 ms
exchanging-currency-is-easy.css
408 ms
todays-best-exchange-rates.css
494 ms
tber-de.js
489 ms
js-body
624 ms
webfont.js
40 ms
46781.js
135 ms
ojILptV8UvnJjSQefItxrOuMsIQCnj0XPyZWR03vG7zUYd+8net1RPWqHwCVa0YEav7UAH5jfU7M66pMZvjx6IL3Zu8gdcdzjI2ly6Gv8to6TpuzxMSIhpEIueYeWyajnhZOmFTmXzq6bKCV+Qf1aaIYhywP1HiCr.woff
163 ms
OCeqBgRtSL82VoY0jWFc+WRdgNNEXNoYTonFepap.woff
359 ms
DdeG7TA8E9cz365O0vGd3j9LWgSV0EAYJNuX8KXCHCJPuXl.woff
359 ms
F5NuG+aRs5Wt4UrmY3mC02zCUymMy2rb4ym.woff
359 ms
QlVNRV9pQWoABfQtC6RC7R3y264XYW8xE5Mrdgu2+0Obzu3keGEmaiINX8zfKwr7dnN7zvPtZEd8SmJPkGct2ox7BEqkA2CVdz3Xte4BW70bHJ1U3opTn+ORIEXbHI9HC4UnBjDbMl1DtNSUiT1ZNzeM4xHPjyyixgUEuHRQvhERjmmzVZOMj4hM.woff
359 ms
qtracker-v3-min.js
275 ms
smartserve-4302.js
991 ms
XBF31D9D83FE2447C3C6099C13E5C9975.js
924 ms
travelex-logo.png
259 ms
phone.png
246 ms
arrow-cutout.png
244 ms
1536779_m.jpg
244 ms
preisversprechen.jpg
389 ms
fremdwahrung.jpg
430 ms
promo-3.jpg
414 ms
london-white.png
387 ms
usa-white.png
387 ms
canada-white.png
386 ms
palm-icon.png
520 ms
verisignseal.png
520 ms
visa-icon.png
519 ms
mastercard-icon.png
517 ms
banku-berweisung.png
539 ms
dhl.png
539 ms
go.png
622 ms
homepage-banner-de.jpg
838 ms
icomoon-ultimate.woff
568 ms
d3CoyPGpJgOG3WBQZkKsW.woff
275 ms
map-opaque.png
634 ms
exchange-with-confidence-bg.jpg
1084 ms
iframe_api
231 ms
gtm.js
250 ms
multi
607 ms
current
662 ms
current
663 ms
current
662 ms
t2
405 ms
www-widgetapi.js
18 ms
fbevents.js
195 ms
analytics.js
15 ms
mopinion.travelex.css
679 ms
mopinion.travelex.custom.js
690 ms
linkid.js
37 ms
ec.js
49 ms
collect
63 ms
collect
7 ms
collect
51 ms
ga-audiences
33 ms
ga-audiences
35 ms
105 ms
collect
11 ms
GetAccessToken
107 ms
icon-question-blue.png
272 ms
home-radio.png
260 ms
118 ms
json2.js
85 ms
tag2
100 ms
feedbacktxt.png
89 ms
feedback.png
83 ms
style.css
42 ms
trustbadgeIE8.css
50 ms
badge_compressed.png
4 ms
bg_small.png
22 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
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
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.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: