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.

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
/w/load.php?lang=en&modules=ext.translate.mainpage.icons%...	300.0 s	26.7 KiB
/w/load.php?lang=en&modules=startup&only=scripts&raw=1&sk...	300.0 s	15.2 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...	14400.0 s	11.4 KiB
/wikipedia/commons/thumb/b/be/CodevTT_logo.png/120px-Code...	0.0 ms	4.4 KiB
/wikipedia/commons/thumb/b/b7/Ajapaik_short_logo.png/120p...	0.0 ms	4.1 KiB
upload.wikimedia.org/wikipedia/commons/a/a6/MediaWiki-2020-icon.svg	0.0 ms	2.9 KiB
upload.wikimedia.org/wikipedia/commons/d/da/Adiutor_icon.svg	0.0 ms	1.4 KiB
/w/load.php?lang=en&modules=site.styles&only=styles&skin=...	300.0 s	680 B

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:266.229 label:Time to first byte subpart:timeToFirstByte] map[duration:42.091 label:Resource load delay subpart:resourceLoadDelay] map[duration:81.514 label:Resource load duration subpart:resourceLoadDuration] map[duration:2170.242 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-DIV

nodeLabel: 66 Projects 19k Translators 127k Messages to translate 238 Active languages Ima…

path: 1,HTML,1,BODY,1,DIV,1,MAIN,0,DIV

selector: body.skin--responsive > div.grid > main > div.row

snippet: <div class="row twn-mainpage-banner" style="background-image: url("/w/extensions/TwnMainPage/resources/banners/dance.jp…");">

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-DIV

nodeLabel: 66 Projects 19k Translators 127k Messages to translate 238 Active languages Ima…

path: 1,HTML,1,BODY,1,DIV,1,MAIN,0,DIV

selector: body.skin--responsive > div.grid > main > div.row

snippet: <div class="row twn-mainpage-banner" style="background-image: url("/w/extensions/TwnMainPage/resources/banners/dance.jp…");">

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
/w/load.php?lang=en&modules=ext.translate.mainpage.icons%...	26.7 KiB	87 ms
/w/load.php?lang=en&modules=site.styles&only=styles&skin=...	680 B	127 ms

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
66 Projects 19k Translators 127k Messages to translate 238 Active languages Ima… `body.skin--responsive > div.grid > main > div.row`	translatewiki.net/w/extensions/TwnMainPage/resources/banners/dance.jpg	158.4 KiB	30.4 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: 0.0 ms 114.2 KiB

URL	Transfer Size	Est Savings
.mw-editfont-monospace{font-family:monospace,monospace} …	74.3 KiB	74.0 KiB
/w/load.php?lang=en&modules=ext.translate.mainpage.icons%...	26.4 KiB	23.7 KiB
.oo-ui-draggableElement-handle:not(.oo-ui-draggableElement-undraggable),.oo-ui-draggableElement-han…	17.3 KiB	16.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 138.1 KiB

URL	Transfer Size	Est Savings
/w/load.php?lang=en&modules=ext.checkUser.clientHints%7Ce...	344.1 KiB	138.1 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.1 s

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 656 KiB

●User Timing marks and measures 1 user timing

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.6 s

●Avoid long main-thread tasks 1 long task found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 240 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
English `div.mw-widgets-languageSelectWidget-vue-container > div.cdx-multiselect-lookup > div.cdx-chip-input > div.cdx-chip-input__chips`

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English `div.mw-widgets-languageSelectWidget-vue-container > div.cdx-multiselect-lookup > div.cdx-chip-input > div.cdx-chip-input__chips`

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

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.row > div.four > div#twnmp-stat-projects > a `div.row > div.four > div#twnmp-stat-projects > a`
div.row > div.four > div#twnmp-stat-translators > a `div.row > div.four > div#twnmp-stat-translators > a`
div.row > div.four > div#twnmp-stat-messages > a `div.row > div.four > div#twnmp-stat-messages > a`
div.row > div.four > div#twnmp-stat-languages > a `div.row > div.four > div#twnmp-stat-languages > 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.

○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

●Buttons have an accessible name

●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

●ARIA toggle fields have accessible names

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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 `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.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

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

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

○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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	translatewiki.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	translatewiki.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	translatewiki.net/cdn-cgi/challenge-platform/scripts/jsd/main.js

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	Map URL
/w/load.php?lang=en&modules=ext.checkUser.clientHints%7Ce...	/w/load.php?lang=en&modules=ext.checkUser.clientHints%7Ce...
/w/load.php?lang=en&modules=startup&only=scripts&raw=1&sk...	/w/load.php?lang=en&modules=startup&only=scripts&skin=vec...
/w/load.php?lang=en&modules=ext.visualEditor.core.utils.p...	/w/load.php?lang=en&modules=ext.visualEditor.core.utils.p...
/w/load.php?lang=en&modules=ext.uls.webfonts.repository&s...	/w/load.php?lang=en&modules=ext.uls.webfonts.repository&s...
/w/load.php?lang=en&modules=ext.gadget.HoverPopTools%2Cne...	/w/load.php?lang=en&modules=ext.gadget.HoverPopTools%2Cne...

●Uses HTTPS

●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

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.

○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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes