2.5 sec in total
186 ms
2.1 sec
259 ms
Visit who.int now to see the best up-to-date Who content for India and also check out these interesting facts you probably never knew about who.int
The United Nations agency working to promote health, keep the world safe and serve the vulnerable.
Visit who.intWe analyzed Who.int page load time and found that the first response time was 186 ms and then it took 2.3 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.
who.int performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value32.1 s
0/100
25%
Value21.0 s
0/100
10%
Value32,420 ms
0/100
30%
Value0.006
100/100
15%
Value48.1 s
0/100
10%
186 ms
93 ms
359 ms
626 ms
643 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 65% of them (42 requests) were addressed to the original Who.int, 5% (3 requests) were made to Youtube.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (900 ms) belongs to the original domain Who.int.
Page size can be reduced by 1.5 MB (51%)
3.0 MB
1.5 MB
In fact, the total size of Who.int main page is 3.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. 65% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 54.7 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 54.7 kB or 78% of the original size.
Potential reduce by 92.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. Who images are well optimized though.
Potential reduce by 982.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 982.4 kB or 70% of the original size.
Potential reduce by 370.8 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. Who.int needs all CSS files to be minified and compressed as it can save up to 370.8 kB or 84% of the original size.
Number of requests can be reduced by 38 (69%)
55
17
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 23 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
who.int
186 ms
en
93 ms
359 ms
jquery.js
626 ms
jquery.plugins_r.js
643 ms
enquire.min.js
182 ms
owl.carousel.js
779 ms
who.js
900 ms
responsive.js
357 ms
FusionCharts.js
165 ms
jquery.countdown.js
150 ms
jquery.countdown-en.js
144 ms
who_responsive.css
353 ms
captify.js
446 ms
lang_en_r.css
447 ms
shadowbox.css
461 ms
shadowbox.js
636 ms
widgets.js
31 ms
reset.css
102 ms
layout-responsive.css
99 ms
general-responsive.css
191 ms
elements-responsive.css
184 ms
owl.carousel.css
102 ms
owl.theme.css
100 ms
responsive.css
200 ms
print.css
198 ms
Malawi_children_310.jpeg
105 ms
chan-rousseff310.jpg
106 ms
ebola-tonkolili-310.jpg
109 ms
assistive-technology310.jpg
108 ms
africa-vaccines-commentary.jpg
108 ms
dg-photo315.png
412 ms
gtm.js
24 ms
0LRdyEx6K30
85 ms
kc6U8HpOWbQ
133 ms
0skonVosTJU
139 ms
who-logo-en.jpg
216 ms
who_sprite.gif
214 ms
responsive-sprite.png
215 ms
lines.gif
215 ms
FusionCharts.HC.js
122 ms
footer_emblem-en-r.gif
191 ms
top.png
377 ms
analytics.js
62 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
12 ms
1158.js
40 ms
www-embed-player-vflZsBgOl.css
61 ms
www-embed-player.js
97 ms
base.js
237 ms
syndication
336 ms
516518516392878080
382 ms
Malawi_children_310.jpeg
311 ms
ebola-tonkolili-310.jpg
420 ms
africa-vaccines-commentary.jpg
307 ms
collect
29 ms
collect
82 ms
s
107 ms
u
397 ms
collect
297 ms
FusionCharts.HC.Charts.js
47 ms
collect
273 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
65 ms
ad_status.js
61 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
37 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
45 ms
who.int 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
who.int 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
who.int 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Who.int can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 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.
who.int
Open Graph data is detected on the main page of Who. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: