Tools & Wizards About Us
water-research.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

water-research.net

Drinking Water Quality | Inform Test Treat | Well or Public Water | Water Research Center

Page Load Speed

2.7 sec in total

First Response

355 ms

Resources Loaded

1.8 sec

Page Rendered

580 ms

water-research.net screenshot

About Website

Click here to check amazing Water Research content for India. Otherwise, check out these important facts you probably never knew about water-research.net

The Path to Clean Water | Get Informed, Get Tested, Get Treatment | Drinking Water Quality Testing and Treatment for Well Water and City Water | Water Research Center

Visit water-research.net

Key Findings

We analyzed Water-research.net page load time and found that the first response time was 355 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

water-research.net performance score

0

Network Requests Diagram

water-research.net

355 ms

template.css.php

18 ms

superfish.css

19 ms

mootools-core.js

13 ms

core.js

11 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 41% of them (56 requests) were addressed to the original Water-research.net, 16% (21 requests) were made to Static.xx.fbcdn.net and 7% (10 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (449 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 405.8 kB (30%)

Content Size

1.4 MB

After Optimization

962.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Water-research.net main page is 1.4 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 918.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 116.3 kB

  • Original 147.5 kB
  • After minification 145.7 kB
  • After compression 31.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. 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 116.3 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 82.7 kB

  • Original 918.9 kB
  • After minification 836.2 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. Water Research images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 154.5 kB

  • Original 234.5 kB
  • After minification 229.9 kB
  • After compression 80.0 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 154.5 kB or 66% of the original size.

CSS Optimization

-77%

Potential reduce by 52.3 kB

  • Original 67.5 kB
  • After minification 54.8 kB
  • After compression 15.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. Water-research.net needs all CSS files to be minified and compressed as it can save up to 52.3 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 83 (63%)

Requests Now

131

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Water Research. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

water-research.net

water-research.net

355 ms

template.css.php

template.css.php

18 ms

superfish.css

superfish.css

19 ms

mootools-core.js

mootools-core.js

13 ms

core.js

core.js

11 ms

caption.js

caption.js

11 ms

in.js

in.js

15 ms

widgets.js

widgets.js

11 ms

plusone.js

plusone.js

96 ms

jquery.min.js

jquery.min.js

51 ms

jquery.fpss.js

jquery.fpss.js

8 ms

jquery.min.js

jquery.min.js

68 ms

hoverIntent.js

hoverIntent.js

11 ms

superfish.js

superfish.js

10 ms

system.css

system.css

6 ms

general.css

general.css

6 ms

template.css

template.css

7 ms

css

css

44 ms

template.css

template.css

6 ms

typography.php

typography.php

67 ms

pinit.js

pinit.js

42 ms

secureAnonymousFramework

secureAnonymousFramework

24 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

30 ms

all.js

all.js

158 ms

system.css

system.css

41 ms

01_global.css

01_global.css

7 ms

02_container.css

02_container.css

8 ms

03_header.css

03_header.css

8 ms

04_nav.css

04_nav.css

8 ms

04_nav_superfish.css

04_nav_superfish.css

8 ms

05_nav_top.css

05_nav_top.css

9 ms

06_intro.css

06_intro.css

10 ms

07_mid.css

07_mid.css

10 ms

08_main_content.css

08_main_content.css

25 ms

09_side_left.css

09_side_left.css

25 ms

10_side_right.css

10_side_right.css

26 ms

11_footer.css

11_footer.css

26 ms

12_nav_bottom.css

12_nav_bottom.css

26 ms

xt_specials.css

xt_specials.css

27 ms

xt_virtuemart.css

xt_virtuemart.css

27 ms

xt_virtuemart_theme.css

xt_virtuemart_theme.css

27 ms

xt_blog.css

xt_blog.css

27 ms

xt_jevents_calendar.css

xt_jevents_calendar.css

28 ms

xt_jevents_calendar_2.5.css

xt_jevents_calendar_2.5.css

29 ms

xt_fpss.css

xt_fpss.css

30 ms

xt_login.css

xt_login.css

28 ms

xt_gallery.css

xt_gallery.css

29 ms

analytics.js

analytics.js

111 ms

PinExt.png

PinExt.png

103 ms

fizzydiscoloredwater.jpg

fizzydiscoloredwater.jpg

105 ms

btn_cart_LG.gif

btn_cart_LG.gif

165 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

159 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

157 ms

share

share

232 ms

sprite_connect_v14.png

sprite_connect_v14.png

247 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

89 ms

fastbutton

fastbutton

164 ms

bfen_top_facebook_02.jpg

bfen_top_facebook_02.jpg

68 ms

bfen_top_twitter_01.jpg

bfen_top_twitter_01.jpg

74 ms

bfen_header_logo_02.jpg

bfen_header_logo_02.jpg

75 ms

loading.gif

loading.gif

73 ms

9_d61d44254608dd06ccdd2ff02982d14d_m.jpg

9_d61d44254608dd06ccdd2ff02982d14d_m.jpg

159 ms

9_d61d44254608dd06ccdd2ff02982d14d_t.jpg

9_d61d44254608dd06ccdd2ff02982d14d_t.jpg

72 ms

bfen_sidebar_App_header_01.jpg

bfen_sidebar_App_header_01.jpg

125 ms

bfen_sidebar_App_iOS_01.jpg

bfen_sidebar_App_iOS_01.jpg

124 ms

bfen_sidebar_App_Android_01.jpg

bfen_sidebar_App_Android_01.jpg

138 ms

bfen_sidebar_header_bkgd_01.jpg

bfen_sidebar_header_bkgd_01.jpg

123 ms

bfen_mobile_join_01.jpg

bfen_mobile_join_01.jpg

123 ms

bfen_Booklet_01.jpg

bfen_Booklet_01.jpg

194 ms

bfen_footer_logo_02.jpg

bfen_footer_logo_02.jpg

156 ms

bfen_footer_bfenvironmental_02.jpg

bfen_footer_bfenvironmental_02.jpg

174 ms

pixel.gif

pixel.gif

123 ms

oramlab.jpg

oramlab.jpg

121 ms

spacer.gif

spacer.gif

63 ms

pabooklet2ndedition.jpg

pabooklet2ndedition.jpg

71 ms

shadow.png

shadow.png

72 ms

pinit_main.js

pinit_main.js

60 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

118 ms

collect

collect

25 ms

218 ms

xd_arbiter.php

xd_arbiter.php

146 ms

xd_arbiter.php

xd_arbiter.php

217 ms

likebox.php

likebox.php

449 ms

count.json

count.json

184 ms

syndication

syndication

167 ms

486909362389012480

486909362389012480

222 ms

postmessageRelay

postmessageRelay

118 ms

tweet_button.6a78875565a912489e9aef879c881358.en-gb.html

tweet_button.6a78875565a912489e9aef879c881358.en-gb.html

57 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

65 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

70 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

105 ms

jot

jot

75 ms

api.js

api.js

30 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

71 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

57 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

3 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

5 ms

gV1klVWt_normal.jpeg

gV1klVWt_normal.jpeg

39 ms

n7IAcY2jJIh.css

n7IAcY2jJIh.css

93 ms

n--mLoVmLJM.css

n--mLoVmLJM.css

112 ms

dbNRhrdsQao.css

dbNRhrdsQao.css

131 ms

vdFoLHd3QwI.css

vdFoLHd3QwI.css

158 ms

uOFrTixURdn.css

uOFrTixURdn.css

182 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

202 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

223 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

149 ms

TTCre3391I0.js

TTCre3391I0.js

150 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

199 ms

b_6HNn_J2BZ.js

b_6HNn_J2BZ.js

200 ms

7cm7D75Y0Sf.js

7cm7D75Y0Sf.js

243 ms

rFmE1g6Dkoz.js

rFmE1g6Dkoz.js

254 ms

336JejShbZp.js

336JejShbZp.js

242 ms

jot

jot

118 ms

10156017_708014285923707_8285894055628276598_n.jpg

10156017_708014285923707_8285894055628276598_n.jpg

97 ms

safe_image.php

safe_image.php

182 ms

10369995_708014005923735_9040077699722752220_n.jpg

10369995_708014005923735_9040077699722752220_n.jpg

169 ms

1795675_486872678124433_1394795575683916192_n.jpg

1795675_486872678124433_1394795575683916192_n.jpg

169 ms

12243352_1655285631385085_2819625407170624731_n.jpg

12243352_1655285631385085_2819625407170624731_n.jpg

170 ms

11055359_1081320988563597_1973091951507785729_n.jpg

11055359_1081320988563597_1973091951507785729_n.jpg

170 ms

12311065_1530557350591922_1909505097947749671_n.jpg

12311065_1530557350591922_1909505097947749671_n.jpg

175 ms

12552885_1664797937092864_6068733910557534164_n.jpg

12552885_1664797937092864_6068733910557534164_n.jpg

174 ms

12669707_174515432923406_3313488785000604463_n.jpg

12669707_174515432923406_3313488785000604463_n.jpg

173 ms

12313856_416046968594740_1224726229795143835_n.jpg

12313856_416046968594740_1224726229795143835_n.jpg

172 ms

10359551_790572284329583_2510454062635777805_n.jpg

10359551_790572284329583_2510454062635777805_n.jpg

176 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

161 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

161 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

160 ms

a-ZN6WoEOje.png

a-ZN6WoEOje.png

161 ms

safe_image.php

safe_image.php

171 ms

safe_image.php

safe_image.php

173 ms

safe_image.php

safe_image.php

176 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

20 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

35 ms

like.php

like.php

87 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

18 ms

SEO Factors

water-research.net SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Water-research.net 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 Water-research.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

water-research.net

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