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
upload.wikimedia.org/wikipedia/donate/b/b2/Frb-Lisa_Seitz-Gruwell.jpg	0.0 ms	101.2 KiB
/wikipedia/commons/thumb/5/57/Octopus2.jpg/500px-Octopus2...	0.0 ms	66.4 KiB
/w/load.php?lang=en&modules=startup&only=scripts&raw=1&sk...	300.0 s	21.9 KiB
/w/load.php?lang=en&modules=ext.cite.parsoid.styles%7Cext...	300.0 s	21.7 KiB
/wikipedia/commons/thumb/f/f4/Moving_Octopus_Vulgaris_200...	0.0 ms	17.2 KiB
upload.wikimedia.org/wikipedia/donate/b/be/Trustly_logos_only.png	0.0 ms	14.2 KiB
/wikipedia/commons/thumb/1/14/Octopus.ogv/250px--Octopus....	0.0 ms	12.5 KiB
upload.wikimedia.org/wikipedia/donate/1/15/Charity-navigator.png	0.0 ms	8.0 KiB
upload.wikimedia.org/wikipedia/donate/6/6b/Candid-seal-platinum-2025.svg	0.0 ms	5.1 KiB
en.wikipedia.org/w/load.php?lang=en&modules=site.styles&only=styles&skin=minerva	300.0 s	1.7 KiB
/wikipedia/commons/thumb/8/8a/OOjs_UI_icon_edit-ltr.svg/4...	0.0 ms	1.3 KiB

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.

URL	Transfer Size	Duration
/w/load.php?lang=en&modules=ext.cite.parsoid.styles%7Cext...	21.7 KiB	300 ms
en.wikipedia.org/w/load.php?lang=en&modules=site.styles&only=styles&skin=minerva	1.7 KiB

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
Lisa Seitz-Gruwell `div.frb-message > div.frb-image-container > span.frb-image > img`	upload.wikimedia.org/wikipedia/donate/b/b2/Frb-Lisa_Seitz-Gruwell.jpg	100.0 KiB	86.2 KiB
Common octopus on seabed `td > span.mw-default-size > a.mw-file-description > img.mw-file-element`	/wikipedia/commons/thumb/5/57/Octopus2.jpg/500px-Octopus2...	65.2 KiB	57.5 KiB
Charity Navigator Four Star `div.frb-ratings > div.frb-ratings-logos > a.frb-ratings-logo > img`	upload.wikimedia.org/wikipedia/donate/1/15/Charity-navigator.png	6.9 KiB	6.5 KiB

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

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.

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

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: 300 ms 16.5 KiB

URL	Transfer Size	Est Savings
/w/load.php?lang=en&modules=ext.cite.parsoid.styles%7Cext...	20.7 KiB	16.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.

Category	Time Spent
Script Evaluation	866 ms
Other	505 ms
Parse HTML & CSS	359 ms
Style & Layout	332 ms
Script Parsing & Compilation	138 ms
Rendering	88 ms

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

URL	Transfer Size	Est Savings
/w/load.php?lang=en&modules=ext.centralNotice.bannerHisto...	208.0 KiB	77.9 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
Lisa Seitz-Gruwell `div.frb-message > div.frb-image-container > span.frb-image > img`	upload.wikimedia.org/wikipedia/donate/b/b2/Frb-Lisa_Seitz-Gruwell.jpg
Charity Navigator Four Star `div.frb-ratings > div.frb-ratings-logos > a.frb-ratings-logo > img`	upload.wikimedia.org/wikipedia/donate/1/15/Charity-navigator.png
Platinum Transparency 2025 - Candid `div.frb-ratings > div.frb-ratings-logos > a.frb-ratings-logo > img`	upload.wikimedia.org/wikipedia/donate/6/6b/Candid-seal-platinum-2025.svg
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

●Document request latency

●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 743 KiB

●User Timing marks and measures 2 user timings

●JavaScript execution time 0.8 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 20 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 30 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.

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
MAYBE LATER `div.frb > a.frb-mini-link > div.frb-mini-buttons > button.frb-rml-link`
Middle Jurassic `div > span.noprint > span > a`
Pg `span.noprint > div#Timeline-row > div > a`
Scientific classification `tbody > tr > th > a`
Synonyms `tbody > tr > th > a`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Octopus (disambiguation) `div.mw-content-ltr > section#mwAQ > div#mwAw > a.mw-disambig`

These are opportunities to improve the legibility of your content.

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ꞓ `span.noprint > div#Timeline-row > div > a`
O `span.noprint > div#Timeline-row > div > a`
S `span.noprint > div#Timeline-row > div > a`
D `span.noprint > div#Timeline-row > div > a`
C `span.noprint > div#Timeline-row > div > a`
P `span.noprint > div#Timeline-row > div > a`
T `span.noprint > div#Timeline-row > div > a`
J `span.noprint > div#Timeline-row > div > a`
Pg `span.noprint > div#Timeline-row > div > a`
N `span.noprint > div#Timeline-row > div > a`

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Octopus Temporal range: Middle Jurassic – recent PreꞒ Ꞓ O S D C P T J K Pg N … `div#mw-content-text > div.mw-content-ltr > section#mwAQ > table.infobox`

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

●`[accesskey]` values are unique

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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

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

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

●Uses ARIA roles only on compatible elements

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

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

URL	Map URL
/w/load.php?lang=en&modules=ext.centralNotice.bannerHisto...	/w/load.php?lang=en&modules=ext.centralNotice.bannerHisto...
/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...
/w/load.php?lang=en&modules=ext.gadget.switcher&skin=mine...	/w/load.php?lang=en&modules=ext.gadget.switcher&skin=mine...

●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

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`