9.9 sec in total
241 ms
9.3 sec
348 ms
Visit worldwatercouncil.org now to see the best up-to-date World Water Council content for India and also check out these interesting facts you probably never knew about worldwatercouncil.org
Visit worldwatercouncil.orgWe analyzed Worldwatercouncil.org page load time and found that the first response time was 241 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
worldwatercouncil.org performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value29.3 s
0/100
25%
Value14.4 s
1/100
10%
Value130 ms
96/100
30%
Value0.012
100/100
15%
Value24.9 s
0/100
10%
241 ms
398 ms
202 ms
64 ms
194 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 87% of them (147 requests) were addressed to the original Worldwatercouncil.org, 5% (9 requests) were made to Cdn.jsdelivr.net and 4% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Worldwatercouncil.org.
Page size can be reduced by 288.8 kB (8%)
3.7 MB
3.4 MB
In fact, the total size of Worldwatercouncil.org main page is 3.7 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. 60% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 112.0 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 57.0 kB, which is 45% 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 112.0 kB or 89% of the original size.
Potential reduce by 149.8 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. World Water Council images are well optimized though.
Potential reduce by 14.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. This website has mostly compressed JavaScripts.
Potential reduce by 12.4 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. Worldwatercouncil.org needs all CSS files to be minified and compressed as it can save up to 12.4 kB or 17% of the original size.
Number of requests can be reduced by 119 (77%)
154
35
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of World Water Council. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 72 to 1 for JavaScripts and from 49 to 1 for CSS and as a result speed up the page load time.
worldwatercouncil.org
241 ms
www.worldwatercouncil.org
398 ms
en
202 ms
js
64 ms
slick.css
194 ms
slick.module.css
264 ms
align.module.css
331 ms
fieldgroup.module.css
330 ms
container-inline.module.css
331 ms
clearfix.module.css
330 ms
details.module.css
329 ms
hidden.module.css
351 ms
item-list.module.css
417 ms
js.module.css
419 ms
nowrap.module.css
420 ms
position-container.module.css
417 ms
progress.module.css
417 ms
reset-appearance.module.css
440 ms
resize.module.css
504 ms
sticky-header.module.css
505 ms
system-status-counter.css
504 ms
system-status-report-counters.css
506 ms
system-status-report-general-info.css
505 ms
tablesort.module.css
528 ms
tree-child.module.css
591 ms
views.module.css
591 ms
flexslider.css
592 ms
blazy.css
594 ms
blazy.loading.css
593 ms
slick-theme.css
614 ms
webform_bootstrap.css
679 ms
flexslider_img.css
680 ms
bootstrap.min.css
777 ms
we_megamenu_backend.css
772 ms
slick.theme.css
680 ms
slick.theme--classic.css
705 ms
bootstrap.css
16 ms
drupal-bootstrap.css
23 ms
drupal-bootstrap.css
25 ms
drupal-bootstrap.css
28 ms
drupal-bootstrap.css
30 ms
drupal-bootstrap.css
29 ms
drupal-bootstrap.css
37 ms
drupal-bootstrap.css
30 ms
reset.css
765 ms
styles.css
857 ms
print.css
766 ms
bootstrap.js
27 ms
js
74 ms
analytics.js
17 ms
responsive.css
674 ms
collect
59 ms
style1.css
624 ms
selection-sharer.css
605 ms
colorbox.css
541 ms
blazy.polyfill.min.js
539 ms
jquery.min.js
564 ms
underscore-min.js
659 ms
blazy.classlist.min.js
662 ms
blazy.promise.min.js
643 ms
blazy.raf.min.js
576 ms
once.min.js
577 ms
drupalSettingsLoader.js
578 ms
drupal.js
644 ms
drupal.init.js
643 ms
debounce.js
623 ms
dblazy.min.js
558 ms
blazy.once.min.js
556 ms
blazy.sanitizer.min.js
586 ms
blazy.dom.min.js
634 ms
blazy.base.min.js
635 ms
blazy.dataset.min.js
609 ms
blazy.viewport.min.js
548 ms
blazy.xlazy.min.js
547 ms
blazy.observer.min.js
565 ms
blazy.loading.min.js
631 ms
blazy.webp.min.js
633 ms
blazy.min.js
612 ms
bio.min.js
550 ms
jquery.easing.min.js
548 ms
slick.min.js
567 ms
bio.media.min.js
606 ms
blazy.drupal.min.js
547 ms
blazy.load.min.js
544 ms
blazy.compat.min.js
538 ms
index.umd.min.js
535 ms
google_analytics.js
540 ms
jquery.placeholder.js
545 ms
css
33 ms
css
52 ms
isotope.pkgd.min.js
543 ms
jquery.highlight-5.js
538 ms
jquery.colorbox.js
539 ms
custom.js
540 ms
modernizr.custom.js
536 ms
classie.js
502 ms
demo1.js
502 ms
webform.behaviors.js
504 ms
states.js
504 ms
states.js
502 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
14 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
26 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
50 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
66 ms
webform.states.js
522 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
67 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
67 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
67 ms
webform_bootstrap.states.js
521 ms
drupal.bootstrap.js
525 ms
attributes.js
527 ms
theme.js
525 ms
popover.js
527 ms
tooltip.js
516 ms
jquery.flexslider-min.js
532 ms
flexslider.load.min.js
533 ms
we_mobile_menu.js
535 ms
we_megamenu_frontend.js
532 ms
progress.js
534 ms
progress.js
538 ms
loadjs.min.js
532 ms
announce.js
531 ms
message.js
533 ms
message.js
533 ms
ajax.js
535 ms
ajax.js
534 ms
bio.ajax.min.js
533 ms
jquery.form.min.js
534 ms
base.js
536 ms
ajax_view.js
535 ms
ajax_view.js
538 ms
slick.load.min.js
535 ms
quicksand-v6-latin-700.woff
621 ms
quicksand-v6-latin-500.woff
534 ms
quicksand-v6-latin-regular.woff
548 ms
quicksand-v6-latin-300.woff
627 ms
slick.woff
542 ms
logo_header.jpg
536 ms
AdobeStock_173631643B_D.jpg
7082 ms
Water_securityHP2.png
986 ms
Financing_water_HP_BD_1.jpg
627 ms
covid_19_HP_BD_0.jpg
569 ms
observatoryBLOCHP_1.jpg
706 ms
GIRE_HP_BD_0.jpg
693 ms
fleche_lien.png
555 ms
11th%20World%20Water%20Forum.png
624 ms
Design%20sans%20titre_0.png
731 ms
Design%20sans%20titre%20%282%29.png
793 ms
2ndSCM_1.png
804 ms
Image1.png
698 ms
4598-REPORT_IWRM_2023_WEB.png
993 ms
4592-WWC-Triennal%20Strategic%20Framework%20-%202023-2025.png
916 ms
4388-WWC_QUADRENNIAL_REPORT_2019_2022_BD_compressed.png
1066 ms
logo_footer.png
809 ms
receive_news_footer.svg
894 ms
bandeau2.jpg
878 ms
facebook.svg
899 ms
twitter.svg
903 ms
linkedin.svg
914 ms
ico-arrow.png
983 ms
ico-arrow-white.png
986 ms
border_bleu.png
968 ms
slick-prev.png
918 ms
slick-next.png
978 ms
border_bleu_left.png
984 ms
facebook_footer.svg
988 ms
twitter_footer.svg
988 ms
linkedin_footer.svg
978 ms
overlay.png
965 ms
worldwatercouncil.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
Image elements do not have [alt] attributes
Links do not have a discernible name
worldwatercouncil.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
Browser errors were logged to the console
Page has valid source maps
worldwatercouncil.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
Image elements do not have [alt] attributes
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 Worldwatercouncil.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 Worldwatercouncil.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.
worldwatercouncil.org
Open Graph description is not detected on the main page of World Water Council. 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: