1.8 sec in total
159 ms
1.2 sec
445 ms
Click here to check amazing Gray Water content. Otherwise, check out these important facts you probably never knew about graywater.org
A compilation of grey water regulations, suggested improvements to grey water laws, legality & regulation policy considerations, sample permits, public health concerns, treatment effectiveness, studie...
Visit graywater.orgWe analyzed Graywater.org page load time and found that the first response time was 159 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
graywater.org performance score
name
value
score
weighting
Value3.2 s
45/100
10%
Value4.2 s
45/100
25%
Value5.4 s
56/100
10%
Value1,250 ms
19/100
30%
Value0
100/100
15%
Value15.0 s
8/100
10%
159 ms
102 ms
76 ms
65 ms
62 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Graywater.org, 36% (13 requests) were made to Oasisdesign.net and 14% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (221 ms) relates to the external source Oasisdesign.net.
Page size can be reduced by 193.8 kB (22%)
874.5 kB
680.8 kB
In fact, the total size of Graywater.org main page is 874.5 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. Images take 447.1 kB which makes up the majority of the site volume.
Potential reduce by 60.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. This page needs HTML code to be minified as it can gain 18.8 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 60.2 kB or 79% of the original size.
Potential reduce by 119.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. Obviously, Gray Water needs image optimization as it can save up to 119.4 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.7 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.
Potential reduce by 11.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. Graywater.org needs all CSS files to be minified and compressed as it can save up to 11.5 kB or 16% of the original size.
Number of requests can be reduced by 14 (47%)
30
16
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gray 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 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
graywater.org
159 ms
greywater
102 ms
greywater
76 ms
65 ms
standard.css
62 ms
bootstrap.min.css
54 ms
font-awesome.min.css
39 ms
js
154 ms
page.js
56 ms
bootstrap.bundle.min.js
33 ms
jquery.min.js
34 ms
ga.js
43 ms
backgroundbluemottle.jpg
30 ms
OasisLogoTag.png
108 ms
carticon.png
106 ms
WebSearchIcon.png
127 ms
MissionLavanderiaCR.jpg
162 ms
GraywaterPermacultureGardBR.jpg
142 ms
PermacultureHarvest4.00_172.jpg
142 ms
GraywaterDataCalcs.png
221 ms
add2cartUC.gif
128 ms
sm.25.html
98 ms
eso.BRQnzO8v.js
96 ms
eaHgvPj9_nA
161 ms
__utm.gif
36 ms
icons.38.svg.js
21 ms
www-player.css
10 ms
www-embed-player.js
26 ms
base.js
51 ms
ad_status.js
155 ms
jj2eNDzr7OxRmG3eEZdf1bHpefYrrxl4VJQY9raQMR0.js
106 ms
embed.js
29 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
138 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
138 ms
id
12 ms
Create
105 ms
graywater.org accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
graywater.org 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
Page has valid source maps
graywater.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Graywater.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 Graywater.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.
graywater.org
Open Graph description is not detected on the main page of Gray 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: