Skip to content
Audit Complete

Results for https://www.who.int

Visit site
United Stated United Stated · Santa Clara Completed: Apr 4, 2026 17:20 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C75

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

'unsafe-eval' found in script source

Security › Content Security Policy
2

'unsafe-inline' found in script source

Security › Content Security Policy
3

Page weighs 13.8 MB (4.6 MB transferred)

Performance › Page Weight Budget
4

1 control(s) without accessible label

Accessibility › Form Accessibility
5

1 link(s) with no accessible text

Accessibility › Link & Button Quality
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.who.int)](https://beavercheck.com/results/2216aedb-ccc3-4442-970f-9b21643a576f)
<a href="https://beavercheck.com/results/2216aedb-ccc3-4442-970f-9b21643a576f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.who.int" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.who.int

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

26
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

12.64 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

26.97 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2.79 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.039

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

12.64 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

27.33 s

Detailed Report

Audit breakdown by category with detailed findings.

26

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:50.03 source:map[column:33335 line:2 type:source-location url:https://www.who.int/ScriptResource.axd?d=6DQe8ARl7A9TiuWej5ttChzH_bH_8oN_s_nT_Gi4bPGf8e5n2fEMKPjzLdvKHVty-4ZMcWf8z4wR7Uoe9uwfRcpGME2zu76GUYKLUjE5oVOWl9suUmdsLOBTG0SyiZPAlK9FJAXJhhse1qDM4EhvGTqNsxl81NUrAtHLeXR4O4h0ZoaW0&t=ffffffff90b6fa90 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:121.962 source:map[column:169304 line:2 type:source-location url:https://cdn.fundraiseup.com/widget/AMEEWKFZ urlProvider:network]] map[reflowTime:50.03 source:map[column:59949 line:1 type:source-location url:https://www.who.int/ScriptResource.axd?d=6DQe8ARl7A9TiuWej5ttChzH_bH_8oN_s_nT_Gi4bPGf8e5n2fEMKPjzLdvKHVty-4ZMcWf8z4wR7Uoe9uwfRcpGME2zu76GUYKLUjE5oVOWl9suUmdsLOBTG0SyiZPAlK9FJAXJhhse1qDM4EhvGTqNsxl81NUrAtHLeXR4O4h0ZoaW0&t=ffffffff90b6fa90 urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
div.list-view--item > a.link-container > div.thumb > div.background-image div.list-view--item > a.link-container > div.thumb > div.background-image
/media/images/default-source/topics/womens-childrens-and-...33.1 KiB8.3 KiB
div.list-view--item > a.link-container > div.thumb > div.background-image div.list-view--item > a.link-container > div.thumb > div.background-image
/media/images/default-source/topics/populations-demograph...27.5 KiB6.6 KiB
div.list-view--item > a.link-container > div.thumb > div.background-image div.list-view--item > a.link-container > div.thumb > div.background-image
/media/images/default-source/topics/womens-childrens-and-...39.2 KiB6.5 KiB
div.list-view--item > a.link-container > div.thumb > div.background-image div.list-view--item > a.link-container > div.thumb > div.background-image
/media/images/default-source/topics/populations-demograph...33.4 KiB5.8 KiB
World Health Day Find out more div.sf-main-site > section#content > div.hero-image--wrapper > div.inner
/media/images/default-source/headquarters/campaigns/world...59.1 KiB5.1 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-2-DIV
nodeLabel: World Health Day Find out more
path: 1,HTML,1,BODY,7,DIV,7,SECTION,0,DIV,0,DIV
selector: div.sf-main-site > section#content > div.hero-image--wrapper > div.inner
snippet: <div class="inner responsive-background-image high-663685238 bg-center-position" style="background-image: url(&quot;https://cdn.who.int/media/images/default-source/hea…&quot;);">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 160 ms 7.5 KiB
URLTransfer SizeEst Savings
/ScriptResource.axd?d=6DQe8ARl7A9TiuWej5ttChzH_bH_8oN_s_n...41.8 KiB7.5 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

CategoryTime Spent
Script Evaluation4.5 s
Other1.5 s
Script Parsing & Compilation1.2 s
Style & Layout1.1 s
Parse HTML & CSS308 ms
Rendering134 ms
Garbage Collection109 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
Home div.main-footer > div.footer-logo > a > img.logo
www.who.int/ResourcePackages/WHO/assets/dist/images/logos/en/h-logo-white.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 110 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 40 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid non-composited animations
96

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
div.row > div.sf_colsIn > div.slicknav_menu > a.slicknav_btn div.row > div.sf_colsIn > div.slicknav_menu > a.slicknav_btn

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
28 March 2026 News release WHO Member States agree to extend negotiations on k… div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
26 March 2026 News release Encouraging progress in inclusive health policies f… div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
24 March 2026 News release WHO recommends new diagnostic tools to help end TB div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
18 March 2026 Joint News Release Progress in reducing child deaths slows as 4.… div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
2026 One Health Summit, Lyon, France, 5-7 April 2026 5 – 7 April 2026 div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
Film screening and discussion on education for a balance between animal, plant … div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
Together for One Health at the Local Level 6 April 2026 14:00 – 17:30 CET div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
World Health Day World Health Day 2026: Together for health. Stand with scienc… div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
Global Forum of WHO Collaborating Centres: collaborating for a healthier future… div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
`[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 used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
92

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
Loading the image 'https://c.bing.com/c.gif?ctsa=mr&CtsSyncId=289FBCFC921948FFA5E454E1FD06CC4D&RedC=c.clarity.ms&MXFR=28C0F2D9885D679508D7E5E88C5D69B0' violates the following Content Security Policy directive: "img-src 'self' *.gstatic.com *.googleapis.com platform.tumblr.com web.facebook.com www.facebook.com www.redditstatic.com www.linkedin.com i.ytimg.com https://syndication.twitter.com https://static.licdn.com/scds/common/u/images/apps/connect/sprites/sprite_connect_v14.png pbs.twimg.com platform.twitter.com/css/ *.twimg.com data: blob: https://*.googletagmanager.com self https://*.fundraiseup.com https://ucarecdn.com https://pay.google.com https://google.com/pay https://*.paypalobjects.com tracking.monsido.com iris.who.int tiles.arcgis.com www.arcgis.com services.arcgis.com utility.arcgisonline.com cdn.insight.sitefinity.com js.arcgis.com *.nativechat.com *.sharethis.com *.google-analytics.com *.clarity.ms https://delicious.com https://dec.azureedge.net https://apps.who.int https://*.dec.sitefinity.com *.eloqua.com track.hubspot.com stats.g.doubleclick.net *.who.int data.who.int *.who.cloud.sitefinity.com yt3.ggpht.com addthis.com *.googleusercontent.com *.googletagmanager.com script.hotjar.com www.addthis.com log.pinterest.com whosearch.searchblox.com app.powerbi.com pbi.azureedge.net kendo.cdn.telerik.com img.youtube.com *.analytics.google.com *.g.doubleclick.net *.google.com whpelasticdsta01.blob.core.windows.net whpelasticpsta01.blob.core.windows.net whointsfcloudmedia.blob.core.windows.net https://cdn.insight.sitefinity.com web-chat.nativechat.com". The action has been blocked.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

64
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.43 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.98 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

268 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.002

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.35 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

4.79 s

Detailed Report

Audit breakdown by category with detailed findings.

64

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:46.828 source:map[column:33335 line:2 type:source-location url:https://www.who.int/ScriptResource.axd?d=6DQe8ARl7A9TiuWej5ttChzH_bH_8oN_s_nT_Gi4bPGf8e5n2fEMKPjzLdvKHVty-4ZMcWf8z4wR7Uoe9uwfRcpGME2zu76GUYKLUjE5oVOWl9suUmdsLOBTG0SyiZPAlK9FJAXJhhse1qDM4EhvGTqNsxl81NUrAtHLeXR4O4h0ZoaW0&t=ffffffff90b6fa90 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:201.269 source:map[type:text value:[unattributed]]] map[reflowTime:46.828 source:map[column:59949 line:1 type:source-location url:https://www.who.int/ScriptResource.axd?d=6DQe8ARl7A9TiuWej5ttChzH_bH_8oN_s_nT_Gi4bPGf8e5n2fEMKPjzLdvKHVty-4ZMcWf8z4wR7Uoe9uwfRcpGME2zu76GUYKLUjE5oVOWl9suUmdsLOBTG0SyiZPAlK9FJAXJhhse1qDM4EhvGTqNsxl81NUrAtHLeXR4O4h0ZoaW0&t=ffffffff90b6fa90 urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-DIV
nodeLabel: World Health Day Find out more
path: 1,HTML,1,BODY,7,DIV,7,SECTION,0,DIV,0,DIV
selector: div.sf-main-site > section#content > div.hero-image--wrapper > div.inner
snippet: <div class="inner responsive-background-image high-663685238 bg-center-position" style="background-image: url(&quot;https://cdn.who.int/media/images/default-source/hea…&quot;);">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
a.link-container > div.table-cell > div.thumb > div.background-image a.link-container > div.table-cell > div.thumb > div.background-image
/images/default-source/departments/fos/codex/flags-in-who...66.3 KiB41.4 KiB
a.link-container > div.table-cell > div.thumb > div.background-image a.link-container > div.table-cell > div.thumb > div.background-image
/media/images/default-source/topics/determinants-of-healt...42.1 KiB17.3 KiB
a.link-container > div.table-cell > div.thumb > div.background-image a.link-container > div.table-cell > div.thumb > div.background-image
/media/images/default-source/headquarters/campaigns/world...32.4 KiB11.5 KiB
div.list-view--item > a.link-container > div.thumb > div.background-image div.list-view--item > a.link-container > div.thumb > div.background-image
/media/images/default-source/topics/womens-childrens-and-...33.1 KiB8.3 KiB
div.list-view--item > a.link-container > div.thumb > div.background-image div.list-view--item > a.link-container > div.thumb > div.background-image
/media/images/default-source/topics/populations-demograph...27.5 KiB6.6 KiB
div.list-view--item > a.link-container > div.thumb > div.background-image div.list-view--item > a.link-container > div.thumb > div.background-image
/media/images/default-source/topics/womens-childrens-and-...39.2 KiB6.5 KiB
a.link-container > div.table-cell > div.thumb > div.background-image a.link-container > div.table-cell > div.thumb > div.background-image
/media/images/default-source/imported/film-festival/kids-...21.9 KiB6.5 KiB
div.list-view--item > a.link-container > div.thumb > div.background-image div.list-view--item > a.link-container > div.thumb > div.background-image
/media/images/default-source/topics/populations-demograph...33.4 KiB5.8 KiB
a.link-container > div.table-cell > div.thumb > div.background-image a.link-container > div.table-cell > div.thumb > div.background-image
/images/default-source/departments/fos/codex/flags-in-who...6.1 KiB4.3 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

CategoryTime Spent
Script Evaluation1.1 s
Other439 ms
Style & Layout412 ms
Script Parsing & Compilation322 ms
Parse HTML & CSS105 ms
Rendering56 ms
Garbage Collection44 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 0.0 ms 7.5 KiB
URLTransfer SizeEst Savings
/ScriptResource.axd?d=6DQe8ARl7A9TiuWej5ttChzH_bH_8oN_s_n...41.8 KiB7.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
Home div.main-footer > div.footer-logo > a > img.logo
www.who.int/ResourcePackages/WHO/assets/dist/images/logos/en/h-logo-white.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 5 user timings
JavaScript execution time 1.2 s
Avoid long main-thread tasks 10 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 90 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 30 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid non-composited animations
100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
28 March 2026 News release WHO Member States agree to extend negotiations on k… div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
26 March 2026 News release Encouraging progress in inclusive health policies f… div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
24 March 2026 News release WHO recommends new diagnostic tools to help end TB div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
18 March 2026 Joint News Release Progress in reducing child deaths slows as 4.… div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
2026 One Health Summit, Lyon, France, 5-7 April 2026 5 – 7 April 2026 div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
Film screening and discussion on education for a balance between animal, pla… div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
Together for One Health at the Local Level 6 April 2026 14:00 – 17:30 CET div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
World Health Day World Health Day 2026: Together for health. Stand with scie… div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
Global Forum of WHO Collaborating Centres: collaborating for a healthier fut… div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Select elements have associated label elements.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
92

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
Loading the image 'https://c.bing.com/c.gif?ctsa=mr&CtsSyncId=CEE65EAF1AE34D8981D44144A4B0CF3D&RedC=c.clarity.ms&MXFR=3CDE118DE9146BB2372506BCED146580' violates the following Content Security Policy directive: "img-src 'self' *.gstatic.com *.googleapis.com platform.tumblr.com web.facebook.com www.facebook.com www.redditstatic.com www.linkedin.com i.ytimg.com https://syndication.twitter.com https://static.licdn.com/scds/common/u/images/apps/connect/sprites/sprite_connect_v14.png pbs.twimg.com platform.twitter.com/css/ *.twimg.com data: blob: https://*.googletagmanager.com self https://*.fundraiseup.com https://ucarecdn.com https://pay.google.com https://google.com/pay https://*.paypalobjects.com tracking.monsido.com iris.who.int tiles.arcgis.com www.arcgis.com services.arcgis.com utility.arcgisonline.com cdn.insight.sitefinity.com js.arcgis.com *.nativechat.com *.sharethis.com *.google-analytics.com *.clarity.ms https://delicious.com https://dec.azureedge.net https://apps.who.int https://*.dec.sitefinity.com *.eloqua.com track.hubspot.com stats.g.doubleclick.net *.who.int data.who.int *.who.cloud.sitefinity.com yt3.ggpht.com addthis.com *.googleusercontent.com *.googletagmanager.com script.hotjar.com www.addthis.com log.pinterest.com whosearch.searchblox.com app.powerbi.com pbi.azureedge.net kendo.cdn.telerik.com img.youtube.com *.analytics.google.com *.g.doubleclick.net *.google.com whpelasticdsta01.blob.core.windows.net whpelasticpsta01.blob.core.windows.net whointsfcloudmedia.blob.core.windows.net https://cdn.insight.sitefinity.com web-chat.nativechat.com". The action has been blocked.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: '/js/isotope.pkgd.js'. It will be ignored.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback