3.4 sec in total
322 ms
2.3 sec
742 ms
Click here to check amazing Cyfex content for Switzerland. Otherwise, check out these important facts you probably never knew about cyfex.com
Visit cyfex.comWe analyzed Cyfex.com page load time and found that the first response time was 322 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
cyfex.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value4.7 s
32/100
25%
Value6.0 s
47/100
10%
Value230 ms
87/100
30%
Value0.01
100/100
15%
Value6.1 s
63/100
10%
322 ms
679 ms
106 ms
207 ms
213 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 93% of them (37 requests) were addressed to the original Cyfex.com, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (841 ms) belongs to the original domain Cyfex.com.
Page size can be reduced by 149.1 kB (20%)
754.0 kB
604.9 kB
In fact, the total size of Cyfex.com main page is 754.0 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. 30% of websites need less resources to load. Images take 556.2 kB which makes up the majority of the site volume.
Potential reduce by 19.8 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.8 kB or 76% of the original size.
Potential reduce by 36.1 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. Cyfex images are well optimized though.
Potential reduce by 45.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 45.2 kB or 41% of the original size.
Potential reduce by 48.0 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. Cyfex.com needs all CSS files to be minified and compressed as it can save up to 48.0 kB or 79% of the original size.
Number of requests can be reduced by 8 (24%)
34
26
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cyfex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
cyfex.com
322 ms
www.cyfex.com
679 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
106 ms
css_7McI5_-ELBMFdDOct0s5hIqd08VjnM__PxKtxOorbig.css
207 ms
css_-rZv9tPx8C3Vlu1KRwGgIaKiwEb2I6yZxRLa_7O3kjQ.css
213 ms
css_-TxdKRXoS3aZg_7qoEMhgOgnYZXwCVAfXDMftuuEG0o.css
208 ms
jquery.min.js
32 ms
js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js
228 ms
js_oVRnYMj7FHgy6RbaTWJ1eTqF4Z8uHY20z0ZMT3lGNiU.js
212 ms
js_TzmnyvOYGi0JLxwLqCnSOQ-25hLOlXG13O4k_yeq9UE.js
233 ms
ga.js
136 ms
body_bg.jpg
105 ms
site_bg.jpg
208 ms
logo_main.png
106 ms
box_white_bg_header.png
210 ms
loading.gif
315 ms
hader_slider_1.jpg
316 ms
hader_slider_home_1.jpg
411 ms
hader_slider_2_1.jpg
415 ms
hader_slider_2_2.jpg
615 ms
cyfex-ag-istockphoto-000019033569_m_2.jpg
623 ms
cyfex-ag-istock_000017055825_0.jpg
727 ms
arrow_header_slider.png
421 ms
box_white_bg_shadow_right.png
515 ms
cyfex-start1b-138310685_75-two-young-doctors-examining-dentures_0.jpg
520 ms
testimonial_quote_small.png
524 ms
dental.jpg
619 ms
hearing.jpg
625 ms
engineering.jpg
627 ms
link_arrow_blue.png
718 ms
logo_footer.png
724 ms
bg_white_trans.png
724 ms
rotator-black.png
728 ms
pause-black.png
730 ms
museo-300-webfont.woff
821 ms
museo-500-webfont.woff
841 ms
museosans-300-webfont.woff
839 ms
museosans-500-webfont.woff
839 ms
__utm.gif
16 ms
css_e0Oi8I1L8cGJ7KxcUbimLkO-ivlPDoZXuBZMWKAz5GY.css
106 ms
cyfex.com 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.
cyfex.com 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
cyfex.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cyfex.com 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 Cyfex.com 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.
cyfex.com
Open Graph description is not detected on the main page of Cyfex. 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: