8.8 sec in total
531 ms
7.8 sec
419 ms
Welcome to whqlibdoc.who.int homepage info - get ready to check Whqlibdoc Who best content for India right away, or after learning these important things about whqlibdoc.who.int
Erreur 404
Visit whqlibdoc.who.intWe analyzed Whqlibdoc.who.int page load time and found that the first response time was 531 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
whqlibdoc.who.int performance score
name
value
score
weighting
Value16.1 s
0/100
10%
Value16.1 s
0/100
25%
Value22.9 s
0/100
10%
Value12,810 ms
0/100
30%
Value0
100/100
15%
Value49.6 s
0/100
10%
531 ms
314 ms
1365 ms
725 ms
418 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Whqlibdoc.who.int, 79% (42 requests) were made to Extranet.who.int and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Extranet.who.int.
Page size can be reduced by 6.2 MB (77%)
8.0 MB
1.9 MB
In fact, the total size of Whqlibdoc.who.int main page is 8.0 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. 45% of websites need less resources to load. Javascripts take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 1.1 MB
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 1.1 MB or 93% of the original size.
Potential reduce by 3.6 MB
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 3.6 MB or 71% of the original size.
Potential reduce by 1.4 MB
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. Whqlibdoc.who.int needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 81% of the original size.
Number of requests can be reduced by 39 (89%)
44
5
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whqlibdoc Who. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
whqlibdoc.who.int
531 ms
libdoc.html
314 ms
libdoc.html
1365 ms
all.css
725 ms
grid.min.css
418 ms
origin.min.css
1043 ms
main.min.css
3554 ms
clarity.js
733 ms
optimize.js
931 ms
js
1339 ms
ekg7xazin3.js
839 ms
analytics.js
926 ms
gtm.js
1255 ms
ScriptResource_002.js
1133 ms
ScriptResource_003.js
1035 ms
ScriptResource.js
1596 ms
kendo.all.min.js
2851 ms
kendo.timezones.min.js
832 ms
Search-box.min.js
574 ms
language-selector.min.js
625 ms
content-block.min.js
680 ms
WebResource.js
729 ms
slicknav.min.js
786 ms
auto-complete.min.js
833 ms
match-height.min.js
881 ms
lazy.min.js
891 ms
modernizr-custom.js
936 ms
select2.full.min.js
1040 ms
accordion-footer-list.min.js
985 ms
main.min.js
996 ms
main-navigation.min.js
1041 ms
geo-navigation.min.js
1090 ms
image-resolution.min.js
1101 ms
picturefill.min.js
1143 ms
gridTabs.min.js
1145 ms
step-tabs.min.js
1195 ms
collect
35 ms
analytics.js
21 ms
js
102 ms
collect
105 ms
css
107 ms
css
132 ms
css
129 ms
print.min.css
127 ms
gtm.js
96 ms
h-logo-white.svg
472 ms
ekg7xazin3
94 ms
arrow-down-blue.svg
412 ms
Translation.svg
412 ms
arrow-down-blue.svg
413 ms
fa-solid-900.woff
382 ms
fa-regular-400.woff
382 ms
ekg7xazin3
72 ms
whqlibdoc.who.int 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
whqlibdoc.who.int 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whqlibdoc.who.int 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 Whqlibdoc.who.int 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.
whqlibdoc.who.int
Open Graph description is not detected on the main page of Whqlibdoc Who. 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: