Lighthouse Desktop

· 0 checks — Desktop 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.

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
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2	80 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/webfonts/fa-brands-400.woff2	55 ms

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

value: no origins were preconnected

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
docs.un.org/static/css/style.css	8.1 KiB
fonts.googleapis.com/icon?family=Material+Icons	817 B	284 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css	19.1 KiB	332 ms
cdn.jsdelivr.net/npm/bootstrap@5.3.2/dist/css/bootstrap.min.css	27.2 KiB	242 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
docs.un.org/static/images/logo-en.svg	86400.0 s	9.2 KiB
docs.un.org/static/images/logo-en-reverse.svg	86400.0 s	8.7 KiB
docs.un.org/static/css/style.css	86400.0 s	8.1 KiB

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

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 50 ms 44.1 KiB

URL	Transfer Size	Est Savings
cdn.jsdelivr.net/npm/bootstrap@5.3.2/dist/css/bootstrap.min.css	26.8 KiB	25.9 KiB
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css	18.4 KiB	18.3 KiB

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: 0.0 ms 2.1 KiB

URL	Transfer Size	Est Savings
docs.un.org/static/css/style.css	8.1 KiB	2.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: 0.0 ms 291.9 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-E886RWKZCH	148.0 KiB	105.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-LQCS	138.2 KiB	63.1 KiB
www.googletagmanager.com/gtag/js?id=G-TK9BQL5X7Z&cx=c&gtm=4e64k0	153.6 KiB	61.6 KiB
www.googletagmanager.com/gtag/js?id=G-E886RWKZCH	148.0 KiB	61.4 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
UN logo `div.site-content > div.header-container > a.logo > img`	docs.un.org/static/images/logo-en.svg
United Nations `div.footer-content > div.footer-main > a.footer--unhome > img`	docs.un.org/static/images/logo-en-reverse.svg

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

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: 490 ms

URL	Time Spent
undocs.org/	490 ms
docs.un.org/	0.0 ms

●Time to Interactive 2.2 s

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify JavaScript

●Avoids enormous network payloads Total size was 793 KiB

●User Timing marks and measures 10 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.3 s

●Avoid long main-thread tasks 1 long task found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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.

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
English `nav.navbar > div#languageLinks > div.language-links > a.active-lang`
Donate `div.footer-content > div.footer-main > div.social-donate > a.donate--button`

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-main > div.social-donate > div.social--media > a `div.footer-main > div.social-donate > div.social--media > a`
div.footer-main > div.social-donate > div.social--media > a `div.footer-main > div.social-donate > div.social--media > a`
div.footer-main > div.social-donate > div.social--media > a `div.footer-main > div.social-donate > div.social--media > a`
div.footer-main > div.social-donate > div.social--media > a `div.footer-main > div.social-donate > div.social--media > a`
div.footer-main > div.social-donate > div.social--media > a `div.footer-main > div.social-donate > div.social--media > a`

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.

Best practices

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

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

○Tables have different content in the summary attribute and `<caption>`.

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

○Elements with visible text labels have matching accessible names.

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	`<!-- language_links.ejs -->`	`Syntax not understood`
2	`<!DOCTYPE html>`	`Syntax not understood`
3	`<html lang="en">`	`Syntax not understood`
4	`<head>`	`Syntax not understood`
6	`<!-- Google Tag Manager -->`	`Syntax not understood`
7	`<script>(function(w,d,s,l,i){w[l]=w[l]\|\|[];w[l].push({'gtm.start':`	`Unknown directive`
8	`new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],`	`Unknown directive`
9	`j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=`	`Unknown directive`
10	`'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);`	`Unknown directive`
11	`})(window,document,'script','dataLayer','GTM-LQCS');</script>`	`Syntax not understood`
12	`<!-- End Google Tag Manager -->`	`Syntax not understood`
15	`<meta charset="UTF-8">`	`Syntax not understood`
16	`<meta name="viewport" content="width=device-width, initial-scale=1.0">`	`Syntax not understood`
17	`<link rel="icon" href="/static/images/favicon.ico" type="image/x-icon">`	`Syntax not understood`
18	`<title>Select a language</title>`	`Syntax not understood`
20	`<!-- Bootstrap 5 CSS -->`	`Syntax not understood`
21	`<link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.2/dist/css/bootstrap.min.css" rel="stylesheet"`	`Unknown directive`
22	`integrity="sha384-T3c6CoIi6uLrA9TneNEoa7RxnatzjcDSCmG1MXxSR1GAsXEV/Dwwykc2MPK8M2HN" crossorigin="anonymous">`	`Syntax not understood`
24	`<link type="text/css" rel="stylesheet" href="/static/css/links.css" media="all">`	`Syntax not understood`
25	`</head>`	`Syntax not understood`
26	`<body>`	`Syntax not understood`
28	`<!-- Google Tag Manager (noscript) -->`	`Syntax not understood`
29	`<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-LQCS"`	`Unknown directive`
30	`height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>`	`Unknown directive`
31	`<!-- End Google Tag Manager (noscript) -->`	`Syntax not understood`
34	`<div class="container min-vh-100 d-flex align-items-center justify-content-center">`	`Syntax not understood`
35	`<div class="card shadow-sm border-0 p-4 p-md-5">`	`Syntax not understood`
36	`<div class="text-center mb-4">`	`Syntax not understood`
37	`<img class="img-fluid mb-4 un-logo" src="/static/images/un-logoV2.png" alt="United Nations Logo">`	`Syntax not understood`
39	`</div>`	`Syntax not understood`
41	`<div class="language-buttons">`	`Syntax not understood`
43	`<a class="btn btn-un w-100 mb-3"`	`Syntax not understood`
44	`href="/ar/robots.txt"`	`Syntax not understood`
45	`role="button"`	`Syntax not understood`
46	`lang="ar">`	`Syntax not understood`
47	`العربية`	`Syntax not understood`
48	`</a>`	`Syntax not understood`
50	`<a class="btn btn-un w-100 mb-3"`	`Syntax not understood`
51	`href="/zh/robots.txt"`	`Syntax not understood`
52	`role="button"`	`Syntax not understood`
53	`lang="zh">`	`Syntax not understood`
54	`中文`	`Syntax not understood`
55	`</a>`	`Syntax not understood`
57	`<a class="btn btn-un w-100 mb-3"`	`Syntax not understood`
58	`href="/en/robots.txt"`	`Syntax not understood`
59	`role="button"`	`Syntax not understood`
60	`lang="en">`	`Syntax not understood`
61	`English`	`Syntax not understood`
62	`</a>`	`Syntax not understood`
64	`<a class="btn btn-un w-100 mb-3"`	`Syntax not understood`
65	`href="/fr/robots.txt"`	`Syntax not understood`
66	`role="button"`	`Syntax not understood`
67	`lang="fr">`	`Syntax not understood`
68	`Français`	`Syntax not understood`
69	`</a>`	`Syntax not understood`
71	`<a class="btn btn-un w-100 mb-3"`	`Syntax not understood`
72	`href="/ru/robots.txt"`	`Syntax not understood`
73	`role="button"`	`Syntax not understood`
74	`lang="ru">`	`Syntax not understood`
75	`Русский`	`Syntax not understood`
76	`</a>`	`Syntax not understood`
78	`<a class="btn btn-un w-100 mb-3"`	`Syntax not understood`
79	`href="/es/robots.txt"`	`Syntax not understood`
80	`role="button"`	`Syntax not understood`
81	`lang="es">`	`Syntax not understood`
82	`Español`	`Syntax not understood`
83	`</a>`	`Syntax not understood`
85	`</div>`	`Syntax not understood`
86	`</div>`	`Syntax not understood`
87	`</div>`	`Syntax not understood`
89	`<!-- Bootstrap 5 Bundle with Popper -->`	`Syntax not understood`
90	`<script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.2/dist/js/bootstrap.bundle.min.js"`	`Unknown directive`
91	`integrity="sha384-C6RzsynM9kWDrMNeT87bh95OGNyZPhcTNXj1NW7RuBCsyN/o0jlpcV8Qyq46cDfL"`	`Syntax not understood`
92	`crossorigin="anonymous"></script>`	`Syntax not understood`
94	`<script async src="https://www.googletagmanager.com/gtag/js?id=G-E886RWKZCH"></script>`	`Unknown directive`
95	`<script>`	`Syntax not understood`
96	`window.dataLayer = window.dataLayer \|\| [];`	`Syntax not understood`
97	`function gtag(){dataLayer.push(arguments);}`	`Syntax not understood`
98	`gtag('js', new Date());`	`Syntax not understood`
99	`gtag('config', 'G-E886RWKZCH', {`	`Syntax not understood`
100	`page_path: window.location.pathname,`	`Unknown directive`
101	`page_location: window.location.href`	`Unknown directive`
102	`});`	`Syntax not understood`
103	`</script>`	`Syntax not understood`
105	`</body>`	`Syntax not understood`
106	`</html>`	`Syntax not understood`

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`