Lighthouse Desktop

· 0 checks — Desktop 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
openwrt.org/lib/tpl/bootstrap3/assets/bootstrap/default/bootstrap.min.css	0.0 ms	118.9 KiB
openwrt.org/_media/inbox/toh/openwrt/openwrt_one_top_400.png?w=400&tok=bd5b35	68400.0 s	189.7 KiB
openwrt.github.io/toh/toh.js?v11	600.0 s	4.3 KiB
openwrt.org/_media/logo.png	68400.0 s	5.4 KiB
openwrt.org/lib/images/interwiki.svg	0.0 ms	532 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.

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: OpenWrt One

path: 1,HTML,1,BODY,0,DIV,2,MAIN,1,DIV,3,ARTICLE,3,DIV,0,DIV,5,DIV,1,DIV,3,DIV,0,P,0,A,0,IMG

selector: div.level2 > p > a.media > img.media

snippet: <img src="/_media/inbox/toh/openwrt/openwrt_one_top_400.png?w=400&tok=bd5b35" class="media img-responsive" loading="lazy" alt="OpenWrt One" width="400">

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

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
openwrt.org/lib/exe/css.php?t=bootstrap3&tseed=3267d969d225a35adbb1c1b9275a164e	246.0 KiB	214 ms
openwrt.org/lib/tpl/bootstrap3/css.php?f=bootstrap.css	294 B
openwrt.org/lib/tpl/bootstrap3/assets/bootstrap/default/bootstrap.min.css	118.9 KiB	86 ms

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
OpenWrt One `div.level2 > p > a.media > img.media`	openwrt.org/_media/inbox/toh/openwrt/openwrt_one_top_400.png?w=400&tok=bd5b35	188.8 KiB	170.3 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: 604 ms

URL	Time Spent
openwrt.org/	604 ms
/.within.website/x/cmd/anubis/api/pass-challenge?id=019db...	0.0 ms
openwrt.org/	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
The OpenWrt Community is proud to present the OpenWrt 25.12 stable version seri… `div.page > div.dw-content-page > div.dw-content > div.plugin_include_content`	0.077
	0.021
This website uses cookies. By using the website, you agree with storing cookies… `div.page > div.dw-content-page > div.dw-content > div.cookielaw-banner`	0.004
The OpenWrt Community is proud to present the OpenWrt 25.12 stable version seri… `div.page > div.dw-content-page > div.dw-content > div.plugin_include_content`	0.001
Log In `nav#dw__navbar > div.dw-container > div.collapse > div#dw__navbar_items`	0.000

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: 290 ms 344.9 KiB

URL	Transfer Size	Est Savings
openwrt.org/lib/exe/css.php?t=bootstrap3&tseed=3267d969d225a35adbb1c1b9275a164e	245.5 KiB	239.8 KiB
openwrt.org/lib/tpl/bootstrap3/assets/bootstrap/default/bootstrap.min.css	118.6 KiB	105.1 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: 880 ms 1.1 MiB

URL	Transfer Size	Est Savings
openwrt.org/lib/exe/js.php?t=bootstrap3&tseed=3267d969d225a35adbb1c1b9275a164e	1.2 MiB	869.9 KiB
openwrt.org/lib/exe/jquery.php?tseed=f0349b609f9b91a485af8fd8ecd4aea4	336.8 KiB	258.0 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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
OpenWrt One `div.level2 > p > a.media > img.media`	openwrt.org/_media/inbox/toh/openwrt/openwrt_one_top_400.png?w=400&tok=bd5b35
OpenWrt Wiki `div.dw-container > div.navbar-header > a.navbar-brand > img#dw__logo`	openwrt.org/_media/logo.png

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

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,474 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.3 s

●Avoid long main-thread tasks 1 long task found

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 110 ms

○INP breakdown

○User Timing marks and measures

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

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
This website uses cookies. By using the website, you agree with storing cookies… `div.page > div.dw-content-page > div.dw-content > div.cookielaw-banner`
More information about cookies `div.dw-content-page > div.dw-content > div.cookielaw-banner > a`
by hauke `div.small > span.docInfo > ul.list-inline > li.text-muted`
hauke `span.docInfo > ul.list-inline > li.text-muted > bdi`

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
Table of Hardware `div.dw-content > div.level1 > p > a.wikilink1`
About OpenWrt `div.dw-content > div.level1 > p > a.wikilink1`
More... `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
vulnerabilities get closed shortly after they are discovered `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
More... `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
More... `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
OpenWrt's IRC channels. `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
More... `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
More... `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
help us improve it for others! `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
Developer Guide `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
Register yourself in the wiki `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
IRC channels `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
More information about cookies `div.dw-content-page > div.dw-content > div.cookielaw-banner > a`

These are opportunities to improve the legibility of your content.

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
`div#dw__navbar_items > ul#dw__tools > li.dropdown > a.dropdown-toggle`

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
Download a firmware image for your device (firmware selector) `ul.fix-media-list-overlap > li.level1 > div.li > a.urlextern`
Download a firmware image for your device (Table of Hardware) `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
All firmware images `ul.fix-media-list-overlap > li.level1 > div.li > a.urlextern`
Detailed Changelog `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
Browse Source `ul.fix-media-list-overlap > li.level1 > div.li > a.interwiki`
Download a firmware image for your device (firmware selector) `ul.fix-media-list-overlap > li.level1 > div.li > a.urlextern`
Download a firmware image for your device (Table of Hardware) `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
All firmware images `ul.fix-media-list-overlap > li.level1 > div.li > a.urlextern`
Detailed Changelog `ul.fix-media-list-overlap > li.level1 > div.li > a.wikilink1`
Browse Source `ul.fix-media-list-overlap > li.level1 > div.li > a.urlextern`
1) `div.footnotes > div.fn > sup > a#fn__1`

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-*]` 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

●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

●Document has a `<title>` element

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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

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
openwrt.org/lib/exe/manifest.php	`Manifest: Line: 1, column: 1, Syntax error.`
openwrt.org/lib/exe/manifest.php	`Manifest: Line: 1, column: 1, Syntax error.`

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
openwrt.org/lib/exe/js.php?t=bootstrap3&tseed=3267d969d225a35adbb1c1b9275a164e
/.within.website/x/cmd/anubis/static/js/main.mjs?cacheBus...	openwrt.org/.within.website/x/cmd/anubis/static/js/main.mjs.map

●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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	`<!doctype html><html lang="en"><head><title>Oh noes!</title><link rel="stylesheet" href="/.within.website/x/xess/xess.min.css?cachebuster=1.22.0-20250926"><meta name="viewport" content="width=device-width, initial-scale=1.0"><meta name="robots" content="noindex,nofollow"><style>`	`Syntax not understood`
2	`body,`	`Syntax not understood`
3	`html {`	`Syntax not understood`
4	`height: 100%;`	`Unknown directive`
5	`display: flex;`	`Unknown directive`
6	`justify-content: center;`	`Unknown directive`
7	`align-items: center;`	`Unknown directive`
8	`margin-left: auto;`	`Unknown directive`
9	`margin-right: auto;`	`Unknown directive`
10	`}`	`Syntax not understood`
12	`.centered-div {`	`Syntax not understood`
13	`text-align: center;`	`Unknown directive`
14	`}`	`Syntax not understood`
17	`font-variant-numeric: tabular-nums;`	`Unknown directive`
18	`}`	`Syntax not understood`
21	`display: none;`	`Unknown directive`
22	`width: 90%;`	`Unknown directive`
23	`width: min(20rem, 90%);`	`Unknown directive`
24	`height: 2rem;`	`Unknown directive`
25	`border-radius: 1rem;`	`Unknown directive`
26	`overflow: hidden;`	`Unknown directive`
27	`margin: 1rem 0 2rem;`	`Unknown directive`
28	`outline-offset: 2px;`	`Unknown directive`
29	`outline: #b16286 solid 4px;`	`Unknown directive`
30	`}`	`Syntax not understood`
32	`.bar-inner {`	`Syntax not understood`
33	`background-color: #b16286;`	`Unknown directive`
34	`height: 100%;`	`Unknown directive`
35	`width: 0;`	`Unknown directive`
36	`transition: width 0.25s ease-in;`	`Unknown directive`
37	`}`	`Syntax not understood`
38	`</style><script id="anubis_version" type="application/json">"1.22.0-20250926"`	`Syntax not understood`
39	`</script><script id="anubis_challenge" type="application/json">null`	`Syntax not understood`
40	`</script><script id="anubis_base_prefix" type="application/json">""`	`Syntax not understood`
41	`</script><script id="anubis_public_url" type="application/json">""`	`Syntax not understood`
42	</script></head><body id="top"><main><h1 id="title" class="centered-div">Oh noes!</h1><div class="centered-div"><img id="image" alt="Sad Anubis" style="width:100%;max-width:256px;" src="/.within.website/x/cmd/anubis/static/img/reject.webp?cacheBuster=1.22.0-20250926"><p>Access Denied: error code 4d1dbaddfcc0f385.</p><p><a href="/">Go home</a></p></div><footer><div class="centered-div"><p>Protected by <a href="https://github.com/TecharoHQ/anubis">Anubis</a> From <a href="https://techaro.lol">Techaro</a>. Made with ❤️ in 🇨🇦.</p><p>Mascot design by <a href="https://bsky.app/profile/celphase.bsky.social">CELPHASE</a>.</p><p>This website is running Anubis version <code>1.22.0-20250926</code>.</p></div></footer></main></body></html>	`Unknown directive`

To appear in search results, crawlers need access to your app.

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`