3.2 sec in total
572 ms
1.8 sec
824 ms
Click here to check amazing Water4 content for United States. Otherwise, check out these important facts you probably never knew about water4.org
We are eradicating the world’s water crisis by putting the solution in the hands of the men, women, and children it affects most.
Visit water4.orgWe analyzed Water4.org page load time and found that the first response time was 572 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
water4.org performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value14.9 s
0/100
25%
Value16.1 s
0/100
10%
Value7,140 ms
0/100
30%
Value0.068
96/100
15%
Value33.8 s
0/100
10%
572 ms
214 ms
36 ms
10 ms
14 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 76% of them (42 requests) were addressed to the original Water4.org, 7% (4 requests) were made to F.vimeocdn.com and 4% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (572 ms) belongs to the original domain Water4.org.
Page size can be reduced by 550.1 kB (22%)
2.5 MB
1.9 MB
In fact, the total size of Water4.org main page is 2.5 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.8 MB which makes up the majority of the site volume.
Potential reduce by 26.4 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 26.4 kB or 80% of the original size.
Potential reduce by 30.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. Water4 images are well optimized though.
Potential reduce by 347.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 347.4 kB or 69% of the original size.
Potential reduce by 145.9 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. Water4.org needs all CSS files to be minified and compressed as it can save up to 145.9 kB or 87% of the original size.
Number of requests can be reduced by 15 (29%)
51
36
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Water4. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.water4.org
572 ms
javelin_global.css
214 ms
base.css
36 ms
style.css
10 ms
index.css
14 ms
jsapi
18 ms
common.js
12 ms
jquery.cycle.js
13 ms
main.min.js
4 ms
home.min.js
15 ms
simplemodal.js
6 ms
jquery.min.js
30 ms
jquery-ui.min.js
50 ms
bg-html.gif
12 ms
analytics.js
35 ms
sprite-icons.png
29 ms
bg-main.jpg
29 ms
logo-lg.png
30 ms
sprite-icons-index.png
26 ms
waves-a-front.png
24 ms
waves-a-middle.png
24 ms
waves-a-back.png
27 ms
bg-index-section-1.jpg
27 ms
bg-slideshow.jpg
25 ms
seven_nations_1-570-360-crop.jpg
29 ms
Justin%20Wren-570-360-crop.png
30 ms
2014_impact_slideshow_image-570-360-crop.jpg
31 ms
border-dotted-x.png
39 ms
border-dotted-y.png
38 ms
bg-index-section-2.jpg
47 ms
waves-inner-top.png
40 ms
waves-inner-bottom.png
90 ms
bg-index-section-3.jpg
39 ms
bg-hexagons-solutions.jpg
39 ms
bg-index-section-4.jpg
38 ms
sprite-hex-nodes.png
41 ms
waves-inner-bottom-dark.png
41 ms
bg-index-section-5.jpg
39 ms
bg-hexagons-fundraiser.jpg
43 ms
waves-b-front.png
42 ms
waves-b-middle.png
41 ms
waves-b-back.png
43 ms
logo-sm.png
43 ms
sourcesanspro-light-webfont.woff
34 ms
sourcesanspro-regular-webfont.woff
35 ms
sourcesanspro-semibold-webfont.woff
35 ms
collect
54 ms
collect
65 ms
60096421
433 ms
player.js
188 ms
player.css
170 ms
ga.js
60 ms
vuid.min.js
180 ms
__utm.gif
12 ms
proxy.html
32 ms
water4.org 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
water4.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
water4.org 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Water4.org 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 Water4.org 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.
water4.org
Open Graph description is not detected on the main page of Water4. 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: