7.5 sec in total
1.4 sec
5.8 sec
341 ms
Visit eglin.ch now to see the best up-to-date Eglin content for Switzerland and also check out these interesting facts you probably never knew about eglin.ch
Die Eglin Elektro bietet Ihnen professionelle Lösungen & Dienstleistungen in den Bereichen Elektroinstallation, ICT & Gebäudeautomation, insbesondere auch Photovoltaik und E-Mobilität
Visit eglin.chWe analyzed Eglin.ch page load time and found that the first response time was 1.4 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eglin.ch performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value3.9 s
53/100
25%
Value5.7 s
50/100
10%
Value430 ms
65/100
30%
Value0.006
100/100
15%
Value6.8 s
55/100
10%
1386 ms
351 ms
99 ms
319 ms
26 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 82% of them (31 requests) were addressed to the original Eglin.ch, 11% (4 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Eglin.ch.
Page size can be reduced by 319.5 kB (44%)
724.3 kB
404.8 kB
In fact, the total size of Eglin.ch main page is 724.3 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. 40% of websites need less resources to load. Images take 324.5 kB which makes up the majority of the site volume.
Potential reduce by 18.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. 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 18.6 kB or 77% of the original size.
Potential reduce by 14.7 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. Eglin images are well optimized though.
Potential reduce by 226.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 226.2 kB or 75% of the original size.
Potential reduce by 60.1 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. Eglin.ch needs all CSS files to be minified and compressed as it can save up to 60.1 kB or 80% of the original size.
Number of requests can be reduced by 3 (10%)
31
28
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eglin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
eglin.ch
1386 ms
351 ms
ffae9d5f.css
99 ms
font-awesome.min.css
319 ms
css
26 ms
mootools-core.js
550 ms
a0380a04.js
280 ms
logo.svg
203 ms
walk.svg
205 ms
tools.svg
202 ms
1_elektro.jpg
234 ms
3_communication.jpg
368 ms
4_gebaeudeautomation.jpg
369 ms
4_immobilien.jpg
966 ms
bulb.svg
865 ms
phone.svg
202 ms
house-plus.svg
293 ms
house.svg
325 ms
news-default.jpg
1021 ms
jobs-default.jpg
526 ms
01_small.jpg
458 ms
map.png
462 ms
footer-eglin.png
551 ms
bulb.svg
555 ms
phone.svg
619 ms
house-plus.svg
645 ms
house.svg
648 ms
TeamViewerWin.svg
712 ms
TeamViewerMac.svg
737 ms
facebook.png
740 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
24 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
25 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
8 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
30 ms
fontawesome-webfont.woff
677 ms
analytics.js
27 ms
collect
20 ms
print.css
94 ms
eglin.ch accessibility score
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
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.
eglin.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
eglin.ch 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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eglin.ch can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eglin.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.
eglin.ch
Open Graph description is not detected on the main page of Eglin. 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: