Tools & Wizards About Us
entex.ch screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

entex.ch

entex GmbH, 8835 Feusisberg, Softwareentwicklung, Webdesign, Support, Microsoft 365, IP-Kameras

Page Load Speed

7.2 sec in total

First Response

640 ms

Resources Loaded

6.4 sec

Page Rendered

165 ms

entex.ch screenshot

About Website

Click here to check amazing Entex content for Turkey. Otherwise, check out these important facts you probably never knew about entex.ch

Ihr IT-Partner für Webdesign, Softwareentwicklung und PC- und Mail-Support in Feusisberg SZ und Umgebung. entex GmbH, Firststrasse 15, CH-8835 Feusisberg.

Visit entex.ch

Key Findings

We analyzed Entex.ch page load time and found that the first response time was 640 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

entex.ch performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.191

64/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

entex.ch

640 ms

entex.ch

619 ms

www.entex.ch

1403 ms

js

68 ms

default.css

643 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 75% of them (53 requests) were addressed to the original Entex.ch, 13% (9 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Entex.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 429.1 kB (29%)

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Entex.ch main page is 1.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. 55% of websites need less resources to load. Javascripts take 606.7 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 68.9 kB

  • Original 102.6 kB
  • After minification 93.3 kB
  • After compression 33.7 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 68.9 kB or 67% of the original size.

Image Optimization

-3%

Potential reduce by 18.6 kB

  • Original 548.3 kB
  • After minification 529.8 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. Entex images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 244.1 kB

  • Original 606.7 kB
  • After minification 606.6 kB
  • After compression 362.5 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 244.1 kB or 40% of the original size.

CSS Optimization

-43%

Potential reduce by 97.5 kB

  • Original 226.6 kB
  • After minification 225.0 kB
  • After compression 129.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. Entex.ch needs all CSS files to be minified and compressed as it can save up to 97.5 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (67%)

Requests Now

54

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Entex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

entex.ch

entex.ch

640 ms

entex.ch

entex.ch

619 ms

www.entex.ch

www.entex.ch

1403 ms

js

js

68 ms

default.css

default.css

643 ms

module.css

module.css

628 ms

skin.css

skin.css

872 ms

Ozone.css

Ozone.css

1019 ms

HomePage.css

HomePage.css

863 ms

container.css

container.css

742 ms

portal.css

portal.css

755 ms

home.css

home.css

826 ms

rateit.css

rateit.css

853 ms

Style.css

Style.css

921 ms

jquery.js

jquery.js

1300 ms

eds2.2.3.js

eds2.2.3.js

1167 ms

jquery-migrate.js

jquery-migrate.js

982 ms

jquery-ui.js

jquery-ui.js

1342 ms

css

css

28 ms

css

css

42 ms

css

css

47 ms

jquery.mmenu.css

jquery.mmenu.css

1036 ms

EasyDnnSolutions_1.1_2.2.js

EasyDnnSolutions_1.1_2.2.js

1107 ms

WebResource.axd

WebResource.axd

1015 ms

toggle.js

toggle.js

1035 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

1247 ms

jquery.themepunch.revolution.merge.js

jquery.themepunch.revolution.merge.js

1342 ms

dnn.modalpopup.js

dnn.modalpopup.js

1166 ms

jquery.rateit_2.2.js

jquery.rateit_2.2.js

1171 ms

dnncore.js

dnncore.js

1290 ms

script.js

script.js

1443 ms

custom.js

custom.js

1350 ms

initWidgets.js

initWidgets.js

1342 ms

dnngo-xplugin.js

dnngo-xplugin.js

1469 ms

cookieinfo.min.js

cookieinfo.min.js

63 ms

bootstrap.css

bootstrap.css

689 ms

animation.css

animation.css

781 ms

shortcodes.css

shortcodes.css

788 ms

font-awesome.min.css

font-awesome.min.css

564 ms

css

css

16 ms

entex-logo3-min.jpg

entex-logo3-min.jpg

187 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

52 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

163 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

178 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

178 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

848 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

213 ms

4iCs6KVjbNBYlgoKfw7z.ttf

4iCs6KVjbNBYlgoKfw7z.ttf

177 ms

4iCv6KVjbNBYlgoCjC3jsGyI.ttf

4iCv6KVjbNBYlgoCjC3jsGyI.ttf

177 ms

4iCv6KVjbNBYlgoC1CzjsGyI.ttf

4iCv6KVjbNBYlgoC1CzjsGyI.ttf

178 ms

abstract-header1.jpg

abstract-header1.jpg

2077 ms

abstract-header2.jpg

abstract-header2.jpg

838 ms

120120p436EDNthumbimg-fuss0001.jpg

120120p436EDNthumbimg-fuss0001.jpg

720 ms

120120p436EDNthumbimg-hr0001.jpg

120120p436EDNthumbimg-hr0001.jpg

279 ms

120120p436EDNthumbimg-waz01.jpg

120120p436EDNthumbimg-waz01.jpg

322 ms

ip-kamera.jpg

ip-kamera.jpg

499 ms

backup.jpg

backup.jpg

446 ms

facebook_button.png

facebook_button.png

556 ms

rss.png

rss.png

607 ms

webmail.htm

webmail.htm

664 ms

blank.png

blank.png

713 ms

h.js

h.js

174 ms

GdZvpAq9shJukTEvSQbePw.woff

GdZvpAq9shJukTEvSQbePw.woff

152 ms

hpORcvLZtemlH8gI-1S-7hsxEYwM7FgeyaSgU71cLG0.woff

hpORcvLZtemlH8gI-1S-7hsxEYwM7FgeyaSgU71cLG0.woff

170 ms

DotNetNukeAjaxShared.js

DotNetNukeAjaxShared.js

738 ms

loader.gif

loader.gif

688 ms

timer.png

timer.png

682 ms

revicons.woff

revicons.woff

759 ms

2609c3b674

2609c3b674

27 ms

log

log

26 ms

widgets.js

widgets.js

155 ms

Accessibility Review

entex.ch accessibility score

74

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

entex.ch best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

entex.ch SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Entex.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 Entex.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.

Social Sharing Optimization

entex.ch

Open Graph description is not detected on the main page of Entex. 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: