Tools & Wizards About Us
e4i.com screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

e4i.com

Ultrasonic Leak Detectors by EFI

Page Load Speed

1.6 sec in total

First Response

176 ms

Resources Loaded

1.2 sec

Page Rendered

238 ms

e4i.com screenshot

About Website

Click here to check amazing E 4 I content. Otherwise, check out these important facts you probably never knew about e4i.com

Electronics For Industry, Ultrasonic Leak Detectors, Ultrasonic Stethoscopes for Detection of leaks in any Gas or Vapor under Pressure or Vacuum. Non-Destructive-Testing of Steam Traps, Bearings, Prev...

Visit e4i.com

Key Findings

We analyzed E4i.com page load time and found that the first response time was 176 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

e4i.com performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

e4i.com

176 ms

wpstyles.css

57 ms

jquery.js

168 ms

jquery.event.move.js

112 ms

jquery.event.swipe.js

111 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that all of those requests were addressed to E4i.com and no external sources were called. The less responsive or slowest element that took the longest time to load (497 ms) belongs to the original domain E4i.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 101.1 kB (4%)

Content Size

2.7 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E4i.com main page is 2.7 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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 69.1 kB

  • Original 81.7 kB
  • After minification 77.8 kB
  • After compression 12.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 69.1 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 31.9 kB

  • Original 2.6 MB
  • After minification 2.6 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. E 4 I images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 96 B

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

CSS Optimization

-6%

Potential reduce by 38 B

  • Original 649 B
  • After minification 649 B
  • After compression 611 B

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. E4i.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (16%)

Requests Now

69

After Optimization

58

  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E 4 I. 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 as a result speed up the page load time.

Network Requests Diagram

e4i.com

e4i.com

176 ms

wpstyles.css

wpstyles.css

57 ms

jquery.js

jquery.js

168 ms

jquery.event.move.js

jquery.event.move.js

112 ms

jquery.event.swipe.js

jquery.event.swipe.js

111 ms

jquery.wpslider.js

jquery.wpslider.js

113 ms

jquery.wplightbox.js

jquery.wplightbox.js

111 ms

wp0300ce79_06.png

wp0300ce79_06.png

59 ms

wpbfc29f90_06.png

wpbfc29f90_06.png

111 ms

wp993ef9a8_06.png

wp993ef9a8_06.png

61 ms

wp55f6d7e6_06.png

wp55f6d7e6_06.png

61 ms

wp4f7a31c7_06.png

wp4f7a31c7_06.png

58 ms

wp559a378e_06.png

wp559a378e_06.png

59 ms

wp6fc26368_06.png

wp6fc26368_06.png

113 ms

wpb5e6ba6e_06.png

wpb5e6ba6e_06.png

116 ms

wp777f8385_06.png

wp777f8385_06.png

114 ms

wp5533b116.gif

wp5533b116.gif

115 ms

wpf34b0e84_06.png

wpf34b0e84_06.png

323 ms

wpe0abedd7_06.png

wpe0abedd7_06.png

166 ms

wpbd9d5dac_06.png

wpbd9d5dac_06.png

220 ms

wp8da6d111_06.png

wp8da6d111_06.png

170 ms

wp1c17c827_06.png

wp1c17c827_06.png

168 ms

wp568eb699_06.png

wp568eb699_06.png

170 ms

wp49fdac91_06.png

wp49fdac91_06.png

221 ms

wpf9a8aa92_06.png

wpf9a8aa92_06.png

225 ms

wp5d8f3887_06.png

wp5d8f3887_06.png

223 ms

wp81440214_06.png

wp81440214_06.png

277 ms

wp915d6c9b_06.png

wp915d6c9b_06.png

277 ms

wpd845c542_06.png

wpd845c542_06.png

279 ms

wp1735d990_06.png

wp1735d990_06.png

280 ms

wpee0548d2_06.png

wpee0548d2_06.png

281 ms

wp58bbe513_06.png

wp58bbe513_06.png

333 ms

wp708a4c91_06.png

wp708a4c91_06.png

334 ms

wp2c7e4508_06.png

wp2c7e4508_06.png

386 ms

wpf11bf87a_06.png

wpf11bf87a_06.png

336 ms

wp06d05964_05_06.jpg

wp06d05964_05_06.jpg

337 ms

wpfa4ce18f_06.png

wpfa4ce18f_06.png

376 ms

wp39e16abd_05_06.jpg

wp39e16abd_05_06.jpg

442 ms

wpe38d14fe_06.png

wpe38d14fe_06.png

388 ms

wp8c26ee06_05_06.jpg

wp8c26ee06_05_06.jpg

393 ms

wpba7d20a3_06.png

wpba7d20a3_06.png

391 ms

wpac53e1d0_05_06.jpg

wpac53e1d0_05_06.jpg

433 ms

wpa7d8d072_06.png

wpa7d8d072_06.png

440 ms

wp4a6c147c_06.png

wp4a6c147c_06.png

445 ms

wp6196f933_06.png

wp6196f933_06.png

495 ms

wp7c4a3140_06.png

wp7c4a3140_06.png

497 ms

wpeaf9958b_06.png

wpeaf9958b_06.png

485 ms

wpd290c7d7_06.png

wpd290c7d7_06.png

441 ms

wp158c6b4b_06.png

wp158c6b4b_06.png

392 ms

wp6106f27c_06.png

wp6106f27c_06.png

446 ms

wp438104a5_06.png

wp438104a5_06.png

446 ms

wp58741048_06.png

wp58741048_06.png

496 ms

wpf32bb16f_06.png

wpf32bb16f_06.png

487 ms

wp0ebd00ea_05_06.jpg

wp0ebd00ea_05_06.jpg

444 ms

wp14739199_05_06.jpg

wp14739199_05_06.jpg

445 ms

wp79cdaaea_06.png

wp79cdaaea_06.png

442 ms

wp86bbde50_05_06.jpg

wp86bbde50_05_06.jpg

443 ms

wp93c21335_05_06.jpg

wp93c21335_05_06.jpg

439 ms

wp80f6d5eb_06.png

wp80f6d5eb_06.png

445 ms

wpfd1620b3_05_06.jpg

wpfd1620b3_05_06.jpg

446 ms

wpdefe3f4c_06.png

wpdefe3f4c_06.png

443 ms

wpd085038c_06.png

wpd085038c_06.png

448 ms

wp6cfd5641_06.png

wp6cfd5641_06.png

395 ms

wp94df6965_06.png

wp94df6965_06.png

440 ms

wpad30bfa8_06.png

wpad30bfa8_06.png

443 ms

wpb6156802_06.png

wpb6156802_06.png

448 ms

wp4f893e16_06.png

wp4f893e16_06.png

401 ms

wpb529a2e7_06.png

wpb529a2e7_06.png

395 ms

wpc664206a_06.png

wpc664206a_06.png

441 ms

wpa3935306_06.png

wpa3935306_06.png

441 ms

Accessibility Review

e4i.com accessibility score

84

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

Best Practices

e4i.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

e4i.com SEO score

92

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

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 E4i.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 E4i.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

e4i.com

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