2.6 sec in total
408 ms
1.7 sec
418 ms
Welcome to eyekon.ch homepage info - get ready to check Eyekon best content right away, or after learning these important things about eyekon.ch
Wir finden nachhaltige Lösungen, die Sie weiterbringen. An der Schnittstelle von Mensch, Marke und Maschine.
Visit eyekon.chWe analyzed Eyekon.ch page load time and found that the first response time was 408 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
eyekon.ch performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value9.0 s
1/100
25%
Value9.6 s
11/100
10%
Value2,200 ms
6/100
30%
Value0.008
100/100
15%
Value11.1 s
20/100
10%
408 ms
328 ms
103 ms
191 ms
62 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 74% of them (25 requests) were addressed to the original Eyekon.ch, 18% (6 requests) were made to Fast.fonts.net and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Eyekon.ch.
Page size can be reduced by 167.2 kB (11%)
1.6 MB
1.4 MB
In fact, the total size of Eyekon.ch 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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 8.6 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 1.4 kB, which is 12% 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 8.6 kB or 71% of the original size.
Potential reduce by 7.9 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. Eyekon images are well optimized though.
Potential reduce by 67.1 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 67.1 kB or 48% of the original size.
Potential reduce by 83.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. Eyekon.ch needs all CSS files to be minified and compressed as it can save up to 83.6 kB or 83% of the original size.
Number of requests can be reduced by 10 (37%)
27
17
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyekon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
eyekon.ch
408 ms
www.eyekon.ch
328 ms
outdatedbrowser.css
103 ms
style.css
191 ms
75f99e3c-c318-4788-8912-2404c0dd2d6a.css
62 ms
royalslider.css
187 ms
rs-eyekon.css
220 ms
jquery.min.js
81 ms
jquery.easing.min.js
204 ms
jquery.royalslider.min.js
318 ms
scroll-up-bar-eyekon.js
207 ms
header-animation.js
293 ms
functions.js
289 ms
eyekon-lampe-black.svg
301 ms
Stage1_myswitzerland@2x.jpg
982 ms
Stage2_swisscom@2x.jpg
918 ms
Stage3_illusions@2x.jpg
746 ms
teaserbild_eyekon_news_jungfrauregion@2x.jpg
604 ms
teaserbild_jobs_eye_@2x.jpg
502 ms
wirsuchendich.svg
438 ms
projekte_finma_teaser_@2x.jpg
619 ms
projekte_stgt_teaser_@2x.jpg
1001 ms
illu_footer_twitter_@2x.png
706 ms
logo_footer.svg
724 ms
plus-hover.svg
598 ms
icons_footer_@2x.png
592 ms
bcf54343-d033-41ee-bbd7-2b77df3fe7ba.woff
28 ms
60be5c39-863e-40cb-9434-6ebafb62ab2b.woff
115 ms
530dee22-e3c1-4e9f-bf62-c31d510d9656.woff
114 ms
14ff6081-326d-4dae-b778-d7afa66166fc.woff
115 ms
a0d9d2cb-f057-4e8d-a957-27853630f58e.woff
115 ms
catalog-regular-webfont.woff
615 ms
analytics.js
78 ms
collect
22 ms
eyekon.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
Links do not have a discernible name
eyekon.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
eyekon.ch SEO score
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 Eyekon.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 Eyekon.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.
eyekon.ch
Open Graph description is not detected on the main page of Eyekon. 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: