8.6 sec in total
Visit icorner.ch now to see the best up-to-date Icorner content for Switzerland and also check out these interesting facts you probably never knew about icorner.ch
iCornèr: Log in or register here to access all the data on your Cornèrcard.Visit icorner.ch
We analyzed Icorner.ch page load time and found that the first response time was 539 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
icorner.ch performance score
Our browser made a total of 17 requests to load all elements on the main page. We found that 12% of them (2 requests) were addressed to the original Icorner.ch, 88% (15 requests) were made to Login.icorner.ch. The less responsive or slowest element that took the longest time to load (840 ms) belongs to the original domain Icorner.ch.
Page size can be reduced by 113.1 kB (53%)
Potential reduce by 5.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 5.1 kB or 64% of the original size.
Potential reduce by 2.3 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. Icorner images are well optimized though.
Potential reduce by 91.3 kB
Potential reduce by 14.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. Icorner.ch needs all CSS files to be minified and compressed as it can save up to 14.4 kB or 82% of the original size.
Number of requests can be reduced by 3 (21%)
icorner.ch accessibility score
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.
ARIA progressbar elements do not have accessible names.
These are opportunities to improve the legibility of your content.
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.
Image elements do not have [alt] attributes
Links do not have a discernible name
These items highlight common accessibility best practices.
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
These are opportunities to improve keyboard navigation in your application.
Some elements have a [tabindex] value greater than 0
icorner.ch best practices score
Trust and Safety
Does not use HTTPS
Ensure CSP is effective against XSS attacks
Browser errors were logged to the console
Page has valid source maps
icorner.ch SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have [alt] attributes
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/).
Document uses legible font sizes
Tap targets are not sized appropriately
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Icorner.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 Icorner.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.
Open Graph description is not detected on the main page of Icorner. 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: