Skip to content
Audit Complete

Results for https://fao.org

Visit site
Spain Spain · Madrid Completed: Apr 21, 2026 18:58 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 69 / 100

Based on 8 categories, 0 sections

Room to improve — your 40.4s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

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.

How the composite score is calculated

How you compare

CMS · 826 peers
You 69
·
Avg 73
At average
0 50 100
Better than 2% of CMS sites
Amazon Route 53 · 544 peers
You 69
·
Avg 72
At average
0 50 100
Better than 8% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

Page weighs 39.4 MB (18.7 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

1 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Ffao.org)](https://beavercheck.com/results/67a2d8d5-00cb-4fb8-9a41-d4d7ee5bac8c)
<a href="https://beavercheck.com/results/67a2d8d5-00cb-4fb8-9a41-d4d7ee5bac8c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ffao.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Ffao.org

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 40.4s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 40.4s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~29%.

Speed (2)

Page takes 40.4s to load

+12% bounce

Users abandon at ~3s — you're 37.9s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 1.2s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€275 investment → €4.35/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -81%

Investment

€275

5h · 5 findings

Monthly returns

€4.35 /mo

~€52 / year

  • Bandwidth savings €4.35

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

€83 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€275

5.0 developer hours at €55/hr

Based on Italy rates (€55/hr)

Quick wins
€83 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,671 / month at risk

~€120,500,052 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 10,000 – EUR 20,000,000

+12 more

Bandwidth Waste

€4.35 /mo

58783.0 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~5.9 MB per page load
    Saves €4.35/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

31
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
81
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
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.

30.83 s

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

40.42 s

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

1.25 s

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

0.000

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

30.83 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.

76.11 s

Detailed Report

Audit breakdown by category with detailed findings.

31

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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
www.fao.org/interactive/hunger-map/assets/main.D1rpvYek.js0.0 ms790.1 KiB
www.fao.org/interactive/hunger-map/assets/main.C7hNZ7Rm.css0.0 ms37.9 KiB
i.ytimg.com/vi/84xaHTYhBUk/sddefault.jpg7200.0 s44.6 KiB
dwt.soundcloud.com/tags.js3600.0 s40.7 KiB
i.ytimg.com/vi_webp/C1_-Vjg_TKQ/sddefault.webp300.0 s23.8 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s46.6 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s45.2 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s42.0 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s34.0 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s29.5 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s27.8 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s24.5 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s24.1 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s15.7 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s15.4 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s15.3 KiB
www.fao.org/interactive/hunger-map/assets/fao-logo-en.BOvgbPyA.svg0.0 ms4.0 KiB
cdn.matomo.cloud/fao-web.matomo.cloud/matomo.js691200.0 s39.0 KiB
/Frontend-Assembly/SitefinityWebApp/Mvc/Scripts/FaoLangua...86314.0 s9.1 KiB
cse.google.com/cse.js?cx=018170620143701104933:qq82jsfba7w0.0 ms3.6 KiB
w.soundcloud.com/player/api.js300.0 s3.5 KiB
cse.google.com/cse.js?cx=018170620143701104933%3Aqq82jsfba7w0.0 ms3.4 KiB
www.fao.org/interactive/hunger-map/assets/fao-logo-mobile.QRq5n-IW.svg0.0 ms2.7 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s3.9 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s2.8 KiB
cdn.insight.sitefinity.com/sdk/sitefinity-insight-client.min.3.1.44.js604800.0 s11.3 KiB
www.google.com/cse/static/style/look/v6/default.css3000.0 s1.2 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s1.2 KiB
static.doubleclick.net/instream/ad_status.js900.0 s494 B
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s1022 B
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s580 B
cdn.matomo.cloud/fao-web.matomo.cloud/matomo.js691200.0 s0 B
static.doubleclick.net/instream/ad_status.js900.0 s0 B

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.

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.

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:15.331 source:map[column:56 line:3879 type:source-location url:https://www.fao.org/home/en 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:94.247 source:map[column:15777 line:3621 type:source-location url:https://www.fao.org/home/en urlProvider:network]] map[reflowTime:6.009 source:map[column:9716 line:12 type:source-location url:https://unpkg.com/swiper@6.7.0/swiper-bundle.min.js urlProvider:network]] map[reflowTime:10.235 source:map[column:34577 line:12 type:source-location url:https://unpkg.com/swiper@6.7.0/swiper-bundle.min.js urlProvider:network]] map[reflowTime:75.003 source:map[type:text value:[unattributed]]] map[reflowTime:9.991 source:map[column:280 line:358 type:source-location url:https://www.google.com/cse/static/element/b33cba5881f68fbf/cse_element__en.js?usqp=CAI%3D urlProvider:network]] map[reflowTime:1.173 source:map[column:168 line:284 type:source-location url:https://www.google.com/cse/static/element/b33cba5881f68fbf/cse_element__en.js?usqp=CAI%3D urlProvider:network]] map[reflowTime:0.408 source:map[column:390 line:508 type:source-location url:https://www.google.com/cse/static/element/b33cba5881f68fbf/cse_element__en.js?usqp=CAI%3D urlProvider:network]] map[reflowTime:2.978 source:map[column:51057 line:6 type:source-location url:https://www.fao.org/interactive/hunger-map/assets/main.D1rpvYek.js urlProvider:network]] map[reflowTime:0.037 source:map[column:376 line:815 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-NF26VFCDMB&cx=c&gtm=4e64h1 urlProvider:network]] map[reflowTime:2.269 source:map[column:128348 line:2031 type:source-location url:https://www.fao.org/home/en urlProvider:network]] map[reflowTime:0.05 source:map[column:55 line:846 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-NF26VFCDMB&cx=c&gtm=4e64h1 urlProvider:network]] map[reflowTime:0.047 source:map[column:896 line:108 type:source-location url:https://cdn.matomo.cloud/fao-web.matomo.cloud/matomo.js urlProvider:network]] map[reflowTime:1.707 source:map[column:54254 line:2031 type:source-location url:https://www.fao.org/home/en 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.row > div.col-md-12 > div.hero-banner > video.hero-banner-video
path: 1,HTML,1,BODY,0,DIV,5,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.row > div.col-md-12 > div.hero-banner > video.hero-banner-video
snippet: <video class="hero-banner-video" loop="" autoplay="" playsinline="" preload="auto">

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

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
div#Contentplaceholder1_C028_Col02 > div.card > div.card-image > img div#Contentplaceholder1_C028_Col02 > div.card > div.card-image > img
/media/images/homepagelibraries/other/fao-response-to-glo...624.8 KiB608.5 KiB
div#Contentplaceholder1_C007_Col01 > div.card > div.card-image > img div#Contentplaceholder1_C007_Col01 > div.card > div.card-image > img
www.fao.org/media/images/homepagelibraries/sdgs/gaza-hp.jpg?sfvrsn=b3a8e8d9_13445.4 KiB429.1 KiB
div#Contentplaceholder1_C140_Col00 > div.card > div.card-image > img div#Contentplaceholder1_C140_Col00 > div.card > div.card-image > img
/media/images/homepagelibraries/other/emergency.jpg?sfvrs...114.4 KiB98.1 KiB
div#Contentplaceholder1_C028_Col00 > div.card > div.card-image > img div#Contentplaceholder1_C028_Col00 > div.card > div.card-image > img
www.fao.org/media/images/homepagelibraries/in-focus/aprc38.jpg?sfvrsn=5678afdd_196.9 KiB78.5 KiB
div#Contentplaceholder1_C028_Col01 > div.card > div.card-image > img div#Contentplaceholder1_C028_Col01 > div.card > div.card-image > img
www.fao.org/media/images/homepagelibraries/in-focus/nerc38.jpg?sfvrsn=bc70052a_590.2 KiB71.9 KiB
div#Contentplaceholder1_C140_Col01 > div.card > div.card-image > img div#Contentplaceholder1_C140_Col01 > div.card > div.card-image > img
/media/images/homepagelibraries/publications/screenshot-2...87.3 KiB69.2 KiB
div#Contentplaceholder1_C007_Col00 > div.card > div.card-image > img div#Contentplaceholder1_C007_Col00 > div.card > div.card-image > img
/media/images/homepagelibraries/data/xmtcdlbpodcast26y.jp...85.8 KiB65.1 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

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: 2.0 s
URLTime Spent
fao.org/807 ms
www.fao.org/home/en1.2 s
www.fao.org/home/en0.0 ms

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.

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.

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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 Evaluation17.9 s
Other4.7 s
Style & Layout1.3 s
Script Parsing & Compilation839 ms
Rendering673 ms
Garbage Collection428 ms
Parse HTML & CSS374 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in a sub frame.Actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.7 KiB
URLTransfer SizeEst Savings
/ScriptResource.axd?d=6DQe8ARl7A9TiuWej5ttCsl0UxczkFZDbeL...31.6 KiB5.7 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
Logo Giahs div#map > div.ui-giahs > a > img
www.fao.org/images/homepagelibraries/default-album/logo-giahs.svg
Food and Agriculture Organization of the United Nations div#Contentplaceholder1_T198B1AC4005_Col00 > div.footer-logo > div.sfContentBlock > img
/media/images/corporatenavigationlibraries/default-album/...
icon-bluesky ul.list-inline > li.list-inline-item > a > img
www.fao.org/images/corporatelibraries/social-icons/bluesky.svg?sfvrsn=91618a92_1
icon-facebook ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-faceb...
icon-instagram ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-insta...
icon-linkedin ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-linke...
icon-soundcloud ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-sound...
icon-tiktok ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-tikto...
icon-tuotiao ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-tuoti...
icon-wechat ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-wecha...
icon-weibo ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-weibo...
icon-X ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-twitt...
icon-youtube ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-youtu...
icon-whatsapp ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/whatsapp-icon.svg...

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

Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 23 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 2 animated elements found
Network Requests
Network Round Trip Times 50 ms
Server Backend Latencies 440 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 50 ms
INP breakdown
Avoid large layout shifts
81

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
tbody > tr > td.gsc-search-button > button.gsc-search-button tbody > tr > td.gsc-search-button > button.gsc-search-button
div.sdg-mobile > div.swiper-container > div.swiper-button > button.btn div.sdg-mobile > div.swiper-container > div.swiper-button > button.btn
div.sdg-mobile > div.swiper-container > div.swiper-button > button.btn div.sdg-mobile > div.swiper-container > div.swiper-button > button.btn
div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-in div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-in
div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-out div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-out

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#Contentplaceholder1_C017_Col01 > div.d-list > div.d-list-visual > iframe div#Contentplaceholder1_C017_Col01 > div.d-list > div.d-list-visual > iframe

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEWS div#Contentplaceholder1_C007_Col00 > div.card > div.card-body > h6.title-category
STORY div#Contentplaceholder1_C007_Col01 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C028_Col00 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C028_Col01 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C028_Col02 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C140_Col00 > div.card > div.card-body > h6.title-category
PUBLICATION div#Contentplaceholder1_C140_Col01 > div.card > div.card-body > h6.title-category
INTERACTIVE STORY div#Contentplaceholder1_C140_Col02 > div.card > div.card-body > h6.title-category
FACEBOOK div#Contentplaceholder1_C013_Col00 > div.card > div.card-body > h6.title-category
INSTAGRAM div#Contentplaceholder1_C013_Col02 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C071_Col00 > div.card > div.card-body > h6.title-category
PUBLICATION div#Contentplaceholder1_C071_Col01 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C071_Col02 > div.card > div.card-body > h6.title-category
FOLLOW US ON div#Contentplaceholder1_T198B1AC4005_Col00 > div.footer-social > div.sfContentBlock > h6.title-category

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SOFI 2025 div.row > div.col-lg-6 > p > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Highlights div#Contentplaceholder1_C008_Col00 > div > div.sfContentBlock > h5.sub-title
Mapping undernourishment and food insecurity worldwide div.container > div.row > div.col-lg-6 > h6
IN FOCUS div#Contentplaceholder1_C071_Col00 > div.card > div.card-body > h6.title-category
BLOG widget-popup > div.popup-wrapper > div.pop-body > h6.title-category
FOLLOW US ON div#Contentplaceholder1_T198B1AC4005_Col00 > div.footer-social > div.sfContentBlock > h6.title-category

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Next slide div#Contentplaceholder1_C047_Col00 > div.sdg-mobile > div.swiper-container > div.swiper-button
Jobs div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Contact us div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Terms and Conditions div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Data protection and privacy div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Scam Alert div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Report Misconduct div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Transparency and accountability div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Procurement div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

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
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
`[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.
`button`, `link`, and `menuitem` elements have accessible names
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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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 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
`<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
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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.
77

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.fao.org/home/enAllowed

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
www.fao.org/home/en line 2290, col 16
TypeError: utility.setBreadcrumbActiveItemTitle is not a function at HTMLDocument.<anonymous> (https://www.fao.org/home/en:2291:17)
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
No issues in the `Issues` panel in Chrome Devtools
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
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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

24
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
80
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
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.70 s

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

3.57 s

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

3.68 s

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

0.248

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

3.58 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.

10.86 s

Detailed Report

Audit breakdown by category with detailed findings.

24

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.24837599999999999] map[node:map[boundingRect:map[bottom:2441 height:1825 left:105 right:1245 top:616 width:1140] lhId:page-16-DIV nodeLabel: Highlights Director-General NEWS Strait of Hormuz: Protracted crisis could … path:1,HTML,1,BODY,0,DIV,6,DIV selector:body.template-corporate > div > div#Contentplaceholder1_C001_Col00 snippet:<div id="Contentplaceholder1_C001_Col00" class="sf_colsIn container" data-sf-element="Container" data-placeholder-label="Container"> type:node] score:0.237507] map[node:map[boundingRect:map[bottom:1260 height:518 left:105 right:1245 top:742 width:1140] lhId:page-21-DIV nodeLabel:NEWS Strait of Hormuz: Protracted crisis could turn into global agrifood catast… path:1,HTML,1,BODY,0,DIV,6,DIV,2,DIV selector:body.template-corporate > div > div#Contentplaceholder1_C001_Col00 > div.row snippet:<div class="row card-image-fix" data-sf-element="Row"> type:node] score:0.008355] map[node:map[boundingRect:map[bottom:1106 height:111 left:894 right:1203 top:995 width:309] lhId:page-12-A nodeLabel:Conflict in the Near East region adds pressure on fragile agrifood systems, FAO… path:1,HTML,1,BODY,0,DIV,6,DIV,2,DIV,2,DIV,0,DIV,1,DIV,0,H5,0,A selector:div.card > div.card-body > h5.card-title > a.title-link snippet:<a href="https://www.fao.org/newsroom/detail/conflict-in-the-near-east-region-adds-…" class="title-link title-link stretched-link" target="_blank"> type:node] score:0.002514] map[node:map[boundingRect:map[bottom:26 height:16 left:8 right:1342 top:10 width:1334] lhId:page-19-P nodeLabel:PREVALENCE OF UNDERNOURISHMENT (PERCENT) (3-YEAR AVERAGE) path:1,HTML,1,BODY,6,DIV,4,MAIN,8,P selector:body.embed-map > div.preloader > main > p.header-title snippet:<p class="header-title text-center"> type:node] score:0]]

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:19.596 source:map[column:56 line:3879 type:source-location url:https://www.fao.org/home/en 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:186.625 source:map[type:text value:[unattributed]]] map[reflowTime:24.954 source:map[column:15777 line:3621 type:source-location url:https://www.fao.org/home/en urlProvider:network]] map[reflowTime:0.114 source:map[column:3965 line:0 type:source-location url:https://www.fao.org/WebResource.axd?d=NjxTqR2bqTw1rewxxlkHPoBB5CDatGYzZ3CWgf1FPNEBuDUZPbAL6EI4dDKbkSdIDdnRDsMyEI1n0bYSuQyPjOMXCNtK20UMe0VarzrEJK3kSl-dB6u-nSg0V62BML_GKgsoVZeWfO-Bb3BI27iNMkTOw9HcDWBzxMNlHZ9B2lK0g7tyFX7r8CxiFBcic142WC75xOF1g27QH0LQ_zZEqJqimpg1T2wEwSEcGdIePyI1&t=638875725940000000 urlProvider:network]] map[reflowTime:8.587 source:map[column:9716 line:12 type:source-location url:https://unpkg.com/swiper@6.7.0/swiper-bundle.min.js urlProvider:network]] map[reflowTime:11.31 source:map[column:34577 line:12 type:source-location url:https://unpkg.com/swiper@6.7.0/swiper-bundle.min.js urlProvider:network]] map[reflowTime:13.574 source:map[column:280 line:386 type:source-location url:https://www.google.com/cse/static/element/dc329f57de078f5d/cse_element__en.js?usqp=CAM%3D urlProvider:network]] map[reflowTime:1.123 source:map[column:390 line:537 type:source-location url:https://www.google.com/cse/static/element/dc329f57de078f5d/cse_element__en.js?usqp=CAM%3D urlProvider:network]] map[reflowTime:0.281 source:map[column:376 line:815 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-NF26VFCDMB&cx=c&gtm=4e64h1 urlProvider:network]] map[reflowTime:3.341 source:map[column:128348 line:2031 type:source-location url:https://www.fao.org/home/en urlProvider:network]] map[reflowTime:1.618 source:map[column:54254 line:2031 type:source-location url:https://www.fao.org/home/en urlProvider:network]] map[reflowTime:0.203 source:map[column:376 line:815 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-NF26VFCDMB&cx=c&gtm=4e64h1 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div#Contentplaceholder1_C028_Col02 > div.card > div.card-image > img div#Contentplaceholder1_C028_Col02 > div.card > div.card-image > img
/media/images/homepagelibraries/other/fao-response-to-glo...624.8 KiB611.1 KiB
div#Contentplaceholder1_C007_Col01 > div.card > div.card-image > img div#Contentplaceholder1_C007_Col01 > div.card > div.card-image > img
www.fao.org/media/images/homepagelibraries/sdgs/gaza-hp.jpg?sfvrsn=b3a8e8d9_13445.4 KiB431.7 KiB
div#Contentplaceholder1_C007_Col02 > div.card > div.card-image > img div#Contentplaceholder1_C007_Col02 > div.card > div.card-image > img
/media/images/homepagelibraries/data/whatsapp-image-2026-...400.7 KiB387.1 KiB
div#Contentplaceholder1_C140_Col00 > div.card > div.card-image > img div#Contentplaceholder1_C140_Col00 > div.card > div.card-image > img
/media/images/homepagelibraries/other/emergency.jpg?sfvrs...114.4 KiB100.6 KiB
div#Contentplaceholder1_C028_Col00 > div.card > div.card-image > img div#Contentplaceholder1_C028_Col00 > div.card > div.card-image > img
www.fao.org/media/images/homepagelibraries/in-focus/aprc38.jpg?sfvrsn=5678afdd_196.9 KiB81.4 KiB
div#Contentplaceholder1_C140_Col02 > div.card > div.card-image > img div#Contentplaceholder1_C140_Col02 > div.card > div.card-image > img
/media/images/homepagelibraries/interactive-stories/sofa2...92.3 KiB78.6 KiB
div#Contentplaceholder1_C028_Col01 > div.card > div.card-image > img div#Contentplaceholder1_C028_Col01 > div.card > div.card-image > img
www.fao.org/media/images/homepagelibraries/in-focus/nerc38.jpg?sfvrsn=bc70052a_590.2 KiB74.8 KiB
div#Contentplaceholder1_C013_Col01 > div.card > div.card-image > img div#Contentplaceholder1_C013_Col01 > div.card > div.card-image > img
/media/images/homepagelibraries/social-media/en-x-17-apr6...76.6 KiB72.7 KiB
div#Contentplaceholder1_C140_Col01 > div.card > div.card-image > img div#Contentplaceholder1_C140_Col01 > div.card > div.card-image > img
/media/images/homepagelibraries/publications/screenshot-2...87.3 KiB72.1 KiB
div#Contentplaceholder1_C007_Col00 > div.card > div.card-image > img div#Contentplaceholder1_C007_Col00 > div.card > div.card-image > img
/media/images/homepagelibraries/data/xmtcdlbpodcast26y.jp...85.8 KiB68.4 KiB
div#Contentplaceholder1_C013_Col00 > div.card > div.card-image > img div#Contentplaceholder1_C013_Col00 > div.card > div.card-image > img
/media/images/homepagelibraries/social-media/en-fb-17-apr...70.2 KiB66.3 KiB
div#Contentplaceholder1_C013_Col02 > div.card > div.card-image > img div#Contentplaceholder1_C013_Col02 > div.card > div.card-image > img
/media/images/homepagelibraries/social-media/en-ig-17-apr...44.3 KiB40.4 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...50.4 KiB39.7 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...46.3 KiB35.7 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...44.9 KiB34.2 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...43.8 KiB33.1 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...41.8 KiB31.1 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...38.5 KiB27.8 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...33.7 KiB23.1 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...33.2 KiB22.5 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...29.3 KiB18.7 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...27.7 KiB17.1 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...24.2 KiB13.6 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...24.1 KiB13.4 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...23.8 KiB13.1 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...22.0 KiB11.3 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...19.3 KiB8.6 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...17.4 KiB6.7 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...15.6 KiB4.9 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...15.3 KiB4.6 KiB
div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile div.leaflet-pane > div.leaflet-layer > div.leaflet-tile-container > img.leaflet-tile
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...15.2 KiB4.5 KiB

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-9-IMG
nodeLabel: div#Contentplaceholder1_C007_Col00 > div.card > div.card-image > img
path: 1,HTML,1,BODY,0,DIV,6,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div#Contentplaceholder1_C007_Col00 > div.card > div.card-image > img
snippet: <img src="https://www.fao.org/media/images/homepagelibraries/data/xmtcdlbpodcast26y.…" alt="" loading="lazy">

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

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
www.fao.org/interactive/hunger-map/assets/main.D1rpvYek.js0.0 ms789.6 KiB
i.ytimg.com/vi_webp/C1_-Vjg_TKQ/maxresdefault.webp300.0 s63.0 KiB
www.fao.org/interactive/hunger-map/assets/main.C7hNZ7Rm.css0.0 ms37.9 KiB
i.ytimg.com/vi/84xaHTYhBUk/sddefault.jpg7200.0 s44.6 KiB
dwt.soundcloud.com/tags.js3600.0 s40.7 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s50.8 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s46.6 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s45.1 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s44.1 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s42.1 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s38.8 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s34.2 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s33.5 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s29.5 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s27.8 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s24.4 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s24.3 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s24.1 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s22.0 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s19.6 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s17.6 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s15.7 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s15.4 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s15.3 KiB
www.fao.org/interactive/hunger-map/assets/fao-logo-en.BOvgbPyA.svg0.0 ms4.0 KiB
cse.google.com/cse.js?cx=018170620143701104933:qq82jsfba7w0.0 ms3.9 KiB
cdn.matomo.cloud/fao-web.matomo.cloud/matomo.js691200.0 s39.0 KiB
/Frontend-Assembly/SitefinityWebApp/Mvc/Scripts/FaoLangua...86314.0 s9.1 KiB
cse.google.com/cse.js?cx=018170620143701104933%3Aqq82jsfba7w0.0 ms3.6 KiB
w.soundcloud.com/player/api.js300.0 s3.5 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s4.5 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s4.0 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s3.9 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s2.8 KiB
cdn.insight.sitefinity.com/sdk/sitefinity-insight-client.min.3.1.44.js604800.0 s11.3 KiB
www.google.com/cse/static/style/look/v6/default.css3000.0 s1.2 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s1.5 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s1.4 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s1.2 KiB
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s1.1 KiB
static.doubleclick.net/instream/ad_status.js900.0 s494 B
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s1021 B
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s770 B
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s602 B
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s556 B
/arcgis/rest/services/basemaps/clearmap_webtopo_nolabel_c...86400.0 s418 B
cdn.matomo.cloud/fao-web.matomo.cloud/matomo.js691200.0 s0 B
i.ytimg.com/vi_webp/C1_-Vjg_TKQ/maxresdefault.webp300.0 s0 B
i.ytimg.com/vi/84xaHTYhBUk/sddefault.jpg7200.0 s0 B
static.doubleclick.net/instream/ad_status.js900.0 s0 B
static.doubleclick.net/instream/ad_status.js900.0 s0 B
static.doubleclick.net/instream/ad_status.js900.0 s0 B

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

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: 621 ms
URLTime Spent
fao.org/257 ms
www.fao.org/home/en364 ms
www.fao.org/home/en0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Highlights Director-General NEWS Strait of Hormuz: Protracted crisis could … body.template-corporate > div > div#Contentplaceholder1_C001_Col00
0.238
NEWS Strait of Hormuz: Protracted crisis could turn into global agrifood catast… body.template-corporate > div > div#Contentplaceholder1_C001_Col00 > div.row
0.008
Conflict in the Near East region adds pressure on fragile agrifood systems, FAO… div.card > div.card-body > h5.card-title > a.title-link
0.003
PREVALENCE OF UNDERNOURISHMENT (PERCENT) (3-YEAR AVERAGE) body.embed-map > div.preloader > main > p.header-title
0.000

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

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.

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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.

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 Evaluation6.0 s
Other1.5 s
Style & Layout384 ms
Script Parsing & Compilation273 ms
Rendering237 ms
Garbage Collection94 ms
Parse HTML & CSS93 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in a sub frame.Actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.7 KiB
URLTransfer SizeEst Savings
/ScriptResource.axd?d=6DQe8ARl7A9TiuWej5ttCsl0UxczkFZDbeL...31.6 KiB5.7 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
Logo Giahs div#map > div.ui-giahs > a > img
www.fao.org/images/homepagelibraries/default-album/logo-giahs.svg
Food and Agriculture Organization of the United Nations div#Contentplaceholder1_T198B1AC4005_Col00 > div.footer-logo > div.sfContentBlock > img
/media/images/corporatenavigationlibraries/default-album/...
icon-bluesky ul.list-inline > li.list-inline-item > a > img
www.fao.org/images/corporatelibraries/social-icons/bluesky.svg?sfvrsn=91618a92_1
icon-facebook ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-faceb...
icon-instagram ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-insta...
icon-linkedin ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-linke...
icon-soundcloud ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-sound...
icon-tiktok ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-tikto...
icon-tuotiao ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-tuoti...
icon-wechat ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-wecha...
icon-weibo ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-weibo...
icon-X ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-twitt...
icon-youtube ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/social-icon-youtu...
icon-whatsapp ul.list-inline > li.list-inline-item > a > img
/images/corporatelibraries/social-icons/whatsapp-icon.svg...

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

Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 23 user timings
Avoid long main-thread tasks 14 long tasks found
Avoid non-composited animations 2 animated elements found
Network Requests
Network Round Trip Times 50 ms
Server Backend Latencies 700 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 50 ms
INP breakdown
80

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
tbody > tr > td.gsc-search-button > button.gsc-search-button tbody > tr > td.gsc-search-button > button.gsc-search-button
div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-in div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-in
div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-out div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-out

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#Contentplaceholder1_C017_Col01 > div.d-list > div.d-list-visual > iframe div#Contentplaceholder1_C017_Col01 > div.d-list > div.d-list-visual > iframe

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEWS div#Contentplaceholder1_C007_Col00 > div.card > div.card-body > h6.title-category
STORY div#Contentplaceholder1_C007_Col01 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C028_Col00 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C028_Col01 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C028_Col02 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C140_Col00 > div.card > div.card-body > h6.title-category
PUBLICATION div#Contentplaceholder1_C140_Col01 > div.card > div.card-body > h6.title-category
INTERACTIVE STORY div#Contentplaceholder1_C140_Col02 > div.card > div.card-body > h6.title-category
FACEBOOK div#Contentplaceholder1_C013_Col00 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C071_Col00 > div.card > div.card-body > h6.title-category
PUBLICATION div#Contentplaceholder1_C071_Col01 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C071_Col02 > div.card > div.card-body > h6.title-category
FOLLOW US ON div#Contentplaceholder1_T198B1AC4005_Col00 > div.footer-social > div.sfContentBlock > h6.title-category

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SOFI 2025 div.row > div.col-lg-6 > p > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Highlights div#Contentplaceholder1_C008_Col00 > div > div.sfContentBlock > h5.sub-title
Mapping undernourishment and food insecurity worldwide div.container > div.row > div.col-lg-6 > h6
IN FOCUS div#Contentplaceholder1_C071_Col00 > div.card > div.card-body > h6.title-category
BLOG widget-popup > div.popup-wrapper > div.pop-body > h6.title-category
FOLLOW US ON div#Contentplaceholder1_T198B1AC4005_Col00 > div.footer-social > div.sfContentBlock > h6.title-category

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Jobs div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Contact us div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Terms and Conditions div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Data protection and privacy div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Report Misconduct div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Transparency and accountability div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Procurement div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

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
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
`[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.
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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Elements with visible text labels have matching accessible names.
`[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 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
`<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
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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.
73

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.fao.org/home/enAllowed
www.fao.org/images/homepagelibraries/default-album/corner-plus.svgAutomatically upgraded to HTTPS

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
www.fao.org/home/en line 2290, col 16
TypeError: utility.setBreadcrumbActiveItemTitle is not a function at HTMLDocument.<anonymous> (https://www.fao.org/home/en:2291:17)

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
Mixed content
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
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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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