6.4 sec in total
121 ms
6.1 sec
215 ms
Click here to check amazing Aqua Viable content. Otherwise, check out these important facts you probably never knew about aquaviable.com
Make water from the air! Join the Personal Water Revolution. Produce up to 5 Gallons of delicious, pure drinking water each day with your own in home, or office atmospheric water generator.
Visit aquaviable.comWe analyzed Aquaviable.com page load time and found that the first response time was 121 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
aquaviable.com performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value15.1 s
0/100
25%
Value15.5 s
0/100
10%
Value850 ms
34/100
30%
Value0.605
10/100
15%
Value16.5 s
5/100
10%
121 ms
91 ms
23 ms
44 ms
59 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 42% of them (31 requests) were addressed to the original Aquaviable.com, 49% (36 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (381 ms) relates to the external source I.vimeocdn.com.
Page size can be reduced by 195.8 kB (41%)
476.4 kB
280.6 kB
In fact, the total size of Aquaviable.com main page is 476.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. 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. HTML takes 228.8 kB which makes up the majority of the site volume.
Potential reduce by 193.8 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 193.8 kB or 85% of the original size.
Potential reduce by 0 B
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. Aqua Viable images are well optimized though.
Potential reduce by 644 B
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.
Potential reduce by 1.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. Aquaviable.com has all CSS files already compressed.
Number of requests can be reduced by 28 (80%)
35
7
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aqua Viable. 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 11 to 1 for CSS and as a result speed up the page load time.
aquaviable.com
121 ms
js
91 ms
formidableforms.css
23 ms
index.css
44 ms
index.css
59 ms
font-awesome.min.css
55 ms
woocommerce-layout.css
58 ms
woocommerce.css
60 ms
wp-email-capture-styles.css
64 ms
style.css
54 ms
wp-polyfill-inert.min.js
59 ms
regenerator-runtime.min.js
62 ms
wp-polyfill.min.js
99 ms
hooks.min.js
64 ms
w.js
16 ms
frontend-gtag.min.js
65 ms
et-core-unified-156.min.css
65 ms
jquery.min.js
99 ms
jquery-migrate.min.js
97 ms
jquery.blockUI.min.js
97 ms
add-to-cart.min.js
97 ms
js.cookie.min.js
97 ms
woocommerce.min.js
98 ms
sourcebuster.min.js
126 ms
order-attribution.min.js
126 ms
scripts.min.js
172 ms
jquery.fitvids.js
126 ms
common.js
126 ms
style.css
77 ms
g.gif
156 ms
fbevents.js
157 ms
640763394
121 ms
avlogoopt.gif
126 ms
2021-Aquaviable-website-homepage.00_00_47_10.Still002-video-cover.jpg
127 ms
640763394
210 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCM.woff
66 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf
77 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCM.woff
87 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf
93 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCM.woff
92 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf
91 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCM.woff
92 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCP.ttf
88 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CM.woff
107 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CP.ttf
107 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCM.woff
109 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf
109 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCM.woff
108 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf
108 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCM.woff
110 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf
110 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCM.woff
123 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCP.ttf
122 ms
modules.woff
53 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff
110 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
118 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff
119 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
121 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff
121 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
123 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff
124 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
122 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff
124 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
124 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff
124 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
161 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff
161 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
160 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff
160 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
160 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff
157 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
161 ms
woocommerce-smallscreen.css
22 ms
1288821422-1b98c38d7838db0b3679407b78a6c5249bdad7f5787962271
381 ms
aquaviable.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
aquaviable.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
aquaviable.com SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aquaviable.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 Aquaviable.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.
aquaviable.com
Open Graph data is detected on the main page of Aqua Viable. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: