Tools & Wizards About Us
in.endress.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

in.endress.com

Flow, level, liquid analysis, optical analysis, pressure, temperature measurement, software and system products | Endress+Hauser

Page Load Speed

11.6 sec in total

First Response

3.2 sec

Resources Loaded

7.6 sec

Page Rendered

772 ms

in.endress.com screenshot

About Website

Welcome to in.endress.com homepage info - get ready to check In Endress best content for Malaysia right away, or after learning these important things about in.endress.com

People for Process Automation offer you solutions and products in flow, level, liquid analysis, optical analysis, pressure, temperature measurement, software and system products

Visit in.endress.com

Key Findings

We analyzed In.endress.com page load time and found that the first response time was 3.2 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

in.endress.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.459

19/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

en

3233 ms

components-53ca815d.css

35 ms

elements-8db200d9.css

42 ms

main-2626faa4.css

41 ms

main_prefixed-0a9545c7.css

60 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 99% of them (72 requests) were addressed to the original In.endress.com, 1% (1 request) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain In.endress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 397.0 kB (11%)

Content Size

3.6 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of In.endress.com main page is 3.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 375.4 kB

  • Original 407.3 kB
  • After minification 372.3 kB
  • After compression 31.9 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 375.4 kB or 92% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.8 MB
  • After minification 2.8 MB

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. In Endress images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 74 B

  • Original 277.7 kB
  • After minification 277.7 kB
  • After compression 277.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-20%

Potential reduce by 21.6 kB

  • Original 109.9 kB
  • After minification 88.6 kB
  • After compression 88.3 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. In.endress.com needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 20% of the original size.

Requests Breakdown

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

Requests Now

59

After Optimization

38

  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of In Endress. 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 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

en

en

3233 ms

components-53ca815d.css

components-53ca815d.css

35 ms

elements-8db200d9.css

elements-8db200d9.css

42 ms

main-2626faa4.css

main-2626faa4.css

41 ms

main_prefixed-0a9545c7.css

main_prefixed-0a9545c7.css

60 ms

EH_Logo-d9672165.svg

EH_Logo-d9672165.svg

46 ms

eh-menu-1dabb5ad.svg

eh-menu-1dabb5ad.svg

48 ms

eh-cart-b25d46b3.svg

eh-cart-b25d46b3.svg

46 ms

nebp-bootstrap-9b367e59.js

nebp-bootstrap-9b367e59.js

24 ms

utag.js

utag.js

76 ms

bottom_start-712491df.js

bottom_start-712491df.js

64 ms

bottom_page_composing-37aa9133.js

bottom_page_composing-37aa9133.js

27 ms

bottom_preview-633c6d95.js

bottom_preview-633c6d95.js

26 ms

eh-arrow-right-4defb12d.svg

eh-arrow-right-4defb12d.svg

27 ms

eh-arrow-down-da966f36.svg

eh-arrow-down-da966f36.svg

26 ms

eh-arrow-left-d7512fc3.svg

eh-arrow-left-d7512fc3.svg

29 ms

eh-user-455a8fed.svg

eh-user-455a8fed.svg

29 ms

eh-cart.svg

eh-cart.svg

1053 ms

eh-cancel-464c9168.svg

eh-cancel-464c9168.svg

27 ms

eh-search-b919ee0f.svg

eh-search-b919ee0f.svg

30 ms

BC-L1-brand-promise.jpg

BC-L1-brand-promise.jpg

66 ms

Yield-l1.jpg

Yield-l1.jpg

85 ms

arrow-new-eb8f1b1b.svg

arrow-new-eb8f1b1b.svg

60 ms

Energy-L1.jpg

Energy-L1.jpg

64 ms

Proline%20Promag%20P%20300%20(5P3B)%20with%20flange%20connections%20for%20process%20applications%20-%20PP01.jpg

Proline%20Promag%20P%20300%20(5P3B)%20with%20flange%20connections%20for%20process%20applications%20-%20PP01.jpg

63 ms

spinner-72511bd6.svg

spinner-72511bd6.svg

62 ms

Proline%20Promass%20Q%20300%20%2F%208Q3B%20with%20flange%20connections%20and%20with%20compact%20transmitter%20-%20PP02.jpg

Proline%20Promass%20Q%20300%20%2F%208Q3B%20with%20flange%20connections%20and%20with%20compact%20transmitter%20-%20PP02.jpg

78 ms

TMT86.jpg

TMT86.jpg

71 ms

Picture-Pool_Liquiphant_FTL63_PP_01.jpg

Picture-Pool_Liquiphant_FTL63_PP_01.jpg

73 ms

Proline%20Promag%20P%20500%20%2F%205P5B%20with%20flange%20connections%20for%20the%20chemical%20industry%20-%20PP04.jpg

Proline%20Promag%20P%20500%20%2F%205P5B%20with%20flange%20connections%20for%20the%20chemical%20industry%20-%20PP04.jpg

77 ms

Proline%20Promass%20Q%20500%20%2F%208Q5B%20with%20flange%20connections%20-%20PP03.jpg

Proline%20Promass%20Q%20500%20%2F%208Q5B%20with%20flange%20connections%20-%20PP03.jpg

95 ms

Cerabar_PMC51B.jpg

Cerabar_PMC51B.jpg

98 ms

iTEMP%20TMT182B.jpg

iTEMP%20TMT182B.jpg

100 ms

TM111.jpg

TM111.jpg

96 ms

Proline%20Prosonic%20Flow%20P%20500%20%2F%209P5B%20with%20clamp-on%20sensor%20-%20PP01.jpg

Proline%20Prosonic%20Flow%20P%20500%20%2F%209P5B%20with%20clamp-on%20sensor%20-%20PP01.jpg

102 ms

TMT31_spring%20terminals_front.jpg

TMT31_spring%20terminals_front.jpg

116 ms

TMT36_spring%20terminals_front.jpg

TMT36_spring%20terminals_front.jpg

115 ms

JT33_CBH_EnclosureClosed_C_003.jpg

JT33_CBH_EnclosureClosed_C_003.jpg

117 ms

Micropilot_NMR84_PP.jpg

Micropilot_NMR84_PP.jpg

146 ms

Cerabar_PMC21_PP_1.jpg

Cerabar_PMC21_PP_1.jpg

113 ms

Proline%20Promag%20H%2010%20%2F%205HBB%20with%20Tri-Clamp%20connections%20for%20basic%20hygienic%20applications%20-%20PP01.jpg

Proline%20Promag%20H%2010%20%2F%205HBB%20with%20Tri-Clamp%20connections%20for%20basic%20hygienic%20applications%20-%20PP01.jpg

433 ms

TM151.jpg

TM151.jpg

124 ms

tms21_cutout.jpg

tms21_cutout.jpg

121 ms

Cerabar_PMP51B.jpg

Cerabar_PMP51B.jpg

178 ms

TT151-14E4_0.jpg

TT151-14E4_0.jpg

140 ms

TMS31-rope-v1.jpg

TMS31-rope-v1.jpg

142 ms

Virtual%20Booth%20TR.jpg

Virtual%20Booth%20TR.jpg

251 ms

Zweileiter_Plattfor_FA_Level_Flow.jpg

Zweileiter_Plattfor_FA_Level_Flow.jpg

237 ms

Promo_Web_GCD_962x212.jpg

Promo_Web_GCD_962x212.jpg

426 ms

EH_2024_products.jpg

EH_2024_products.jpg

194 ms

EH_2024_maulburg_campus2030.jpg

EH_2024_maulburg_campus2030.jpg

241 ms

EH_thomas_buer.jpg

EH_thomas_buer.jpg

420 ms

EH_2024_India_1.jpg

EH_2024_India_1.jpg

422 ms

styles.css

styles.css

218 ms

styles.css

styles.css

220 ms

fonts.css

fonts.css

218 ms

dialogbox.css

dialogbox.css

90 ms

timebox.css

timebox.css

91 ms

eh-icon-fonts.cache.css

eh-icon-fonts.cache.css

91 ms

undefined.cache.js

undefined.cache.js

3663 ms

clear.cache.gif

clear.cache.gif

88 ms

E+H_SerifReg.woff

E+H_SerifReg.woff

13 ms

E+H_SerifReg.woff

E+H_SerifReg.woff

13 ms

E+H_SansReg.woff

E+H_SansReg.woff

11 ms

E+H_SansReg.woff

E+H_SansReg.woff

13 ms

E+H_SansBol.woff

E+H_SansBol.woff

14 ms

E+H_SansLig.woff

E+H_SansLig.woff

14 ms

E+H_SansLig.woff

E+H_SansLig.woff

12 ms

E+H_SansDem.woff

E+H_SansDem.woff

14 ms

E+H_SansDem.woff

E+H_SansDem.woff

342 ms

eh-iconset-30.woff

eh-iconset-30.woff

14 ms

eh-iconset-30.woff

eh-iconset-30.woff

15 ms

Promo_Web_GCD_962x212.jpg

Promo_Web_GCD_962x212.jpg

60 ms

Accessibility Review

in.endress.com accessibility score

86

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

Best Practices

in.endress.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

in.endress.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

in.endress.com

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