Tools & Wizards About Us
i2owater.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

i2owater.com

i2O Water

Page Load Speed

2.3 sec in total

First Response

80 ms

Resources Loaded

1.8 sec

Page Rendered

434 ms

i2owater.com screenshot

About Website

Visit i2owater.com now to see the best up-to-date I2O Water content for Malaysia and also check out these interesting facts you probably never knew about i2owater.com

i2O’s solutions are being used worldwide to instrument, analyse and control water networks to reduce leakage, reduce energy consumption and improve supply.

Visit i2owater.com

Key Findings

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

Performance Metrics

i2owater.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

i2owater.com

80 ms

en.i2owater.com

144 ms

css

46 ms

style.css

50 ms

style.min.css

105 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original I2owater.com, 62% (31 requests) were made to En.i2owater.com and 10% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (362 ms) relates to the external source En.i2owater.com.

Page Optimization Overview & Recommendations

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

Content Size

533.4 kB

After Optimization

472.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I2owater.com main page is 533.4 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. 45% of websites need less resources to load. Javascripts take 205.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 51.2 kB

  • Original 65.3 kB
  • After minification 61.2 kB
  • After compression 14.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. 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 51.2 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 132 B

  • Original 192.8 kB
  • After minification 192.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. I2O Water images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.5 kB

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

CSS Optimization

-11%

Potential reduce by 7.4 kB

  • Original 69.5 kB
  • After minification 68.8 kB
  • After compression 62.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. I2owater.com needs all CSS files to be minified and compressed as it can save up to 7.4 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (79%)

Requests Now

42

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

i2owater.com

i2owater.com

80 ms

en.i2owater.com

en.i2owater.com

144 ms

css

css

46 ms

style.css

style.css

50 ms

style.min.css

style.min.css

105 ms

styles.css

styles.css

80 ms

cms-navigation-base.css

cms-navigation-base.css

79 ms

cms-navigation.css

cms-navigation.css

76 ms

style.css

style.css

108 ms

jquery.min.js

jquery.min.js

35 ms

xdomain-data.js

xdomain-data.js

82 ms

ribbon.css

ribbon.css

184 ms

js

js

68 ms

ribbon.js

ribbon.js

164 ms

formreset.min.css

formreset.min.css

87 ms

formsmain.min.css

formsmain.min.css

135 ms

readyclass.min.css

readyclass.min.css

87 ms

browsers.min.css

browsers.min.css

87 ms

main.js

main.js

137 ms

main-deferred.js

main-deferred.js

199 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

137 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

137 ms

wp-polyfill.min.js

wp-polyfill.min.js

137 ms

dom-ready.min.js

dom-ready.min.js

139 ms

hooks.min.js

hooks.min.js

165 ms

i18n.min.js

i18n.min.js

165 ms

a11y.min.js

a11y.min.js

163 ms

jquery.json.min.js

jquery.json.min.js

163 ms

gravityforms.min.js

gravityforms.min.js

166 ms

utils.min.js

utils.min.js

198 ms

vendor-theme.min.js

vendor-theme.min.js

198 ms

scripts-theme.min.js

scripts-theme.min.js

199 ms

lazyload.min.js

lazyload.min.js

199 ms

analytics.js

analytics.js

42 ms

collect

collect

13 ms

ewa2lll.css

ewa2lll.css

42 ms

collect

collect

56 ms

js

js

106 ms

p.css

p.css

33 ms

ga-audiences

ga-audiences

323 ms

video-poster-1600x908.jpg

video-poster-1600x908.jpg

362 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

252 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

269 ms

cIf4MaFatEE-VTaP_JWEdGYmmA.ttf

cIf4MaFatEE-VTaP_JWEdGYmmA.ttf

286 ms

cIf4MaFatEE-VTaP_PGFdGYmmA.ttf

cIf4MaFatEE-VTaP_PGFdGYmmA.ttf

286 ms

cIf9MaFatEE-VTaP9C6hZA.ttf

cIf9MaFatEE-VTaP9C6hZA.ttf

287 ms

d

d

108 ms

i2O-LOGO.svg

i2O-LOGO.svg

35 ms

en.png

en.png

36 ms

es.png

es.png

35 ms

Accessibility Review

i2owater.com accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Links do not have a discernible name

Best Practices

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

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

High

Tap targets are not sized appropriately

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

i2owater.com

Open Graph data is detected on the main page of I2O Water. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: