https://stationery.wiki/Stationery_Wiki:Mechanical_Pencil_Day_Contest

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
stationery.wiki/resources/assets/wiki-norispollux.jpg?8f2c8	0.0 ms	19.5 KiB
/load.php?lang=en-gb&modules=skins.vector.icons%2Cstyles%...	300.0 s	19.6 KiB
stationery.wiki/resources/assets/poweredby_mediawiki.svg	0.0 ms	14.4 KiB
/load.php?lang=en-gb&modules=startup&only=scripts&raw=1&s...	300.0 s	11.6 KiB
stationery.wiki/extensions/SemanticMediaWiki/res/smw/assets/logo_footer.svg	0.0 ms	7.1 KiB
/wikipedia/commons/thumb/e/e2/Flag_of_the_United_States_(...	0.0 ms	2.7 KiB
/wikipedia/commons/thumb/3/3e/Flag_of_New_Zealand.svg/lan...	0.0 ms	2.5 KiB
/wikipedia/commons/thumb/7/73/Flag_of_Romania.svg/langen-...	0.0 ms	2.1 KiB
/wikipedia/commons/thumb/0/03/Flag_of_Italy.svg/langen-gb...	0.0 ms	2.1 KiB
stationery.wiki/resources/assets/licenses/cc-by-sa.png	0.0 ms	1.5 KiB
/skins/Vector/resources/skins.vector.styles/images/link-e...	0.0 ms	451 B

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
/load.php?lang=en-gb&modules=skins.vector.icons%2Cstyles%...	19.6 KiB	306 ms

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

Why this matters

Performance issues directly impact user engagement and conversion rates.


head > meta `head > meta`

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

Diagnostics

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
Rendering	624 ms
Other	587 ms
Script Evaluation	483 ms
Style & Layout	360 ms
Script Parsing & Compilation	85 ms
Parse HTML & CSS	43 ms

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.3 KiB

URL	Transfer Size	Est Savings
/load.php?lang=en-gb&modules=skins.vector.icons%2Cstyles%...	19.3 KiB	15.3 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 107.1 KiB

URL	Transfer Size	Est Savings
/load.php?lang=en-gb&modules=skins.vector.search.codex.sc...	67.5 KiB	55.9 KiB
/load.php?lang=en-gb&modules=ext.jquery.async%7Cext.smw%7...	109.0 KiB	51.2 KiB

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

●Time to Interactive 3.1 s

●Max Potential First Input Delay 100 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 304 KiB

●User Timing marks and measures 1 user timing

●JavaScript execution time 0.3 s

●Avoid long main-thread tasks 4 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 720 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 320 ms

●Avoid large layout shifts 3 layout shifts 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.

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
(Redirected from Stationery Wiki:Mechanical Pencil Day Contest) The Mechanical… `div.mw-page-container-inner > div.mw-content-container > main#content > div#bodyContent`
main#content > div#bodyContent > div.vector-body-before-content > div.mw-indicators `main#content > div#bodyContent > div.vector-body-before-content > div.mw-indicators`

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

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
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`

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
tr > td > span > a.mw-file-description `tr > td > span > a.mw-file-description`
tr > td > span > a.mw-file-description `tr > td > span > a.mw-file-description`
tr > td > span > a.mw-file-description `tr > td > span > a.mw-file-description`
tr > td > span > a.mw-file-description `tr > td > span > a.mw-file-description`
tr > td > span > a.mw-file-description `tr > td > span > a.mw-file-description`
tr > td > span > a.mw-file-description `tr > td > span > 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.

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
Dish `div.mw-content-ltr > ol > li > a`
Rares `div.mw-content-ltr > ol > li > a.mw-redirect`

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

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

●`[accesskey]` values are unique

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

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

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

●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

●Skip links are focusable.

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

●`<td>` elements in a large `<table>` have one or more table headers.

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

○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

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
stationery.wiki/Favicon.ico	`Failed to load resource: the server responded with a status of 404 ()`
stationery.wiki/Favicon.ico	`Failed to load resource: the server responded with a status of 404 ()`

●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 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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > 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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid