Skip to content
https://debian.org

Lighthouse Mobile

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

66

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.

RequestCache TTLTransfer Size
www.debian.org/Pics/debconf25_group_photo.jpg604800.0 s508.1 KiB
www.debian.org/Pics/mini-dc25-hamburg.jpg604800.0 s431.3 KiB
www.debian.org/Pics/calamares-installer.png604800.0 s275.8 KiB
www.debian.org/Pics/debian-funny-people-1024x576.jpg604800.0 s214.4 KiB
www.debian.org/Pics/mini-dc25-maceio.jpg604800.0 s151.2 KiB
www.debian.org/Pics/debian-swiss-knife-hands-1024x576.jpg604800.0 s118.5 KiB
www.debian.org/Pics/ceratopsian-fg.svg86400.0 s22.8 KiB
www.debian.org/Pics/debian-logo-1024x576.png604800.0 s32.1 KiB
www.debian.org/debian.css86400.0 s4.7 KiB
www.debian.org/Pics/users.svg86400.0 s3.4 KiB
www.debian.org/Pics/life-ring.svg86400.0 s3.1 KiB
www.debian.org/Pics/user-plus.svg86400.0 s3.0 KiB
www.debian.org/Pics/trophy.svg86400.0 s2.9 KiB
www.debian.org/startpage.css86400.0 s2.8 KiB
www.debian.org/Pics/list.svg86400.0 s2.6 KiB
www.debian.org/Pics/heartbeat.svg86400.0 s2.3 KiB
www.debian.org/Pics/security.svg86400.0 s2.1 KiB
www.debian.org/debhome.css86400.0 s1.6 KiB
www.debian.org/5img-carousel-slider.css86400.0 s1.4 KiB
www.debian.org/Pics/openlogo-50.png604800.0 s2.0 KiB
www.debian.org/debian-en.css86400.0 s482 B
www.debian.org/empty.css86400.0 s69 B

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
DebConf25 Group Photo div.slider-wrapper > div.inner > article > img
www.debian.org/Pics/debconf25_group_photo.jpg507.7 KiB471.8 KiB
Group photo of the MiniDebConf Hamburg 2025 div.slider-wrapper > div.inner > article > img
www.debian.org/Pics/mini-dc25-hamburg.jpg431.0 KiB396.4 KiB
Screenshot from the Calamares installer div.slider-wrapper > div.inner > article > img
www.debian.org/Pics/calamares-installer.png275.5 KiB238.2 KiB
Debian people at Debconf18 in Hsinchu really having fun div.slider-wrapper > div.inner > article > img
www.debian.org/Pics/debian-funny-people-1024x576.jpg214.2 KiB179.6 KiB
Group photo of the MiniDebConf Maceió 2025 div.slider-wrapper > div.inner > article > img
www.debian.org/Pics/mini-dc25-maceio.jpg151.1 KiB116.5 KiB
Debian is like a Swiss Army Knife div.slider-wrapper > div.inner > article > img
www.debian.org/Pics/debian-swiss-knife-hands-1024x576.jpg118.4 KiB83.8 KiB
Debian div.column > div > div.os-img-container > img
www.debian.org/Pics/debian-logo-1024x576.png32.0 KiB19.2 KiB

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: DebConf25 Group Photo
path: 1,HTML,1,BODY,3,SECTION,2,DIV,0,DIV,0,DIV,3,DIV,6,DIV,0,DIV,0,ARTICLE,1,IMG
selector: div.slider-wrapper > div.inner > article > img
snippet: <img src="Pics/debconf25_group_photo.jpg" alt="DebConf25 Group Photo" width="1024" height="598">

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.

URLTransfer SizeDuration
www.debian.org/debian.css4.7 KiB
www.debian.org/empty.css69 B
www.debian.org/debian-en.css482 B
www.debian.org/5img-carousel-slider.css1.4 KiB
www.debian.org/startpage.css2.8 KiB
www.debian.org/debhome.css1.6 KiB150 ms

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.

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: 750 ms
URLTime Spent
debian.org/750 ms
www.debian.org/0.0 ms

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
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 1,797 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.6 s
●Avoid long main-thread tasks 2 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 180 ms
●Server Backend Latencies 980 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 180 ms
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
69

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
div.column > div.row > div.community > a div.column > div.row > div.community > a
div.column > div.row > div.community > a div.column > div.row > div.community > a
div.column > div.row > div.community > a div.column > div.row > div.community > a
div.column > div.row > div.community > a div.column > div.row > div.community > a
div.column > div.row > div.community > a div.column > div.row > div.community > a
div.column > div.row > div.community > a div.column > div.row > div.community > a
div.column > div.row > div.community > a div.column > div.row > div.community > a
div.column > div.row > div.community > a div.column > div.row > div.community > a

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.

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
RSS div.column > div.project-news > div.project-news-content > a.rss_logo

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
div#searchbox > form > p > input div#searchbox > form > p > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select your language català dansk Deutsch español français Galego Indonesia Ita… div#pageLang > div#langSelector > div#langContainer > select

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
Blog div#navbar > ul > li > a
Other downloads div.column > div > div.os-img-container > a.os-other-download
Select your language català dansk Deutsch español français Galego Indonesia Ita… div#pageLang > div#langSelector > div#langContainer > select

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
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
○`[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 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
○`<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 type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○`<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.
96

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Debian div#upperheader > div#logo > a > img
www.debian.org/Pics/openlogo-50.png50 x 6150 x 6175 x 92
●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
●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 DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback