Skip to content
https://wikiwand.com

Lighthouse Desktop

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

94

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.

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

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.

URLResource SizeEst Savings
Grizzly bear main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Grizzly_bear.jpg59.1 KiB48.2 KiB
Colorado River main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Colorado_River.jpg50.0 KiB43.5 KiB
Jerusalem main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Jerusalem.jpg54.2 KiB42.7 KiB
Rome main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Rome.jpg48.5 KiB39.5 KiB
New York City main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/New_York_City.jpg40.8 KiB34.4 KiB
Moon main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Moon.jpg38.2 KiB26.6 KiB
20th-century Western painting main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/20th-century_Western_painting.jpg33.2 KiB24.2 KiB
Plasma (physics) main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Plasma_(physics).jpg35.1 KiB22.1 KiB
Long Island main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Long_Island.jpg25.9 KiB16.8 KiB
Yangtze main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Yangtze.jpg22.8 KiB13.8 KiB
Barack Obama main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Barack_Obama.jpg21.9 KiB13.1 KiB
Bruce Lee main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Bruce_Lee.jpg21.7 KiB13.0 KiB
Art of Europe main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Art_of_Europe.jpg20.7 KiB12.4 KiB
Elon Musk main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Elon_Musk.jpg15.5 KiB8.2 KiB
David Bowie main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/David_Bowie.jpg14.6 KiB7.0 KiB
Mahatma Gandhi main > article._container_1qls1_1 > a._item_1qls1_14 > img._image_1qls1_100
www.wikiwand.com/featured/Mahatma_Gandhi.jpg14.9 KiB6.1 KiB
Yangtze ARTICLE body > main > article._container_1qls1_1 > a._item_1qls1_14
i.ytimg.com/vi/_mTDxQwLaoM/maxresdefault.jpg154.2 KiB4.2 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.

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

Diagnostics

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

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

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: 253 ms
URLTime Spent
wikiwand.com/253 ms
www.wikiwand.com/0.0 ms
●Time to Interactive 1.3 s
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 50 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 13 user timings
●JavaScript execution time 0.3 s
●Minimizes main-thread work 0.8 s
●Avoid non-composited animations 9 animated elements 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 230 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 long main-thread tasks
○Avoid large layout shifts
88

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
Search Wikiwand section._container_1ndjw_1 > astro-island > div._search_1ndjw_46 > div._content_1ndjw_67
⌘+K section._container_1ndjw_1 > astro-island > div._search_1ndjw_46 > span._badge_1o94u_1
CHROME STORE FEATURED body > main > section._container_1ndjw_1 > a._chromeStoreLink_1ndjw_108
MONTHLY div._container_1q3o8_1 > div._container_8isnv_1 > div._periods_8isnv_11 > div._period_8isnv_11
Wikiwand AI Pro model div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
1,000 monthly AI credits div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
Timelines & Top Qs generation div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
Dozens of themes variations div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
Zero ads. Forever. div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
Unlimited bookmarks div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
☝️ FOR USERS WHO WANT WIKIPEDIA OPTIMIZED div._container_8isnv_1 > div._plans_8isnv_68 > div._plan_8isnv_68 > footer._footer_8isnv_221
All of Pro features div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
Our strongest AI model div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
5,000 monthly AI credits div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
5x more Fact-Checking div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
Access beta features first div._plans_8isnv_68 > div._plan_8isnv_68 > ul._bullets_8isnv_193 > li
🧠 FOR HEAVY READERS, MAXIMIZING AI-POWER div._container_8isnv_1 > div._plans_8isnv_68 > div._plan_8isnv_68 > footer._footer_8isnv_221
COMPANY div._content_1hvza_22 > nav._nav_1hvza_80 > div._linkGroup_1hvza_94 > h3._linkGroupTitle_1hvza_108
PRODUCT div._content_1hvza_22 > nav._nav_1hvza_80 > div._linkGroup_1hvza_94 > h3._linkGroupTitle_1hvza_108
EXTENSIONS div._content_1hvza_22 > nav._nav_1hvza_80 > div._linkGroup_1hvza_94 > h3._linkGroupTitle_1hvza_108
SOCIAL div._content_1hvza_22 > nav._nav_1hvza_80 > div._linkGroup_1hvza_94 > h3._linkGroupTitle_1hvza_108
Sign in div._content_1hvza_22 > div._footer_1hvza_143 > div._metadata_1hvza_154 > a._metadataItem_1hvza_181
Site map div._content_1hvza_22 > div._footer_1hvza_143 > div._metadata_1hvza_154 > a._metadataItem_1hvza_181
Privacy div._content_1hvza_22 > div._footer_1hvza_143 > div._metadata_1hvza_154 > a._metadataItem_1hvza_181
Terms of use div._content_1hvza_22 > div._footer_1hvza_143 > div._metadata_1hvza_154 > a._metadataItem_1hvza_181
© 2026 Wikiwand. All rights reserved. div._content_1hvza_22 > div._footer_1hvza_143 > div._metadata_1hvza_154 > span._metadataItem_1hvza_181

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Elon Musk article._container_1qls1_1 > a._item_1qls1_14 > div._content_1qls1_78 > h3._title_1qls1_127

These are opportunities to improve keyboard navigation in your application.

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
body > header._container_1t28o_1 > a._logo_1t28o_20 body > header._container_1t28o_1 > a._logo_1t28o_20
header._container_1t28o_1 > div._side_1t28o_52 > astro-island > a._avatar_ekz68_1 header._container_1t28o_1 > div._side_1t28o_52 > astro-island > a._avatar_ekz68_1

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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 use only permitted ARIA attributes
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○`<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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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
○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.
81

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 / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
●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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
100

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.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●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`

Send Feedback