Skip to content
https://www.archlinux.org

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.

98

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.

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

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
Icons8 logo div#content-right > div.widget > a > img
archlinux.org/static/icons8_logo.png10.2 KiB7.4 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

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
Icons8 logo div#content-right > div.widget > a > img
archlinux.org/static/icons8_logo.png
Hetzner logo div#content-right > div.widget > a > img
archlinux.org/static/hetzner_logo.png
Donate via Click&Pledge to Arch Linux div#content-right > div#home-donate-button > a > img
archlinux.org/static/click_and_pledge.png
RSS Feed div#content-left > div#news > a.rss-icon > img
archlinux.org/static/rss.svg
RSS Feed div#content-right > div#pkg-updates > a.rss-icon > img
archlinux.org/static/rss.svg

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: 583 ms
URLTime Spent
www.archlinux.org/583 ms
archlinux.org/0.0 ms
Use efficient cache lifetimes
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Time to Interactive 0.9 s
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 47 KiB
Minimizes main-thread work 0.1 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 120 ms
Server Backend Latencies 60 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 60 ms
INP breakdown
LCP request discovery
User Timing marks and measures
JavaScript execution time
Avoid long main-thread tasks
Avoid non-composited animations
Avoid large layout shifts
86

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
Packages div#archnavbarmenu > ul#archnavbarlist > li#anb-packages > a
Forums div#archnavbarmenu > ul#archnavbarlist > li#anb-forums > a
Wiki div#archnavbarmenu > ul#archnavbarlist > li#anb-wiki > a
GitLab div#archnavbarmenu > ul#archnavbarlist > li#anb-gitlab > a
Security div#archnavbarmenu > ul#archnavbarlist > li#anb-security > a
AUR div#archnavbarmenu > ul#archnavbarlist > li#anb-aur > a
Download div#archnavbarmenu > ul#archnavbarlist > li#anb-download > a
community-operated package repository div#content-left > div#intro > p > a
forums div#content-left > div#intro > p > a
mailing lists div#content-left > div#intro > p > a
wiki div#content-left > div#intro > p > a
Learn more... div#content-left > div#intro > p.readmore > a
Latest News div#content-left > div#news > h3 > a
kea >= 1:3.0.3-6 update requires manual intervention div#content-left > div#news > h4 > a
iptables now defaults to the nft backend div#content-left > div#news > h4 > a
NVIDIA 590 driver drops Pascal and lower support; main packages switch to Open … div#content-left > div#news > h4 > a
.NET packages may require manual intervention div#content-left > div#news > h4 > a
waydroid >= 1.5.4-3 update may require manual intervention div#content-left > div#news > h4 > a
Older News div#content-left > div#news > h3 > a
dovecot >= 2.4 requires manual intervention div#news > dl.newslist > dd > a
Recent service outages div#news > dl.newslist > dd > a
zabbix >= 7.4.1-2 may require manual intervention div#news > dl.newslist > dd > a
linux-firmware >= 20250613.12fe085f-5 upgrade requires manual intervention div#news > dl.newslist > dd > a
Plasma 6.4.0 will need manual intervention if you are on X11 div#news > dl.newslist > dd > a
Transition to the new WoW64 wine and wine-staging div#news > dl.newslist > dd > a
Valkey to replace Redis in the [extra] Repository div#news > dl.newslist > dd > a
Cleaning up old repositories div#news > dl.newslist > dd > a
Glibc 2.41 corrupting Discord installation div#news > dl.newslist > dd > a
Critical rsync security release 3.4.0 div#news > dl.newslist > dd > a
Package Search: div#pkgsearch > form#pkgsearch-form > fieldset > label
more div#pkg-updates > h3 > span.more > a
x86_64 tbody > tr > td.pkg-arch > a
x86_64 tbody > tr > td.pkg-arch > a
x86_64 tbody > tr > td.pkg-arch > a
x86_64 tbody > tr > td.pkg-arch > a
x86_64 tbody > tr > td.pkg-arch > a
x86_64 tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
Wiki div#nav-sidebar > ul > li > a
Manual Pages div#nav-sidebar > ul > li > a
Installation Guide div#nav-sidebar > ul > li > a
Mailing Lists div#nav-sidebar > ul > li > a
IRC Channels div#nav-sidebar > ul > li > a
Planet Arch div#nav-sidebar > ul > li > a
International Communities div#nav-sidebar > ul > li > a
Donate div#nav-sidebar > ul > li > a
T-shirts via Freewear div#nav-sidebar > ul > li > a
T-shirts via HELLOTUX div#nav-sidebar > ul > li > a
Mirrorlist Updater div#nav-sidebar > ul > li > a
Mirror List div#nav-sidebar > ul > li > a
Mirror Status div#nav-sidebar > ul > li > a
Getting involved div#nav-sidebar > ul > li > a
Dev Blog div#nav-sidebar > ul > li > a
Projects in Git div#nav-sidebar > ul > li > a
Developer Wiki div#nav-sidebar > ul > li > a
Package Groups div#nav-sidebar > ul > li > a
Todo Lists div#nav-sidebar > ul > li > a
ISO Release List div#nav-sidebar > ul > li > a
Visualizations div#nav-sidebar > ul > li > a
Differences Reports div#nav-sidebar > ul > li > a
Developers div#nav-sidebar > ul > li > a
Package Maintainers div#nav-sidebar > ul > li > a
Support Staff div#nav-sidebar > ul > li > a
Developer Fellows div#nav-sidebar > ul > li > a
Package Maintainer Fellows div#nav-sidebar > ul > li > a
Support Staff Fellows div#nav-sidebar > ul > li > a
Signing Master Keys div#nav-sidebar > ul > li > a
Press Coverage div#nav-sidebar > ul > li > a
Logos & Artwork div#nav-sidebar > ul > li > a
News Archives div#nav-sidebar > ul > li > a
RSS Feeds div#nav-sidebar > ul > li > a
Judd Vinet div#content > div#footer > p > a
Aaron Griffin div#content > div#footer > p > a
Levente Polyák div#content > div#footer > p > a
trademarks div#content > div#footer > p > a

These are opportunities to improve the legibility of your content.

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
x86_64 tbody > tr > td.pkg-arch > a
x86_64 tbody > tr > td.pkg-arch > a
x86_64 tbody > tr > td.pkg-arch > a
x86_64 tbody > tr > td.pkg-arch > a
x86_64 tbody > tr > td.pkg-arch > a
x86_64 tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
any tbody > tr > td.pkg-arch > a
Wiki div#nav-sidebar > ul > li > a
Manual Pages div#nav-sidebar > ul > li > a
Installation Guide div#nav-sidebar > ul > li > a
Mailing Lists div#nav-sidebar > ul > li > a
IRC Channels div#nav-sidebar > ul > li > a
Planet Arch div#nav-sidebar > ul > li > a
Donate div#nav-sidebar > ul > li > a
T-shirts via Freewear div#nav-sidebar > ul > li > a
T-shirts via HELLOTUX div#nav-sidebar > ul > li > a
Mirrorlist Updater div#nav-sidebar > ul > li > a
Mirror List div#nav-sidebar > ul > li > a
Mirror Status div#nav-sidebar > ul > li > a
Getting involved div#nav-sidebar > ul > li > a
Dev Blog div#nav-sidebar > ul > li > a
Projects in Git div#nav-sidebar > ul > li > a
Developer Wiki div#nav-sidebar > ul > li > a
Package Groups div#nav-sidebar > ul > li > a
Todo Lists div#nav-sidebar > ul > li > a
ISO Release List div#nav-sidebar > ul > li > a
Visualizations div#nav-sidebar > ul > li > a
Differences Reports div#nav-sidebar > ul > li > a
Developers div#nav-sidebar > ul > li > a
Package Maintainers div#nav-sidebar > ul > li > a
Support Staff div#nav-sidebar > ul > li > a
Developer Fellows div#nav-sidebar > ul > li > a
Package Maintainer Fellows div#nav-sidebar > ul > li > a
Support Staff Fellows div#nav-sidebar > ul > li > a
Signing Master Keys div#nav-sidebar > ul > li > a
Press Coverage div#nav-sidebar > ul > li > a
Logos & Artwork div#nav-sidebar > ul > li > a
News Archives div#nav-sidebar > ul > li > a
RSS Feeds div#nav-sidebar > ul > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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>`
Image elements have `[alt]` attributes
Form elements have associated labels
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
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.
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
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
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`[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
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[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
`[role]` values are valid
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
Buttons have an accessible name
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">`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
`<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.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

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
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
83

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.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
archlinux.org/packages/?sort=-last_updatemore

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 are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback