Skip to content
https://wfp.org

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

33

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:30.983 source:map[column:22772 line:7 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js 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:35.638 source:map[column:7097 line:49 type:source-location url:https://www.wfp.org/sites/default/files/js/js_x1PXGzWuJqEJANHUiLPQ_6sVAwiKRGHC726ZlofPPX4.js?scope=footer&delta=0&language=en&theme=wfp_org&include=eJxtyUEOwyAMBdELhXAky00-BMmxEYZw_aJ200VXI70RcBL0KN_uGd5HA12spxTN2yhUuXc09XihGaUhQn40QOkpJ2z_z9tMlW6uca6PMBF4ZcFnWMvxsLuaQvv-q1nsxRLYHd3fpOg-Yw urlProvider:network]] map[reflowTime:29.993 source:map[column:292645 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:0.239 source:map[column:292989 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:0.751 source:map[column:345853 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-VIDEO
nodeLabel: div > div.field > section.hero-full-screen-video > video.hero-full-screen-video__video
path: 1,HTML,1,BODY,4,DIV,1,MAIN,0,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,SECTION,0,VIDEO
selector: div > div.field > section.hero-full-screen-video > video.hero-full-screen-video__video
snippet: <video role="none" preload="none" class="hero-full-screen-video__video hero-full-screen-video__video--mobile js--he…" style="opacity: 0.6" playsinline="" muted="" loop="" poster="/sites/default/files/2026-04/WF11163961%2020260404_SND_Mohamed-Jamal-Jebre…" autoplay="">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
/sites/default/files/css/css_-cNaOtn89sJPQyO7DmOUJKbrfKGm...80.5 KiB971 ms
/sites/default/files/css/css_SE-YOYmR2HsGnbvle5yXQF2QyaGW...6.0 KiB
/css2?family=Open+Sans:ital,wght@0,400;0,700;0,800;1,400;...2.6 KiB758 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/sites/default/files/fullscreen-hero-video/2026-04/WF1116...1209600.0 s2.7 MiB
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js86400.0 s124.4 KiB
/sites/default/files/styles/card_featured/public/images/n...1209600.0 s266.5 KiB
/sites/default/files/2026-04/WF11163961 20260404_SND_Moha...1209600.0 s172.3 KiB
/sites/default/files/2026-04/WF11163961 20260404_SND_Moha...1209600.0 s172.3 KiB
/sites/default/files/styles/card_featured/public/images/n...1209600.0 s150.6 KiB
/sites/default/files/styles/card_featured/public/2026-03/...1209600.0 s108.3 KiB
/sites/default/files/js/js_x1PXGzWuJqEJANHUiLPQ_6sVAwiKRG...1209600.0 s106.8 KiB
/guides/ui/assets/v0.0.1/logos/standard/en/wfp-logo-stand...0.0 ms9.9 KiB
/guides/ui/assets/v0.0.1/logos/vertical/en/wfp-logo-verti...0.0 ms9.8 KiB
/sites/default/files/styles/card_featured/public/2026-04/...1209600.0 s98.1 KiB
/logos/5201e374-2f45-4337-89ef-a5130c7191e0/019a2504-bdc3...86400.0 s21.1 KiB
/sites/default/files/css/css_-cNaOtn89sJPQyO7DmOUJKbrfKGm...1209600.0 s80.5 KiB
/sites/default/files/styles/card_featured/public/images/W...1209600.0 s77.7 KiB
/sites/default/files/styles/card_featured/public/2026-03/...1209600.0 s40.7 KiB
/scripttemplates/otSDKStub.js?did=018e1e5b-47a9-7e90-8ba7...86400.0 s9.1 KiB
www.wfp.org/sites/default/files/2023-03/social%20protection.svg1209600.0 s14.5 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.5 KiB
www.wfp.org/sites/default/files/2023-03/nutrition.svg1209600.0 s9.9 KiB
www.wfp.org/sites/default/files/2023-03/school%20programme.svg1209600.0 s9.3 KiB
www.wfp.org/sites/default/files/2023-03/climate%20action.svg1209600.0 s6.5 KiB
/sites/default/files/css/css_SE-YOYmR2HsGnbvle5yXQF2QyaGW...1209600.0 s6.0 KiB
www.wfp.org/sites/default/files/2023-03/cash-based%20transfers.svg1209600.0 s4.6 KiB
cdn.wfp.org/ew/ew-en.js0.0 ms373 B
www.wfp.org/sites/default/files/2023-03/gender.svg1209600.0 s3.3 KiB
www.wfp.org/sites/default/files/2023-03/innovation.svg1209600.0 s2.9 KiB
www.wfp.org/sites/default/files/2023-03/resilience2.svg1209600.0 s2.8 KiB
www.wfp.org/sites/default/files/2023-03/emergencies.svg1209600.0 s2.4 KiB
/themes/custom/wfp_org/templates/patterns/menu/images/clo...1209600.0 s774 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
article.explore-new__item > a > div.explore-new__item-image > div article.explore-new__item > a > div.explore-new__item-image > div
/sites/default/files/styles/card_featured/public/images/n...265.9 KiB215.9 KiB
article.explore-new__item > a > div.explore-new__item-image > div article.explore-new__item > a > div.explore-new__item-image > div
/sites/default/files/styles/card_featured/public/images/n...150.2 KiB87.5 KiB
div > div.field > section.hero-full-screen-video > video.hero-full-screen-video__video div > div.field > section.hero-full-screen-video > video.hero-full-screen-video__video
/sites/default/files/2026-04/WF11163961 20260404_SND_Moha...171.9 KiB76.5 KiB
article.explore-new__item > a > div.explore-new__item-image > div article.explore-new__item > a > div.explore-new__item-image > div
/sites/default/files/styles/card_featured/public/2026-03/...108.0 KiB44.0 KiB
article.explore-new__item > a > div.explore-new__item-image > div article.explore-new__item > a > div.explore-new__item-image > div
/sites/default/files/styles/card_featured/public/2026-04/...97.8 KiB33.8 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 858 ms
URLTime Spent
wfp.org/858 ms
www.wfp.org/0.0 ms

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 92.1 KiB
URLTransfer SizeEst Savings
/sites/default/files/css/css_-cNaOtn89sJPQyO7DmOUJKbrfKGm...80.3 KiB73.6 KiB
21.2 KiB18.5 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 300 ms 702.8 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-F7MC9KQVZS&cx=c&gtm=4e64h1173.0 KiB71.3 KiB
www.googletagmanager.com/gtag/js?id=G-TL7TXTVCYL&cx=c&gtm=4e64h1173.5 KiB71.1 KiB
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js124.3 KiB66.3 KiB
/sites/default/files/js/js_x1PXGzWuJqEJANHUiLPQ_6sVAwiKRG...105.5 KiB64.3 KiB
www.googletagmanager.com/gtag/js?id=AW-784352746&cx=c&gtm=4e64h1134.2 KiB64.2 KiB
www.googletagmanager.com/gtag/js?id=AW-597680250&cx=c&gtm=4e64h1136.7 KiB63.9 KiB
www.googletagmanager.com/gtag/js?id=DC-10390555&cx=c&gtm=4e64h1129.4 KiB62.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-KN3K8D183.3 KiB60.1 KiB
www.googletagmanager.com/gtag/js?id=DC-5499309&cx=c&gtm=4e64h1126.1 KiB59.9 KiB
www.googletagmanager.com/gtag/js?id=AW-1005839990&cx=c&gtm=4e64h1137.5 KiB59.7 KiB
www.googletagmanager.com/gtag/js?id=AW-347102041&cx=c&gtm=4e64h1137.0 KiB59.5 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.googletagmanager.com/gtm.js?id=GTM-KN3K8D2.4 s2.0 s128 ms
/sites/default/files/js/js_x1PXGzWuJqEJANHUiLPQ_6sVAwiKRG...1.7 s1.1 s59 ms
Unattributable1.2 s29 ms0.0 ms
www.wfp.org/867 ms10 ms1.9 ms
cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js567 ms332 ms76 ms
www.googletagmanager.com/gtag/js?id=G-F7MC9KQVZS&cx=c&gtm=4e64h1394 ms305 ms84 ms
www.googletagmanager.com/gtag/js?id=G-TL7TXTVCYL&cx=c&gtm=4e64h1387 ms298 ms85 ms
www.googletagmanager.com/gtag/js?id=AW-347102041&cx=c&gtm=4e64h1348 ms261 ms79 ms
www.googletagmanager.com/gtag/js?id=AW-1005839990&cx=c&gtm=4e64h1272 ms194 ms60 ms
www.googletagmanager.com/gtag/js?id=AW-597680250&cx=c&gtm=4e64h1266 ms186 ms64 ms
www.googletagmanager.com/gtag/js?id=DC-10390555&cx=c&gtm=4e64h1257 ms200 ms55 ms
www.googletagmanager.com/gtag/js?id=AW-784352746&cx=c&gtm=4e64h1234 ms171 ms60 ms
www.googletagmanager.com/gtag/js?id=DC-5499309&cx=c&gtm=4e64h1220 ms166 ms50 ms
/scripttemplates/otSDKStub.js?did=018e1e5b-47a9-7e90-8ba7...151 ms133 ms4.7 ms
bat.bing.com/bat.js51 ms40 ms10 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation5.5 s
Other1.7 s
Style & Layout845 ms
Script Parsing & Compilation816 ms
Garbage Collection382 ms
Rendering139 ms
Parse HTML & CSS131 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
/sites/default/files/fullscreen-hero-video/2026-04/WF1116...2.7 MiB
www.wfp.org/sites/default/files/wfp-map/where_we_are/en.js?g=17767764011.5 MiB
/sites/default/files/styles/card_featured/public/images/n...266.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-KN3K8D183.6 KiB
www.googletagmanager.com/gtag/js?id=G-TL7TXTVCYL&cx=c&gtm=4e64h1173.6 KiB
www.googletagmanager.com/gtag/js?id=G-F7MC9KQVZS&cx=c&gtm=4e64h1173.1 KiB
/sites/default/files/2026-04/WF11163961 20260404_SND_Moha...172.3 KiB
/sites/default/files/2026-04/WF11163961 20260404_SND_Moha...172.3 KiB
/sites/default/files/styles/card_featured/public/images/n...150.6 KiB
www.googletagmanager.com/gtag/js?id=AW-1005839990&cx=c&gtm=4e64h1137.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
UN World Food Programme section.site-footer__institutional > div.wfp-wrapper > div.site-footer__branding > img.site-footer__logo
/guides/ui/assets/v0.0.1/logos/standard/en/wfp-logo-stand...
UN World Food Programme div.site-header__wrapper > div.site-header__branding > a.site-header__logo > img
/guides/ui/assets/v0.0.1/logos/vertical/en/wfp-logo-verti...

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 20 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 90 ms
●Server Backend Latencies 30 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 190 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○Avoid non-composited animations
95

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Visit X div.wfp-wrapper > div.site-footer__social-links > div.site-footer__social-links-icons > a
Visit Facebook div.wfp-wrapper > div.site-footer__social-links > div.site-footer__social-links-icons > a
Visit Instagram div.wfp-wrapper > div.site-footer__social-links > div.site-footer__social-links-icons > a
Visit Linkedin div.wfp-wrapper > div.site-footer__social-links > div.site-footer__social-links-icons > a
Visit YouTube div.wfp-wrapper > div.site-footer__social-links > div.site-footer__social-links-icons > a
Visit TikTok div.wfp-wrapper > div.site-footer__social-links > div.site-footer__social-links-icons > a
Cookies Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●`<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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○`<frame>` or `<iframe>` elements have a title
○`<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.
○Skip links are focusable.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
bat.bing.com/bat.js
Connecting to 'https://bat.bing.net/actionp/0?ti=22021902&tm=gtm002&Ver=2&mid=5773ac10-3cca-401b-99c8-e311da22323d&bo=1&evt=consent&src=update&cdb=AQER&asc=D' violates the following Content Security Policy directive: "connect-src 'self' data: analytics.tiktok.com wcs.naver.com tiles.arcgis.com spring.wfp.org *.spring.wfp.org cdn.wfp.org geonode.wfp.org *.google-analytics.com *.analytics.google.com *.googletagmanager.com analytics.google.com api.mapbox.com geoip.nekudo.com api.ipify.org api.ip2country.info mycountry.picktek.org content.jwplatform.com *.jwpsrv.com cdn.jwplayer.com acr.api.spring.wfp.org cdn.sparkcentral.com *.smooch.io *.user1st.info stats.g.doubleclick.net fh.mg.wfp.org geoip.maxmind.com www.juicer.io juicer.io graph.facebook.com *.typekit.net *.sentry.io bat.bing.com *.hotjar.com *.hotjar.io *.jwpltx.com logx.optimizely.com *.optimizely.com https://pagead2.googlesyndication.com https://www.googleadservices.com https://www.google.com https://google.com https://ad.doubleclick.net https://googleads.g.doubleclick.net https://*.onetrust.com https://cdn.cookielaw.org https://cookie-cdn.cookiepro.com 'self' ws: https://o274918.ingest.sentry.io/api/5249464/envelope/". The action has been blocked.
bat.bing.com/bat.js
Connecting to 'https://bat.bing.net/actionp/0?ti=22021902&tm=gtm002&Ver=2&mid=5773ac10-3cca-401b-99c8-e311da22323d&bo=2&evt=consent&src=default&cdb=AQER&asc=D' violates the following Content Security Policy directive: "connect-src 'self' data: analytics.tiktok.com wcs.naver.com tiles.arcgis.com spring.wfp.org *.spring.wfp.org cdn.wfp.org geonode.wfp.org *.google-analytics.com *.analytics.google.com *.googletagmanager.com analytics.google.com api.mapbox.com geoip.nekudo.com api.ipify.org api.ip2country.info mycountry.picktek.org content.jwplatform.com *.jwpsrv.com cdn.jwplayer.com acr.api.spring.wfp.org cdn.sparkcentral.com *.smooch.io *.user1st.info stats.g.doubleclick.net fh.mg.wfp.org geoip.maxmind.com www.juicer.io juicer.io graph.facebook.com *.typekit.net *.sentry.io bat.bing.com *.hotjar.com *.hotjar.io *.jwpltx.com logx.optimizely.com *.optimizely.com https://pagead2.googlesyndication.com https://www.googleadservices.com https://www.google.com https://google.com https://ad.doubleclick.net https://googleads.g.doubleclick.net https://*.onetrust.com https://cdn.cookielaw.org https://cookie-cdn.cookiepro.com 'self' ws: https://o274918.ingest.sentry.io/api/5249464/envelope/". The action has been blocked.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
85

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.wfp.org/media-and-resourcesRead more
www.wfp.org/who-we-areRead more
www.wfp.org/our-workRead more
www.wfp.org/countriesRead more
www.wfp.org/get-involvedRead more
/stories/sudans-war-three-years-shattered-dreams-soaring-...READ MORE
www.wfp.org/who-we-areREAD MORE

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
div.site-header__wrapper > div.navigation-main > div.navigation-main__mobile-togglers > a.search-overlay__toggler div.site-header__wrapper > div.navigation-main > div.navigation-main__mobile-togglers > a.search-overlay__toggler
div#navigation-main__panel > div.navigation-main__panel-content > nav.menu-secondary > a.search-overlay__toggler div#navigation-main__panel > div.navigation-main__panel-content > nav.menu-secondary > a.search-overlay__toggler
× div#where-we-are-map > div.leaflet-control-container > div.leaflet-sidebar > a.close
body.homepage > div.dialog-off-canvas-main-canvas > div#search-overlay > a.fullscreen-overlay__closer body.homepage > div.dialog-off-canvas-main-canvas > div#search-overlay > a.fullscreen-overlay__closer

To appear in search results, crawlers need access to your app.

○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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback