Skip to content
https://commons.wikimedia.org

Lighthouse Mobile

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

86

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.

RequestCache TTLTransfer Size
/wikipedia/commons/thumb/f/fb/Lupa_Capitolina,_Rome.jpg/1...0.0 ms168.7 KiB
/wikipedia/commons/thumb/8/8b/Tampines_West.Singapore_Sky...0.0 ms29.2 KiB
/w/load.php?lang=en&modules=ext.tmh.player.styles%7Cext.w...300.0 s24.4 KiB
/w/load.php?lang=en&modules=startup&only=scripts&raw=1&sk...300.0 s22.9 KiB
/wikipedia/commons/thumb/3/37/Generic_Camera_Icon.svg/250...0.0 ms20.9 KiB
/wikipedia/commons/thumb/e/ec/Wiktionary-logo.svg/120px-W...0.0 ms16.1 KiB
/wikipedia/commons/thumb/8/80/Wikipedia-logo-v2.svg/120px...0.0 ms12.7 KiB
/wikipedia/commons/thumb/d/df/Wikispecies-logo.svg/120px-...0.0 ms10.4 KiB
/wikipedia/commons/thumb/a/a6/MediaWiki-2020-icon.svg/120...0.0 ms9.3 KiB
/wikipedia/commons/thumb/2/24/Wikinews-logo.svg/120px-Wik...0.0 ms8.5 KiB
/wikipedia/commons/thumb/4/4c/Wikisource-logo.svg/120px-W...0.0 ms6.2 KiB
/wikipedia/commons/thumb/f/fa/Wikiquote-logo.svg/120px-Wi...0.0 ms6.0 KiB
/wikipedia/commons/thumb/7/75/Wikimedia_Community_Logo.sv...0.0 ms6.0 KiB
/wikipedia/commons/thumb/e/e0/Wiki_Loves_Africa_Logo_Vect...0.0 ms5.8 KiB
/wikipedia/commons/thumb/f/fa/Wikibooks-logo.svg/120px-Wi...0.0 ms5.8 KiB
/wikipedia/commons/thumb/0/0d/Get_it_on_F-Droid.svg/250px...0.0 ms5.4 KiB
/wikipedia/commons/thumb/7/78/Google_Play_Store_badge_EN....0.0 ms4.8 KiB
/wikipedia/commons/thumb/0/0c/Wikifunctions-logo.svg/120p...0.0 ms4.4 KiB
/wikipedia/commons/thumb/8/8b/Wikimedia-logo_black.svg/12...0.0 ms2.9 KiB
/wikipedia/commons/thumb/8/8a/Wikivoyage-logo.svg/120px-W...0.0 ms2.4 KiB
/wikipedia/commons/thumb/0/0b/Wikiversity_logo_2017.svg/1...0.0 ms2.3 KiB
/wikipedia/commons/thumb/f/ff/Wikidata-logo.svg/120px-Wik...0.0 ms1.4 KiB
/wikipedia/commons/thumb/f/fd/Magnify-clip_(sans_arrow).s...0.0 ms1.2 KiB
/wikipedia/commons/4/41/MediaWiki_Vector_skin_right_arrow...0.0 ms1.1 KiB
/w/load.php?lang=en&modules=ext.gadget.Long-Image-Names-i...300.0 s1.1 KiB
/w/load.php?lang=en&modules=site.styles&only=styles&skin=...300.0 s1005 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.

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 > span > a.mw-file-description > img.mw-file-element div > span > a.mw-file-description > img.mw-file-element
/wikipedia/commons/thumb/f/fb/Lupa_Capitolina,_Rome.jpg/1...167.5 KiB130.0 KiB
div > span > a > img.mw-file-element div > span > a > img.mw-file-element
/wikipedia/commons/thumb/e/ec/Wiktionary-logo.svg/120px-W...15.0 KiB12.8 KiB
div.mainpage-box-content > figure.mw-halign-right > a > img.mw-file-element div.mainpage-box-content > figure.mw-halign-right > a > img.mw-file-element
/wikipedia/commons/thumb/3/37/Generic_Camera_Icon.svg/250...19.8 KiB11.2 KiB
div > span > a > img.mw-file-element div > span > a > img.mw-file-element
/wikipedia/commons/thumb/8/80/Wikipedia-logo-v2.svg/120px...11.5 KiB9.4 KiB
div > span > a > img.mw-file-element div > span > a > img.mw-file-element
/wikipedia/commons/thumb/d/df/Wikispecies-logo.svg/120px-...9.2 KiB6.5 KiB
div > span > a > img.mw-file-element div > span > a > img.mw-file-element
/wikipedia/commons/thumb/2/24/Wikinews-logo.svg/120px-Wik...7.4 KiB6.1 KiB
div > span > a > img.mw-file-element div > span > a > img.mw-file-element
/wikipedia/commons/thumb/a/a6/MediaWiki-2020-icon.svg/120...8.2 KiB5.9 KiB
span > span > span.mw-tmh-player > video#mwe_player_0_placeholder span > span > span.mw-tmh-player > video#mwe_player_0_placeholder
/wikipedia/commons/thumb/8/8b/Tampines_West.Singapore_Sky...28.0 KiB5.1 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-0-IMG
nodeLabel: div > span > a.mw-file-description > img.mw-file-element
path: 1,HTML,1,BODY,1,DIV,0,DIV,2,MAIN,2,DIV,0,DIV,1,DIV,0,SECTION,1,DIV,1,TABLE,0,TBODY,0,TR,0,TD,0,DIV,1,DIV,0,DIV,0,DIV,0,SPAN,0,A,0,IMG
selector: div > span > a.mw-file-description > img.mw-file-element
snippet: <img src="https://upload.wikimedia.org/wikipedia/commons/thumb/f/fb/Lupa_Capitolina%…" decoding="async" width="500" height="326" class="mw-file-element" srcset="https://upload.wikimedia.org/wikipedia/commons/thumb/f/fb/Lupa_Capitolina%…" data-file-width="7489" data-file-height="4876">

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

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.

URLTransfer SizeDuration
/w/load.php?lang=en&modules=ext.tmh.player.styles%7Cext.w...24.4 KiB302 ms
/w/load.php?lang=en&modules=site.styles&only=styles&skin=...1005 B
/w/load.php?lang=en&modules=ext.gadget.Long-Image-Names-i...1.1 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: 821 ms
URLTime Spent
commons.wikimedia.org/821 ms
commons.wikimedia.org/wiki/Main_Page0.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

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 45.0 KiB
URLTransfer SizeEst Savings
/w/load.php?lang=en&modules=ext.tmh.player.styles%7Cext.w...23.6 KiB20.2 KiB
.mf-icon-clear{ min-width:10px;min-height:10px;width:calc(var(--font-size-medium,1rem) + 4px); … } …13.6 KiB13.3 KiB
.ext-urlshortener-result-dialog{font-size:0.90909em} …11.8 KiB11.5 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 Evaluation713 ms
Other546 ms
Style & Layout488 ms
Script Parsing & Compilation171 ms
Rendering156 ms
Parse HTML & CSS58 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.8 KiB
URLTransfer SizeEst Savings
/w/index.php?title=MediaWiki:Wikiminiatlas.js&action=raw&...10.7 KiB2.8 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 204.8 KiB
URLTransfer SizeEst Savings
/w/load.php?lang=en&modules=ext.campaignEvents.postEdit%7...384.2 KiB183.3 KiB
/w/load.php?lang=en&modules=ext.gadget.AjaxQuickDelete%2C...31.8 KiB21.5 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.

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Avoids enormous network payloads Total size was 908 KiB
●User Timing marks and measures 1 user timing
●JavaScript execution time 0.5 s
●Avoid long main-thread tasks 6 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 70 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 40 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
78

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
By location div.mainpage-box > div#mf-content-links > div.tpl-hidden > div.mw-collapsible-toggle
By type div.mainpage-box > div#mf-content-links > div.tpl-hidden > div.mw-collapsible-toggle
By author div.mainpage-box > div#mf-content-links > div.tpl-hidden > div.mw-collapsible-toggle
By license div.mainpage-box > div#mf-content-links > div.tpl-hidden > div.mw-collapsible-toggle
By source div.mainpage-box > div#mf-content-links > div.tpl-hidden > div.mw-collapsible-toggle

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.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
By topic div.mainpage-box > div#mf-content-links > div.hlist > dl
Images from April 21 td.mainpage-column-right > div.mainpage-box > div#mf-content-links > dl

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > span > a.mw-file-description > img.mw-file-element div > span > a.mw-file-description > img.mw-file-element
div > figure.mw-halign-right > a > img.mw-file-element div > figure.mw-halign-right > a > img.mw-file-element
div.mainpage-box-content > figure.mw-halign-right > a.mw-file-description > img.mw-file-element div.mainpage-box-content > figure.mw-halign-right > a.mw-file-description > img.mw-file-element
div.mainpage-box-content > figure.mw-halign-right > a > img.mw-file-element div.mainpage-box-content > figure.mw-halign-right > a > img.mw-file-element

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

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#mainpage-potd > div > span > a.mw-file-description div#mainpage-potd > div > span > a.mw-file-description
div.mainpage-box > div.mainpage-box-content > figure.mw-halign-right > a.mw-file-description div.mainpage-box > div.mainpage-box-content > figure.mw-halign-right > a.mw-file-description

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
Simple English ul > li > bdi > div.description

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

○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-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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Definition list items are wrapped in `<dl>` elements
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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.
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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.
○`<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.
○Image elements do not have `[alt]` attributes that are redundant text.
○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

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.

URLMap URL
/w/load.php?lang=en&modules=ext.campaignEvents.postEdit%7.../w/load.php?lang=en&modules=ext.campaignEvents.postEdit%7...
/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=jquery.makeCollapsible%7Cjque.../w/load.php?lang=en&modules=jquery.makeCollapsible%7Cjque...
/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.gadget.AjaxQuickDelete%2C.../w/load.php?lang=en&modules=ext.gadget.AjaxQuickDelete%2C...
●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
●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
85

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.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > span > a.mw-file-description > img.mw-file-element div > span > a.mw-file-description > img.mw-file-element
div > figure.mw-halign-right > a > img.mw-file-element div > figure.mw-halign-right > a > img.mw-file-element
div.mainpage-box-content > figure.mw-halign-right > a.mw-file-description > img.mw-file-element div.mainpage-box-content > figure.mw-halign-right > a.mw-file-description > img.mw-file-element
div.mainpage-box-content > figure.mw-halign-right > a > img.mw-file-element div.mainpage-box-content > figure.mw-halign-right > a > img.mw-file-element

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`

Send Feedback