Tools & Wizards About Us
innocard.ch screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

innocard.ch

Secure cashless payment transactions with Innocard AG

Page Load Speed

7.5 sec in total

First Response

240 ms

Resources Loaded

7.1 sec

Page Rendered

198 ms

innocard.ch screenshot

About Website

Click here to check amazing Innocard content for Switzerland. Otherwise, check out these important facts you probably never knew about innocard.ch

With us you get everything from a single source: latest card terminals with secure card acceptance and customer-oriented services.

Visit innocard.ch

Key Findings

We analyzed Innocard.ch page load time and found that the first response time was 240 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

innocard.ch performance score

0

Network Requests Diagram

home

240 ms

09a70d38-1997-4802-b711-29d77477abec.css

56 ms

56c2f06479d2c8e7a82ba1c18d554029.css

124 ms

base.css

207 ms

custom.css

204 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 63% of them (32 requests) were addressed to the original Innocard.ch, 10% (5 requests) were made to My.clickdesk.com and 8% (4 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (6.3 sec) relates to the external source Tracking.globonet.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 703.0 kB (53%)

Content Size

1.3 MB

After Optimization

622.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Innocard.ch 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 667.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 97.5 kB

  • Original 125.0 kB
  • After minification 115.2 kB
  • After compression 27.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. 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 97.5 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 5.1 kB

  • Original 377.7 kB
  • After minification 372.6 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. Innocard images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 470.9 kB

  • Original 667.1 kB
  • After minification 667.0 kB
  • After compression 196.2 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 470.9 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 129.5 kB

  • Original 155.2 kB
  • After minification 142.8 kB
  • After compression 25.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. Innocard.ch needs all CSS files to be minified and compressed as it can save up to 129.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (45%)

Requests Now

47

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Innocard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

home

home

240 ms

09a70d38-1997-4802-b711-29d77477abec.css

09a70d38-1997-4802-b711-29d77477abec.css

56 ms

56c2f06479d2c8e7a82ba1c18d554029.css

56c2f06479d2c8e7a82ba1c18d554029.css

124 ms

base.css

base.css

207 ms

custom.css

custom.css

204 ms

2f3d7f51b376f7eae0c8f250c1132d9a.css

2f3d7f51b376f7eae0c8f250c1132d9a.css

196 ms

5bf758551b6f9047a80635394d20c09b.css

5bf758551b6f9047a80635394d20c09b.css

208 ms

37d563a75ec42e45c091ebd91390c558.js

37d563a75ec42e45c091ebd91390c558.js

356 ms

ef92412b1a59c063f92e62d4b7db9ba2.js

ef92412b1a59c063f92e62d4b7db9ba2.js

222 ms

2e89eb860541651b756c979d59a28526.js

2e89eb860541651b756c979d59a28526.js

298 ms

4f0f3e5eb86f2fd89672c050a5210e3b.js

4f0f3e5eb86f2fd89672c050a5210e3b.js

298 ms

06937797906618dd9619ee0419fce9ff.js

06937797906618dd9619ee0419fce9ff.js

304 ms

5a2f52c1356826cb409befc86560a994.js

5a2f52c1356826cb409befc86560a994.js

313 ms

4bbe361dbd5155f0e346b149289146f9.js

4bbe361dbd5155f0e346b149289146f9.js

321 ms

svg-morpheus.js

svg-morpheus.js

1667 ms

piwik.js

piwik.js

6296 ms

analytics.js

analytics.js

8 ms

collect

collect

14 ms

0_left_iconset.svg

0_left_iconset.svg

148 ms

0_right_iconset.svg

0_right_iconset.svg

153 ms

1_left_iconset.svg

1_left_iconset.svg

146 ms

1_right_iconset.svg

1_right_iconset.svg

151 ms

2_left_iconset.svg

2_left_iconset.svg

147 ms

2_right_iconset.svg

2_right_iconset.svg

144 ms

logo_innocard-en.png

logo_innocard-en.png

316 ms

img.jpg

img.jpg

752 ms

img.jpg

img.jpg

1811 ms

img.jpg

img.jpg

1927 ms

img.jpg

img.jpg

2080 ms

img.jpg

img.jpg

2181 ms

logo.png

logo.png

1903 ms

livechat-new.js

livechat-new.js

34 ms

shim-ext.css

shim-ext.css

836 ms

3.js

3.js

935 ms

form-shim-extend.js

form-shim-extend.js

1042 ms

17.js

17.js

1166 ms

3b15daf5-d7fb-4099-93b9-db20fd26c2fe.woff

3b15daf5-d7fb-4099-93b9-db20fd26c2fe.woff

41 ms

0c0418fe-d324-4ab2-978a-e8201c646ca1.woff

0c0418fe-d324-4ab2-978a-e8201c646ca1.woff

109 ms

icomoon.woff

icomoon.woff

1610 ms

1b99d71c-c066-4ce3-b4af-38dfd9fe3d85.woff

1b99d71c-c066-4ce3-b4af-38dfd9fe3d85.woff

109 ms

livechat-cloud-new.js

livechat-cloud-new.js

30 ms

livechat-v2.js

livechat-v2.js

12 ms

preferences

preferences

238 ms

ajax-loader-cursor.gif

ajax-loader-cursor.gif

139 ms

009bff.css

009bff.css

41 ms

warning.png

warning.png

139 ms

clickdesklogo.png

clickdesklogo.png

75 ms

proactive

proactive

115 ms

1429702530582

1429702530582

71 ms

1455195070180

1455195070180

640 ms

ultra-modern-sprite.png

ultra-modern-sprite.png

9 ms

SEO Factors

innocard.ch SEO score

0

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 Innocard.ch 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 Innocard.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.

Social Sharing Optimization

innocard.ch

Open Graph description is not detected on the main page of Innocard. 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: