Access exowater.com. Water Quality Continuous Monitoring System

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value12,980 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.313

37/100

15%

TTI (Time to Interactive)

Value34.3 s

0/100

10%

exowater.com

324 ms

exo

551 ms

marvel.js

103 ms

responsive.css

16 ms

jquery.min.js

94 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Exowater.com, 65% (61 requests) were made to Ysi.com and 7% (7 requests) were made to Video.ysi.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Ysi.com.

Content Size

1.6 MB

After Optimization

1.3 MB

In fact, the total size of Exowater.com main page is 1.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. 75% 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 143.0 kB

Original 189.3 kB
After minification 179.4 kB
After compression 46.3 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 143.0 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 28.7 kB

Original 1.1 MB
After minification 1.0 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. EXO Water images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 60.4 kB

Original 259.8 kB
After minification 259.5 kB
After compression 199.4 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 60.4 kB or 23% of the original size.

CSS Optimization

-2%

Potential reduce by 752 B

Original 38.7 kB
After minification 38.7 kB
After compression 38.0 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. Exowater.com has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

Low

No form fields have multiple labels

High

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

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA IDs are not unique

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exowater.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Exowater.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

exowater.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Water Quality Continuous Monitoring System - EXO Sondes

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

exowater.com

exo

marvel.js

responsive.css

jquery.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

exowater.com

exo

marvel.js

responsive.css

jquery.min.js

jquery-ui.min.js

modernizr.js

slider.js

base.css

responsive.css

sharethis.js

7971.js

WebForms.js

MicrosoftAjax.js

MicrosoftAjaxWebForms.js

forms2.min.js

Basepage.js

ComponentArtScript.axd

common.js

jquery.royalslider.min.js

gtm.js

bat.js

fbevents.js

munchkin.js

logo.png

player.html

player.html

player.html

player.html

player.html

cta-core-v3.js

blank.gif

water-quality-monitoring-system-exo-sonde.jpg

water-quality-monitoring-system-exo-family.jpg

learn-more-exo2.jpg

water-monitoring-sonde-exo2.jpg

learn-more-exo3.jpg

water-monitoring-sonde-exo3.jpg

learn-more-exo1.jpg

water-monitoring-sonde-exo1.jpg

learn-more-exo1s.jpg

learn-more-exo2s.jpg

learn-more-exo3s.jpg