Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

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.

Request	Cache TTL	Transfer Size
assets-jpcust.jwpsrv.com/thumbnails/Q37ADh5O-640.mp4	900.0 s	808.0 KiB
mfe.weforum.org/global-nav/next/s/659.9e80ad8fb1cafceb.js	3600.0 s	383.7 KiB
auth-widgets.weforum.org/widgets/auth/v0.4.59/index.umd.js	3600.0 s	83.5 KiB
auth.lrcontent.com/v2/LoginRadiusV2.js	14400.0 s	56.6 KiB
consent.cookiebot.com/uc.js	575.0 s	35.7 KiB
/dcdn/settings.js?a=593726&settings_type=4&ts=1776790816&...	1800.0 s	14.8 KiB
auth-widgets.weforum.org/widgets/auth/v0.4.59/index.css	3600.0 s	6.5 KiB
www.weforum.org/a-weekly-logo.svg	0.0 ms	3.0 KiB
mfe.weforum.org/global-nav/next/s/remoteEntry.js	3600.0 s	2.5 KiB
fast.fonts.net/cssapi/4946bd2e-8cbd-461c-8121-ca6696f6267d.css	300.0 s	2.0 KiB
mfe.weforum.org/global-nav/next/s/558.490117622e1be7a2.js	3600.0 s	736 B
/t/1.css?apiType=css&projectid=4946bd2e-8cbd-461c-8121-ca...	1.0 s	529 B
/consentconfig/efc82a3f-4d9a-4cba-8bc2-a51619a84a40/wefor...	40358.0 s	833 B
/eu01/v.gif?cd=0&a=593726&d=weforum.org&u=D0BF325DB353034...	43200.0 s	145 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.

URL	Est Savings
www.weforum.org/fonts/Akkurat/AkkuratLLWeb-Bold.woff	50 ms
www.weforum.org/fonts/Akkurat/AkkuratLLWeb-Regular.woff2	45 ms
www.weforum.org/fonts/Akkurat/AkkuratLLWeb-Black.woff2	40 ms

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:154.968 source:map[type:text value:[unattributed]]]]

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.

	URL	Resource Size	Est Savings
div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85 `div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85`	/community/image/responsive_large_webp_cUJKdAiLYJCmwVVq6c...	517.6 KiB	471.8 KiB
div.wef-17csfx1 > div.chakra-aspect-ratio > picture > img.chakra-image `div.wef-17csfx1 > div.chakra-aspect-ratio > picture > img.chakra-image`	/article/image/responsive_large_webp_NJlniFQxYj1f2f_FvgcI...	130.8 KiB	125.1 KiB
div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h `div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h`	/article/image/responsive_large_webp_-mQp0euW6dX20vlf02Wf...	131.6 KiB	83.6 KiB
div.wef-17csfx1 > div.chakra-aspect-ratio > picture > img.chakra-image `div.wef-17csfx1 > div.chakra-aspect-ratio > picture > img.chakra-image`	/article/image/responsive_large_webp_VjSTDbT_7HaZNnzIGqnR...	128.2 KiB	81.0 KiB
div.wef-1gnrjno > div.wef-1srmzni > div.wef-tqumyf > img.wef-1o9b4je `div.wef-1gnrjno > div.wef-1srmzni > div.wef-tqumyf > img.wef-1o9b4je`	www.weforum.org/packs/static/si-initiative-45d9653189ca943b0dc7.jpeg	77.6 KiB	76.2 KiB
div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85 `div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85`	/community/image/responsive_large_webp_c-zmSV2oX0cY0JSuSV...	89.2 KiB	53.1 KiB
div.wef-17csfx1 > div.chakra-aspect-ratio > picture > img.chakra-image `div.wef-17csfx1 > div.chakra-aspect-ratio > picture > img.chakra-image`	/article/image/responsive_large_webp_Lucr6ErMpqY8LhUZSJ6w...	57.1 KiB	51.6 KiB
div.wef-1th3fel > div.wef-1tr4eyi > picture > img.wef-19qvy6h `div.wef-1th3fel > div.wef-1tr4eyi > picture > img.wef-19qvy6h`	/collection/image/responsive_large_webp_bFActzUmXclYQ0kZA...	96.1 KiB	49.2 KiB
div.wef-17csfx1 > div.chakra-aspect-ratio > picture > img.chakra-image `div.wef-17csfx1 > div.chakra-aspect-ratio > picture > img.chakra-image`	/article/image/responsive_large_webp_DEezBJLIGJXjJRdXmc4g...	89.3 KiB	41.3 KiB
div.wef-1gnrjno > div.wef-1kvj0y4 > div.wef-1xt3ztg > img.wef-19ja7d2 `div.wef-1gnrjno > div.wef-1kvj0y4 > div.wef-1xt3ztg > img.wef-19ja7d2`	www.weforum.org/packs/static/uplink-initiative-ceff9cfdd2e858ac3307.jpeg	77.0 KiB	40.5 KiB
div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h `div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h`	/article/image/responsive_large_webp_tbNYUgJXPjBjxcCmXCpK...	59.3 KiB	26.6 KiB
div.wef-17csfx1 > div.chakra-aspect-ratio > picture > img.chakra-image `div.wef-17csfx1 > div.chakra-aspect-ratio > picture > img.chakra-image`	/article/image/responsive_large_webp_7M087Z2Q3z4QVYGknxw1...	21.9 KiB	17.6 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-12-VIDEO

nodeLabel: div.wef-1l63pvi > div.wef-1wmycnq > div.chakra-aspect-ratio > video.wef-0

path: 1,HTML,1,BODY,6,DIV,0,DIV,3,SECTION,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,VIDEO

selector: div.wef-1l63pvi > div.wef-1wmycnq > div.chakra-aspect-ratio > video.wef-0

snippet: <video autoplay="" muted="" playsinline="" loop="" src="https://cdn.jwplayer.com/v2/media/CsSwjh6M/poster.mp4?width=640" class="wef-0">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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.

URL	Transfer Size	Duration
/assets/swiper/swiper-d58521792df503d8ccc5c75a7afee37ce94...	1.5 KiB
/t/1.css?apiType=css&projectid=4946bd2e-8cbd-461c-8121-ca...	529 B	153 ms

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: 1.2 s

URL	Time Spent
weforum.org/	1.2 s
www.weforum.org/	0.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

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.

Estimated savings: 300 ms 49.8 KiB

URL	Transfer Size	Est Savings
/assets/application-a5591b3e426bc96757bdb09968aed043b2dd2...	110.4 KiB	49.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 600 ms 220.9 KiB

URL	Transfer Size	Est Savings
/assets/application-a5591b3e426bc96757bdb09968aed043b2dd2...	110.2 KiB	109.2 KiB
@keyframes _ngcontent-ng-c776726875_fadeIn{0%{opacity:.6} …	28.9 KiB	28.9 KiB
@keyframes _ngcontent-ng-c3556001274_fadeIn{0%{opacity:.6} …	17.9 KiB	17.9 KiB
@charset "UTF-8";@keyframes _ngcontent-ng-c3727337105_fadeIn{0%{opacity:.6} …	23.6 KiB	16.8 KiB
@keyframes _ngcontent-ng-c2342676998_fadeIn{0%{opacity:.6} …	15.2 KiB	15.2 KiB
	13.5 KiB	12.0 KiB
:host,:root,[data-theme]{--chakra-ring-inset:var(--chakra-empty,/!/ /!/);--chakra-ring-offset-w…	10.8 KiB	10.8 KiB
@keyframes _ngcontent-ng-c4052917526_fadeIn{0%{opacity:.6} …	16.0 KiB	10.1 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: 3.3 s 1.4 MiB

URL	Transfer Size	Est Savings
www.weforum.org/packs/js/app-bundle-6fe0ba159cfc1b34391f.js	438.2 KiB	201.9 KiB
www.weforum.org/packs/js/922-352a71d0e9788b160e3c.js	225.3 KiB	130.7 KiB
www.googletagmanager.com/gtag/js?id=G-4DKG1LX6QK&cx=c&gtm=4e64h1	175.9 KiB	114.4 KiB
mfe.weforum.org/global-nav/next/s/659.9e80ad8fb1cafceb.js	383.3 KiB	114.3 KiB
www.googletagmanager.com/gtag/js?id=G-1RV0X04XBG&cx=c&gtm=4e64h1	173.2 KiB	72.2 KiB
www.googletagmanager.com/gtag/js?id=G-2K5FR2KRN5&cx=c&gtm=4e64h1	171.8 KiB	68.7 KiB
www.weforum.org/packs/js/93-c19c8d49cbcf5dd9c444.js	82.9 KiB	67.6 KiB
www.googletagmanager.com/gtag/js?id=AW-10828833886&cx=c&gtm=4e64h1	176.0 KiB	64.3 KiB
www.googletagmanager.com/gtag/js?id=AW-16759232739&cx=c&gtm=4e64h1	145.6 KiB	64.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-W7SZB6C	175.1 KiB	63.7 KiB
www.googletagmanager.com/gtag/js?id=DC-13894911&cx=c&gtm=4e64h1	129.4 KiB	62.7 KiB
www.googletagmanager.com/gtag/js?id=AW-17334477208&cx=c&gtm=4e64h1	140.5 KiB	62.6 KiB
/cdn/edrv/va_gq-d728c477f0f4777c8be7f1f120d0c70b.br.js	96.5 KiB	61.4 KiB
www.weforum.org/packs/js/10-ac3f1aff0b8dfb42dbcd.js	77.4 KiB	50.4 KiB
www.weforum.org/packs/js/191-fbde39dcd171b6dc553a.js	63.7 KiB	50.2 KiB
auth.lrcontent.com/v2/LoginRadiusV2.js	56.2 KiB	49.9 KiB
auth-widgets.weforum.org/widgets/auth/v0.4.59/index.umd.js	80.5 KiB	45.8 KiB
/cdn/analysis/4.0/opaEv-1c7ce826a687aa150a0d779609032360b...	44.1 KiB	36.6 KiB
www.weforum.org/packs/js/application-6d79c5b7767f47dedde6.js	28.2 KiB	25.7 KiB
www.weforum.org/packs/js/40-ab65ef154c6c4cf00aed.js	49.9 KiB	25.2 KiB
/efc82a3f-4d9a-4cba-8bc2-a51619a84a40/cc.js?renew=false&r...	120.6 KiB	24.8 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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.weforum.org/packs/js/245-1cbfbba9c93ec6fde9b7.js	2.5 s	2.1 s	16 ms
www.weforum.org/	2.1 s	42 ms	23 ms
/efc82a3f-4d9a-4cba-8bc2-a51619a84a40/cc.js?renew=false&r...	1.1 s	472 ms	43 ms
mfe.weforum.org/global-nav/next/s/659.9e80ad8fb1cafceb.js	1.1 s	671 ms	215 ms
www.googletagmanager.com/gtm.js?id=GTM-W7SZB6C	868 ms	608 ms	129 ms
www.weforum.org/packs/js/app-bundle-6fe0ba159cfc1b34391f.js	854 ms	619 ms	160 ms
/cdn/edrv/va_gq-d728c477f0f4777c8be7f1f120d0c70b.br.js	843 ms	674 ms	81 ms
mfe.weforum.org/global-nav/next/s/558.490117622e1be7a2.js	746 ms	679 ms	0.5 ms
www.googletagmanager.com/gtag/js?id=G-1RV0X04XBG&cx=c&gtm=4e64h1	742 ms	691 ms	42 ms
Unattributable	736 ms	44 ms	0.0 ms
www.weforum.org/packs/js/922-352a71d0e9788b160e3c.js	700 ms	40 ms	67 ms
www.googletagmanager.com/gtag/js?id=AW-10828833886&cx=c&gtm=4e64h1	534 ms	342 ms	69 ms
www.weforum.org/packs/js/application-6d79c5b7767f47dedde6.js	364 ms	310 ms	13 ms
consent.cookiebot.com/uc.js	271 ms	246 ms	11 ms
www.googletagmanager.com/gtag/js?id=G-2K5FR2KRN5&cx=c&gtm=4e64h1	265 ms	215 ms	48 ms
www.googletagmanager.com/gtag/js?id=AW-16759232739&cx=c&gtm=4e64h1	210 ms	168 ms	41 ms
www.googletagmanager.com/gtag/js?id=AW-17334477208&cx=c&gtm=4e64h1	191 ms	154 ms	36 ms
www.googletagmanager.com/gtag/js?id=DC-13894911&cx=c&gtm=4e64h1	158 ms	125 ms	31 ms
www.googletagmanager.com/gtag/js?id=G-4DKG1LX6QK&cx=c&gtm=4e64h1	87 ms	32 ms	55 ms
auth-widgets.weforum.org/widgets/auth/v0.4.59/index.umd.js	85 ms	55 ms	30 ms
/assets/application-a5591b3e426bc96757bdb09968aed043b2dd2...	71 ms	0.0 ms	0.0 ms
/j.php?a=593726&u=https%3A%2F%2Fwww.weforum.org%2F&f=1&r=...	71 ms	58 ms	8.6 ms
/cdn/analysis/4.0/opaEv-1c7ce826a687aa150a0d779609032360b...	60 ms	37 ms	16 ms
/cdn/edrv/nc-367e6623b8f828e1b7169e212977ec69.br.js	60 ms	28 ms	31 ms
www.weforum.org/packs/js/10-ac3f1aff0b8dfb42dbcd.js	51 ms	25 ms	25 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.

Category	Time Spent
Script Evaluation	8.6 s
Style & Layout	2.1 s
Other	1.7 s
Script Parsing & Compilation	1.4 s
Parse HTML & CSS	790 ms
Garbage Collection	284 ms
Rendering	255 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.

URL	Transfer Size
assets-jpcust.jwpsrv.com/thumbnails/Q37ADh5O-640.mp4	808.0 KiB
/community/image/responsive_large_webp_cUJKdAiLYJCmwVVq6c...	518.2 KiB
www.weforum.org/packs/js/app-bundle-6fe0ba159cfc1b34391f.js	438.3 KiB
mfe.weforum.org/global-nav/next/s/659.9e80ad8fb1cafceb.js	383.7 KiB
www.weforum.org/packs/js/922-352a71d0e9788b160e3c.js	225.4 KiB
www.googletagmanager.com/gtag/js?id=AW-10828833886&cx=c&gtm=4e64h1	176.0 KiB
www.googletagmanager.com/gtag/js?id=G-4DKG1LX6QK&cx=c&gtm=4e64h1	175.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-W7SZB6C	175.5 KiB
www.googletagmanager.com/gtag/js?id=G-1RV0X04XBG&cx=c&gtm=4e64h1	173.2 KiB
www.googletagmanager.com/gtag/js?id=G-2K5FR2KRN5&cx=c&gtm=4e64h1	171.8 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
World Economic Forum logo `div.wef-16gxeys > div.wef-0 > div.wef-ydr723 > img.chakra-image`	www.weforum.org/a-weekly-logo.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

●Minify JavaScript

●User Timing marks and measures 54 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 140 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 30 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sign in `div#global-nav_root > div#global-nav_display > navbar > div#navbar_container`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
div.wef-1l63pvi > div.wef-1wmycnq > div.wef-1l9nceh > button.chakra-button `div.wef-1l63pvi > div.wef-1wmycnq > div.wef-1l9nceh > button.chakra-button`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Join us `div#navbar_right-panel > public-bar-panel > div#public_right-panel_container > a.public-bar-panel__link`
article.wef-ahbhn4 > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link `article.wef-ahbhn4 > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link`
article.wef-ahbhn4 > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link `article.wef-ahbhn4 > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link`
div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link `div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link`
div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link `div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link`
div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link `div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link`
article.wef-lv2neg > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link `article.wef-lv2neg > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link`
article.wef-lv2neg > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link `article.wef-lv2neg > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link`

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.

○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]`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

●`[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

●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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[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 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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
logo `div#CybotCookiebotDialogHeader > div#CybotCookiebotDialogHeaderLogosWrapper > div#CybotCookiebotDialogPoweredbyLink > img#CybotCookiebotDialogPoweredbyImage`		46 x 34 (1.35)	46 x 46 (1.00)

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.

Source	Description
mfe.weforum.org/global-nav/next/s/659.9e80ad8fb1cafceb.js	`Uncaught TypeError: Cannot set properties of null (setting 'lastSetTimerId')`

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

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.weforum.org/packs/js/app-bundle-6fe0ba159cfc1b34391f.js
www.weforum.org/packs/js/922-352a71d0e9788b160e3c.js
mfe.weforum.org/global-nav/next/s/659.9e80ad8fb1cafceb.js

●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

●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

100

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.

○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 have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`