Skip to content
https://weforum.org

Lighthouse Desktop

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

Detailed Report

Audit breakdown by category with detailed findings.

42

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:8.398 source:map[column:168385 line:2 type:source-location url:https://www.weforum.org/packs/js/245-1cbfbba9c93ec6fde9b7.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:156.987 source:map[type:text value:[unattributed]]] map[reflowTime:7.034 source:map[column:257731 line:280 type:source-location url:https://www.weforum.org/packs/js/922-352a71d0e9788b160e3c.js urlProvider:network]] map[reflowTime:0.45 source:map[column:252095 line:280 type:source-location url:https://www.weforum.org/packs/js/922-352a71d0e9788b160e3c.js urlProvider:network]] map[reflowTime:0.914 source:map[column:258247 line:280 type:source-location url:https://www.weforum.org/packs/js/922-352a71d0e9788b160e3c.js urlProvider:network]] map[reflowTime:3.691 source:map[column:208856 line:1 type:source-location url:https://consent.cookiebot.com/efc82a3f-4d9a-4cba-8bc2-a51619a84a40/cc.js?renew=false&referer=www.weforum.org&dnt=false&init=false&culture=EN urlProvider:network]] map[reflowTime:5.27 source:map[column:219190 line:1 type:source-location url:https://consent.cookiebot.com/efc82a3f-4d9a-4cba-8bc2-a51619a84a40/cc.js?renew=false&referer=www.weforum.org&dnt=false&init=false&culture=EN urlProvider:network]] map[reflowTime:1.011 source:map[column:111659 line:1 type:source-location url:https://consent.cookiebot.com/efc82a3f-4d9a-4cba-8bc2-a51619a84a40/cc.js?renew=false&referer=www.weforum.org&dnt=false&init=false&culture=EN urlProvider:network]] map[reflowTime:0.567 source:map[column:113197 line:1 type:source-location url:https://consent.cookiebot.com/efc82a3f-4d9a-4cba-8bc2-a51619a84a40/cc.js?renew=false&referer=www.weforum.org&dnt=false&init=false&culture=EN 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.swiper-slide > a.chakra-link > picture > img.wef-n9lm85 div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85
/community/image/responsive_big_webp_cUJKdAiLYJCmwVVq6c8g...517.6 KiB495.4 KiB
div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h
/article/image/responsive_big_webp_-mQp0euW6dX20vlf02Wf17...416.7 KiB406.3 KiB
div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h
/article/image/responsive_big_webp_xCsNhvQ5iCKk46q-rMylnr...353.4 KiB343.0 KiB
div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h
/article/image/responsive_big_webp_tbNYUgJXPjBjxcCmXCpKZV...271.0 KiB260.6 KiB
div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85 div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85
/community/image/responsive_big_webp_c-zmSV2oX0cY0JSuSVZy...276.9 KiB251.9 KiB
div.wef-1th3fel > div.wef-1tr4eyi > picture > img.wef-19qvy6h div.wef-1th3fel > div.wef-1tr4eyi > picture > img.wef-19qvy6h
/collection/image/responsive_big_webp_bFActzUmXclYQ0kZAE8...365.4 KiB231.9 KiB
div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h div.swiper-slide > div.wef-1uij82s > picture > img.wef-eoet0h
/article/image/responsive_big_webp_52KRawdMoxGf0J_e5GLYkz...186.8 KiB179.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_big_webp_9J5cA9o51Xtg2cuKMBYQyD...158.2 KiB150.9 KiB
div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85 div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85
/community/image/responsive_big_webp_QcmU5WNU7nZuim7g_Bcd...155.7 KiB130.7 KiB
div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85 div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85
/community/image/responsive_big_webp_Lcpy2J6K0R-yVXXMSpKk...114.3 KiB94.6 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.jpeg52.7 KiB41.4 KiB
div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85 div.swiper-slide > a.chakra-link > picture > img.wef-n9lm85
/community/image/responsive_big_webp_UlNB7uu_8IUV0VWb1wHj...38.8 KiB32.1 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.jpeg29.3 KiB29.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_small_webp_NJlniFQxYj1f2f_FvgcI...32.6 KiB21.4 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_small_webp_JJm9_VnK9kcvd3pv8HIQ...29.6 KiB18.4 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_small_webp_VjSTDbT_7HaZNnzIGqnR...26.8 KiB15.5 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_small_webp_Lucr6ErMpqY8LhUZSJ6w...20.1 KiB8.9 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_small_webp_DEezBJLIGJXjJRdXmc4g...18.5 KiB7.3 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-18-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.

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

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: 633 ms
URLTime Spent
weforum.org/633 ms
www.weforum.org/0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 160 ms 49.8 KiB
URLTransfer SizeEst Savings
/assets/application-a5591b3e426bc96757bdb09968aed043b2dd2...110.4 KiB49.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.

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: 600 ms 1.4 MiB
URLTransfer SizeEst Savings
www.weforum.org/packs/js/app-bundle-6fe0ba159cfc1b34391f.js438.2 KiB201.9 KiB
www.weforum.org/packs/js/922-352a71d0e9788b160e3c.js225.3 KiB129.1 KiB
mfe.weforum.org/global-nav/next/s/659.9e80ad8fb1cafceb.js383.3 KiB114.6 KiB
www.googletagmanager.com/gtag/js?id=AW-10828833886&cx=c&gtm=4e64h1176.0 KiB114.5 KiB
www.googletagmanager.com/gtag/js?id=G-1RV0X04XBG&cx=c&gtm=4e64h1173.2 KiB72.5 KiB
www.googletagmanager.com/gtag/js?id=G-2K5FR2KRN5&cx=c&gtm=4e64h1171.8 KiB68.6 KiB
www.weforum.org/packs/js/93-c19c8d49cbcf5dd9c444.js82.9 KiB67.6 KiB
www.googletagmanager.com/gtag/js?id=G-4DKG1LX6QK&cx=c&gtm=4e64h1175.9 KiB64.2 KiB
www.googletagmanager.com/gtag/js?id=AW-16759232739&cx=c&gtm=4e64h1145.6 KiB63.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-W7SZB6C175.1 KiB63.7 KiB
www.googletagmanager.com/gtag/js?id=AW-17334477208&cx=c&gtm=4e64h1140.5 KiB63.5 KiB
www.googletagmanager.com/gtag/js?id=DC-13894911&cx=c&gtm=4e64h1129.4 KiB62.7 KiB
/cdn/edrv/va_gq-d728c477f0f4777c8be7f1f120d0c70b.br.js96.5 KiB60.5 KiB
www.weforum.org/packs/js/10-ac3f1aff0b8dfb42dbcd.js77.4 KiB50.4 KiB
www.weforum.org/packs/js/191-fbde39dcd171b6dc553a.js63.7 KiB50.2 KiB
auth.lrcontent.com/v2/LoginRadiusV2.js56.2 KiB49.9 KiB
auth-widgets.weforum.org/widgets/auth/v0.4.59/index.umd.js80.5 KiB45.8 KiB
/cdn/analysis/4.0/opaEv-1c7ce826a687aa150a0d779609032360b...44.1 KiB36.6 KiB
www.weforum.org/packs/js/application-6d79c5b7767f47dedde6.js28.2 KiB25.8 KiB
www.weforum.org/packs/js/40-ab65ef154c6c4cf00aed.js49.9 KiB25.2 KiB
/efc82a3f-4d9a-4cba-8bc2-a51619a84a40/cc.js?renew=false&r...120.6 KiB24.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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.3 s
Style & Layout546 ms
Other466 ms
Script Parsing & Compilation326 ms
Parse HTML & CSS219 ms
Garbage Collection74 ms
Rendering72 ms

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 14 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 140 ms
●Server Backend Latencies 90 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
87

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
Join us 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
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
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
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-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.
88

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.

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

SourceDescription
TypeError: Cannot set properties of null (setting 'lastSetTimerId') at https://dev.visualwebsiteoptimizer.com/cdn/edrv/va_gq-d728c477f0f4777c8be7f1f120d0c70b.br.js:2:288820 at B.e.___hb.e.___hb (https://www.weforum.org/packs/js/245-1cbfbba9c93ec6fde9b7.js:2:14315) at https://www.weforum.org/packs/js/245-1cbfbba9c93ec6fde9b7.js:2:19130

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.

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

Send Feedback