Who.int WHO | World Health Organization
WHO's primary role is to direct international health within the United Nations' system and to lead partners in global health responses.
who.int Desktop Performance
53/100
These metrics represent real-world Chrome users experience viewing who.int web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
First Input Delay
First Contentful Paint
Cumulative Layout Shift
Largest Contentful Paint
Metrics
Largest Contentful Paint33/100 3.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Total Blocking Time36/100 440 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Speed Index53/100 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Time to Interactive69/100 3.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint83/100 1.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Cumulative Layout Shift100/100 0.031
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (18)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 854 KiB
640 ms
Avoid multiple page redirects
Potential savings of 380 ms
380 ms
Eliminate render-blocking resources
Potential savings of 310 ms
305 ms
Remove unused CSS
Potential savings of 128 KiB
280 ms
Remove unused JavaScript
Potential savings of 702 KiB
120 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Does not use passive listeners to improve scrolling performance
Avoid an excessive DOM size
2,285 elements
Serve static assets with an efficient cache policy
67 resources found
Avoid enormous network payloads
Total size was 3,430 KiB
Minimize main-thread work
2.2 s
JavaScript execution time
1.2 s
Largest Contentful Paint element
1 element found
User Timing marks and measures
5 user timings
Avoid chaining critical requests
24 chains found
Avoid large layout shifts
1 element found
Keep request counts low and transfer sizes small
113 requests • 3,430 KiB
Avoid long main-thread tasks
4 long tasks found
Passed Audits (12)
Preconnect to required origins
Minimize third-party usage
Third-party code blocked the main thread for 140 ms
Avoids `document.write()`
Minify CSS
Defer offscreen images
Initial server response time was short
Root document took 260 ms
Preload key requests
Minify JavaScript
Enable text compression
Use video formats for animated content
Properly size images
Potential savings of 57 KiB
Efficiently encode images
who.int Desktop SEO
92/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (1)
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
3 links found
Passed Audits (11)
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Page isn’t blocked from indexing
robots.txt is valid
Page has successful HTTP status code
Document has a meta description
Links are crawlable
Document avoids plugins
Document has a `<title>` element
who.int Desktop Best Practices
69/100
These checks highlight opportunities to improve the overall code health of who.int page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
General
Browser errors were logged to the console
Trust and Safety
Does not use HTTPS
2 insecure requests found
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Links to cross-origin destinations are unsafe
Passed Audits (10)
Serves images with appropriate resolution
Avoids requesting the geolocation permission on page load
Properly defines charset
Displays images with correct aspect ratio
Allows users to paste into password fields
Avoids requesting the notification permission on page load
Avoids deprecated APIs
Avoids Application Cache
Page has the HTML doctype
Detected JavaScript libraries
who.int Desktop Progressive Web App
19/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (10)
PWA Optimized
Is not configured for a custom splash screen
Does not set a theme color for the address bar.
Manifest doesn't have a maskable icon
Does not provide a valid `apple-touch-icon`
Fast and reliable
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 15.5 s
`start_url` does not respond with a 200 when offline
Current page does not respond with a 200 when offline
Installable
Does not use HTTPS
2 insecure requests found
Does not register a service worker that controls page and `start_url`
Web app manifest does not meet the installability requirements
Passed Audits (3)
Contains some content when JavaScript is not available
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Redirects HTTP traffic to HTTPS
who.int Desktop Accessibility
96/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (2)
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.
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (20)
`[role]`s are contained by their required parent element
Image elements have `[alt]` attributes
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[aria-*]` attributes match their roles
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
`<html>` element has a `[lang]` attribute
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`<html>` element has a valid value for its `[lang]` attribute
`[role]` values are valid
Heading elements appear in a sequentially-descending order
`[aria-*]` attributes have valid values
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[aria-*]` attributes are valid and not misspelled
ARIA IDs are unique
`[role]`s have all required `[aria-*]` attributes
`[aria-hidden="true"]` is not present on the document `<body>`
The page contains a heading, skip link, or landmark region
`<frame>` or `<iframe>` elements have a title
`[aria-hidden="true"]` elements do not contain focusable descendents
Document has a `<title>` element
Desktop Speed
79/100
These checks analyze the performance of who.int on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (6)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Avoid landing page redirects
Leverage browser caching
Minify JavaScript
Enable compression
Optimize images
Passed Audits (4)
Reduce server response time
Minify CSS
Minify HTML
Prioritize visible content
www.who.com
www.who.net
www.who.org
www.who.info
www.who.biz
www.who.us
www.who.mobi
www.ho.int
www.who.int
www.qho.int
www.wqho.int
www.qwho.int
www.aho.int
www.waho.int
www.awho.int
www.sho.int
www.wsho.int
www.swho.int
www.eho.int
www.weho.int
www.ewho.int
www.wo.int
www.wbo.int
www.whbo.int
www.wbho.int
www.wgo.int
www.whgo.int
www.wgho.int
www.wyo.int
www.whyo.int
www.wyho.int
www.wuo.int
www.whuo.int
www.wuho.int
www.wjo.int
www.whjo.int
www.wjho.int
www.wno.int
www.whno.int
www.wnho.int
www.wh.int
www.whi.int
www.whoi.int
www.whio.int
www.whk.int
www.whok.int
www.whko.int
www.whl.int
www.whol.int
www.whlo.int
www.whp.int
www.whop.int
www.whpo.int
www.who.net
www.who.org
www.who.info
www.who.biz
www.who.us
www.who.mobi
www.ho.int
www.who.int
www.qho.int
www.wqho.int
www.qwho.int
www.aho.int
www.waho.int
www.awho.int
www.sho.int
www.wsho.int
www.swho.int
www.eho.int
www.weho.int
www.ewho.int
www.wo.int
www.wbo.int
www.whbo.int
www.wbho.int
www.wgo.int
www.whgo.int
www.wgho.int
www.wyo.int
www.whyo.int
www.wyho.int
www.wuo.int
www.whuo.int
www.wuho.int
www.wjo.int
www.whjo.int
www.wjho.int
www.wno.int
www.whno.int
www.wnho.int
www.wh.int
www.whi.int
www.whoi.int
www.whio.int
www.whk.int
www.whok.int
www.whko.int
www.whl.int
www.whol.int
www.whlo.int
www.whp.int
www.whop.int
www.whpo.int