11.3 sec in total
1.9 sec
5.9 sec
3.5 sec
Click here to check amazing Be Cause Water content. Otherwise, check out these important facts you probably never knew about becausewater.com
BeCause Water creates and implements solutions that promote smarter, healthier water consumption.
Visit becausewater.comWe analyzed Becausewater.com page load time and found that the first response time was 1.9 sec and then it took 9.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.
becausewater.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value5.1 s
24/100
25%
Value9.9 s
10/100
10%
Value980 ms
28/100
30%
Value0.261
47/100
15%
Value21.1 s
1/100
10%
1906 ms
76 ms
155 ms
657 ms
2355 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 71% of them (46 requests) were addressed to the original Becausewater.com, 20% (13 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Becausewater.com.
Page size can be reduced by 630.0 kB (30%)
2.1 MB
1.5 MB
In fact, the total size of Becausewater.com main page is 2.1 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 58.6 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 58.6 kB or 83% of the original size.
Potential reduce by 3.4 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. Be Cause Water images are well optimized though.
Potential reduce by 64.5 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 64.5 kB or 64% of the original size.
Potential reduce by 503.5 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. Becausewater.com needs all CSS files to be minified and compressed as it can save up to 503.5 kB or 83% of the original size.
Number of requests can be reduced by 20 (40%)
50
30
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Be Cause 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 11 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
becausewater.com
1906 ms
wp-emoji-release.min.js
76 ms
style.min.css
155 ms
styles.css
657 ms
contact-form-7-email-spam-blocker-public.css
2355 ms
css
31 ms
style.css
314 ms
css
32 ms
style.css
125 ms
form-basic.min.css
141 ms
dashicons.min.css
252 ms
jquery.js
275 ms
contact-form-7-email-spam-blocker-public.js
1628 ms
load.sumome.com
179 ms
et-divi-customizer-global-16037440873041.min.css
368 ms
css
27 ms
scripts.js
2739 ms
comment-reply.min.js
434 ms
custom.min.js
508 ms
common.js
508 ms
wp-embed.min.js
553 ms
forms-api.min.js
574 ms
analytics.js
379 ms
logo_transparent.png
282 ms
logo_transparent1.jpg
269 ms
school-customer-banner.png
285 ms
causetjs.png
266 ms
sucre.png
267 ms
pipe.png
286 ms
feuille.png
283 ms
titre-why-provide-2.png
282 ms
pic.png
515 ms
A.png
284 ms
B.png
286 ms
C.png
313 ms
gloria.jpg
299 ms
titre-partie-zig-zag-2.png
373 ms
every-product-1.png
612 ms
we-handle-everything-3.png
374 ms
Service-pic-1.png
549 ms
educate-3.png
375 ms
newspaper_cover_mockup_1900.png
611 ms
Product-Hihglih-titre-1.png
405 ms
ezH2O-logo-e1462230684324.jpg
496 ms
EZH2O-LANDING-PAGE-1-1-1.jpg
499 ms
logomark_noletters-small.png
547 ms
mem8YaGs126MiZpBA-UFW50e.ttf
76 ms
mem5YaGs126MiZpBA-UN_r8OXOhs.ttf
77 ms
mem5YaGs126MiZpBA-UNirkOXOhs.ttf
79 ms
mem5YaGs126MiZpBA-UN7rgOXOhs.ttf
78 ms
mem5YaGs126MiZpBA-UN8rsOXOhs.ttf
79 ms
modules.ttf
250 ms
collect
239 ms
AdobeStock_46458253.jpeg
510 ms
More-transparent.png
129 ms
vague.png
193 ms
water-splash-3.png
117 ms
S6uyw4BMUTPHjx4wWw.ttf
39 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
41 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
39 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
41 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
41 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
41 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
37 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
49 ms
becausewater.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
becausewater.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
becausewater.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Becausewater.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 Becausewater.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.
becausewater.com
Open Graph data is detected on the main page of Be Cause Water. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: