5.3 sec in total
627 ms
4.4 sec
260 ms
Click here to check amazing Naef content for Switzerland. Otherwise, check out these important facts you probably never knew about naef.ch
Vous cherchez à louer ou acheter un appartement, une maison en Suisse romande ? Mettez en vente ou en gérance votre bien immobilier avec Naef
Visit naef.chWe analyzed Naef.ch page load time and found that the first response time was 627 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
naef.ch performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value18.7 s
0/100
25%
Value8.7 s
16/100
10%
Value1,870 ms
9/100
30%
Value0.022
100/100
15%
Value21.7 s
1/100
10%
627 ms
696 ms
429 ms
230 ms
911 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 97% of them (77 requests) were addressed to the original Naef.ch, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Naef.ch.
Page size can be reduced by 748.2 kB (30%)
2.5 MB
1.7 MB
In fact, the total size of Naef.ch main page is 2.5 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. 40% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 63.2 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 11.1 kB, which is 14% 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 63.2 kB or 79% of the original size.
Potential reduce by 124.0 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. Naef images are well optimized though.
Potential reduce by 424.3 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 424.3 kB or 73% of the original size.
Potential reduce by 136.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. Naef.ch needs all CSS files to be minified and compressed as it can save up to 136.6 kB or 86% of the original size.
Number of requests can be reduced by 23 (29%)
78
55
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Naef. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
naef.ch
627 ms
default.css
696 ms
skin.css
429 ms
portal.css
230 ms
jquery.min.js
911 ms
jquery-ui.min.js
1491 ms
WebResource.axd
232 ms
Telerik.Web.UI.WebResource.axd
256 ms
dnn.modalpopup.js
455 ms
dnncore.js
577 ms
AC_RunActiveContent.js
544 ms
swfobject.js
722 ms
jquery.bxslider.min.js
783 ms
jquery.bxslider.css
854 ms
initWidgets.js
810 ms
skin_inhereted.css
605 ms
jquery-ui-1.8.10.custom.css
611 ms
analytics.js
23 ms
pageBg.png
134 ms
sub_img_0.png
195 ms
sub_img_1.png
216 ms
sub_img_4.png
145 ms
sub_img_6.png
242 ms
sub_img_3.png
164 ms
sub_img_2.png
491 ms
sub_img_5.png
653 ms
sub_img_terrain.png
652 ms
sub-img-vtpromo.png
374 ms
sub_img_publication.png
563 ms
sub_img_0_Group.png
628 ms
sub_img_1_Group.png
761 ms
sub_img_2_Group.png
636 ms
sub_img_3_Group.png
668 ms
fb_sub.png
730 ms
li_sub.png
739 ms
naef_logo.png
745 ms
moncompte.png
767 ms
ae17c87d-c09d-40ed-85d6-53e5fe34bae9_vignette_investissement.png
760 ms
a399cf5e-1318-4b78-83ab-be25a174b2ea_Sans%20titre%201.jpg
822 ms
249abe14-6844-4684-b822-12196e11124f_vignette-%C3%A0-la-une.png
846 ms
12e04625-96bd-4419-9a29-943a508dba1c_Rapport%20DD_homepage.jpg
945 ms
c8f26d58-59d7-4e0d-a5d3-b2880d904b58_L9117.jpg
853 ms
37528c06-87e5-45c2-b35f-4fd6436b029a_L10028.jpg
1001 ms
be7a35d9-2e42-409d-b15a-fec27d505b65_homepage-thumb.png
1179 ms
977b9c2a-f6ea-4d40-980c-9a2ea285a165_L9777.jpg
918 ms
2017eb11-7368-4775-bd51-76a5dcf7a1aa_t%C3%A9l%C3%A9chargement.jpg
943 ms
c0715fad-7170-475c-a501-9dd1c3bf1b62_Image%20exterieur%20N%C2%B01.jpg
1169 ms
ab837c92-22d6-4f44-b5b5-112df515a000_Sans%20titre%201.jpg
1028 ms
948d2ebc-fedc-4c1f-9d20-5139c652135e_Villas-Prechautagne-EXTc.jpg
1074 ms
d35c1100-1b0b-475a-86a2-4e45fe34f305_26139.jpg
1043 ms
42b143d2-e19b-4c2f-8c9d-8b450bbe167b_Sans%20titre%201.jpg
1383 ms
6c5e98f7-eb80-4dc7-acb8-cdeb1e98dcf7_26334.jpg
1115 ms
030aa21a-a9e5-4e1c-90a7-dc3a9f6eb09a_26519.jpg
1136 ms
fdd5d619-6bc5-4825-98a6-c55ff61cbbb1_homepage_thumb.png
1239 ms
collect
16 ms
DotNetNukeAjaxShared.js
1089 ms
db706ba4-f3a9-430e-b3a2-853b0ef0de95_26656.jpg
1126 ms
66187b14-1636-4cef-b56d-dc0342984492_26489.jpg
1109 ms
pop-up_3.png
2292 ms
facebook-logo.png
1182 ms
linkedin-logo.jpg
1714 ms
logo_sgs.png
1580 ms
logo_enaef.png
928 ms
headBg0.jpg
1740 ms
subm_bg.png
1575 ms
subDummy.png
1566 ms
bg.png
1400 ms
main_but_bg.png
1561 ms
break.png
1465 ms
lb_prestige_bg.png
1556 ms
home_box_bg.png
1547 ms
home_bg_image.png
1554 ms
plus_ico.png
1534 ms
home_box_end.png
1618 ms
litebox_window_bg.png
1602 ms
foo_line.png
1555 ms
footer_break.png
1536 ms
baloon_close_button.png
1547 ms
widgets.js
1254 ms
naef.ch accessibility score
ARIA
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.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
naef.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
Missing source maps for large first-party JavaScript
naef.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Naef.ch can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Naef.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.
naef.ch
Open Graph description is not detected on the main page of Naef. 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: