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
/wikipedia/commons/f/fb/Wikisource-logo.png?utm_source=wi...	0.0 ms	21.1 KiB
/w/load.php?lang=en&modules=ext.wikimediamessages.styles%...	300.0 s	19.6 KiB
/w/load.php?lang=en&modules=startup&only=scripts&raw=1&sk...	300.0 s	19.4 KiB
/wikipedia/commons/thumb/e/ec/Wiktionary-logo.svg/120px-W...	0.0 ms	16.1 KiB
/wikipedia/commons/thumb/8/80/Wikipedia-logo-v2.svg/120px...	0.0 ms	12.7 KiB
/wikipedia/commons/thumb/d/df/Wikispecies-logo.svg/120px-...	0.0 ms	10.4 KiB
/wikipedia/commons/thumb/a/a6/MediaWiki-2020-icon.svg/120...	0.0 ms	9.3 KiB
/wikipedia/commons/thumb/9/9a/Wikisource_wordmark.svg/500...	0.0 ms	7.8 KiB
/wikipedia/commons/thumb/f/fa/Wikiquote-logo.svg/120px-Wi...	0.0 ms	6.0 KiB
/wikipedia/commons/thumb/7/75/Wikimedia_Community_Logo.sv...	0.0 ms	6.0 KiB
/wikipedia/commons/thumb/f/fa/Wikibooks-logo.svg/120px-Wi...	0.0 ms	5.8 KiB
/wikipedia/commons/thumb/0/0c/Wikifunctions-logo.svg/120p...	0.0 ms	4.4 KiB
/wikipedia/commons/thumb/4/4a/Commons-logo.svg/120px-Comm...	0.0 ms	4.3 KiB
/wikipedia/commons/thumb/8/81/Wikimedia-logo.svg/120px-Wi...	0.0 ms	3.6 KiB
/wikipedia/commons/thumb/5/57/Wikimania.svg/60px-Wikimani...	0.0 ms	3.1 KiB
/wikipedia/commons/thumb/d/dd/Wikivoyage-Logo-v3-icon.svg...	0.0 ms	2.4 KiB
/wikipedia/commons/thumb/0/0b/Wikiversity_logo_2017.svg/1...	0.0 ms	2.3 KiB
/wikipedia/commons/thumb/f/ff/Wikidata-logo.svg/120px-Wik...	0.0 ms	1.4 KiB

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.

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

value: No additional origins are good candidates for preconnecting

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
logo Wikisource `div.central-logo-core > figure.noresize > span > img.mw-file-element`	/wikipedia/commons/f/fb/Wikisource-logo.png?utm_source=wi...	20.0 KiB	19.7 KiB
Logo of Wiktionary `td > span > a > img.mw-file-element`	/wikipedia/commons/thumb/e/ec/Wiktionary-logo.svg/120px-W...	15.0 KiB	14.8 KiB
Logo of Wikipedia `td > span > a > img.mw-file-element`	/wikipedia/commons/thumb/8/80/Wikipedia-logo-v2.svg/120px...	11.5 KiB	9.4 KiB
Logo of Wikispecies `td > span > a > img.mw-file-element`	/wikipedia/commons/thumb/d/df/Wikispecies-logo.svg/120px-...	9.2 KiB	6.5 KiB
Logo of MediaWiki `td > span > a > img.mw-file-element`	/wikipedia/commons/thumb/a/a6/MediaWiki-2020-icon.svg/120...	8.2 KiB	5.9 KiB

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
/w/load.php?lang=en&modules=ext.wikimediamessages.styles%...	19.6 KiB

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

URL	Time Spent
wikisource.org/	764 ms
wikisource.org/wiki/Main_Page	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

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 15.6 KiB

URL	Transfer Size	Est Savings
/w/load.php?lang=en&modules=ext.wikimediamessages.styles%...	18.8 KiB	15.6 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 82.1 KiB

URL	Transfer Size	Est Savings
/w/load.php?lang=en&modules=ext.centralNotice.choiceData%...	181.2 KiB	82.1 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.


div.donate-banner > a.donate-banner__link > picture > img.donate-banner__gif `div.donate-banner > a.donate-banner__link > picture > img.donate-banner__gif`

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

●Time to Interactive 3.1 s

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 411 KiB

●User Timing marks and measures 1 user timing

●JavaScript execution time 0.2 s

●Minimizes main-thread work 1.3 s

●Avoid long main-thread tasks 4 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 60 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

○LCP request discovery

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

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.header-container > div.minerva-header > nav.navigation-drawer > input#main-menu-input `header.header-container > div.minerva-header > nav.navigation-drawer > input#main-menu-input`

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.

Internationalization and localization

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Reo Tahiti `p > span.nowrap > a > span`

These are opportunities to improve the interpretation of your content by users in different locales.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Wiktionary Wikiquote Wikibooks Wikispecies Wikipedia Wikiversity Wikivoy… `section#mf-section-0 > div > div.center > table.plainlinks`

○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

●Buttons have an accessible name

●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

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

●Links are distinguishable without relying on color.

●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

●Touch targets have sufficient size and spacing.

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

○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

○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

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

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

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

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

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 Wikisource `div.central-logo-core > figure.noresize > span > img.mw-file-element`	/wikipedia/commons/f/fb/Wikisource-logo.png?utm_source=wi...	50 x 50 (1.00)	409 x 431 (0.95)

General

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.centralNotice.choiceData%...	/w/load.php?lang=en&modules=ext.centralNotice.choiceData%...
/w/load.php?lang=en&modules=startup&only=scripts&raw=1&sk...	/w/load.php?lang=en&modules=startup&only=scripts&skin=min...
/w/load.php?lang=en&modules=ext.visualEditor.core.utils.p...	/w/load.php?lang=en&modules=ext.visualEditor.core.utils.p...

●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

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`