3.2 sec in total
303 ms
2.7 sec
121 ms
Visit travelcash.ch now to see the best up-to-date Travelcash content for Switzerland and also check out these interesting facts you probably never knew about travelcash.ch
Travel - Die kostenlose Prepaid Kreditkarte ✓ 0,-- CHF Jahresgebühr ✓ Hotels mit bis zu 50 % Rabatt ✓ Weltweit einsetzbar ✓ ▷ Hier bestellen!
Visit travelcash.chWe analyzed Travelcash.ch page load time and found that the first response time was 303 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
travelcash.ch performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value16.5 s
0/100
25%
Value16.1 s
0/100
10%
Value880 ms
32/100
30%
Value0.225
55/100
15%
Value14.4 s
9/100
10%
303 ms
699 ms
896 ms
109 ms
219 ms
Our browser made a total of 23 requests to load all elements on the main page. We found that 9% of them (2 requests) were addressed to the original Travelcash.ch, 78% (18 requests) were made to Swissbankers.ch and 9% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (896 ms) relates to the external source Swissbankers.ch.
Page size can be reduced by 236.3 kB (43%)
550.3 kB
314.0 kB
In fact, the total size of Travelcash.ch main page is 550.3 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. 20% of websites need less resources to load. Javascripts take 254.3 kB which makes up the majority of the site volume.
Potential reduce by 19.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 19.1 kB or 74% of the original size.
Potential reduce by 6.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. Travelcash images are well optimized though.
Potential reduce by 179.8 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 179.8 kB or 71% of the original size.
Potential reduce by 30.6 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. Travelcash.ch needs all CSS files to be minified and compressed as it can save up to 30.6 kB or 73% of the original size.
Number of requests can be reduced by 10 (50%)
20
10
The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Travelcash. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
travelcash.ch
303 ms
www.travelcash.ch
699 ms
travel-cash.aspx
896 ms
bundle_-1915494229_5_2_7_0_28.min.css
109 ms
bundle_1431711094_1_2_7_0_28.min.js
219 ms
bundle_-901682192_5_2_7_0_28.min.js
391 ms
jquery.bxslider.css
303 ms
bundle_-2135692906_3_2_7_0_28.min.css
301 ms
jquery.bxslider.js
412 ms
DESGetFiles.axd
326 ms
WebResource.axd
327 ms
WebResource.axd
402 ms
DESGetFiles.axd
507 ms
ga.js
16 ms
Logo_SwissBankers_TravelCash.png
128 ms
WamsResources.ashx
418 ms
WamsResources.ashx
323 ms
__utm.gif
11 ms
plus.png
101 ms
search.png
107 ms
list-image.png
98 ms
trackingCode.js
139 ms
bx_loader.gif
108 ms
travelcash.ch accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
travelcash.ch 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
travelcash.ch SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Travelcash.ch 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 Travelcash.ch 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.
travelcash.ch
Open Graph description is not detected on the main page of Travelcash. 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: