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
savannah.nongnu.org/images/Savannah.theme/floating.png	0.0 ms	18.1 KiB
savannah.nongnu.org/css/internal/base.css	0.0 ms	16.6 KiB
savannah.nongnu.org/css/Savannah.css	0.0 ms	8.3 KiB
savannah.nongnu.org/images/Savannah.theme/thin-image.png	0.0 ms	6.1 KiB
savannah.nongnu.org/images/Savannah.theme/leopard.png	0.0 ms	5.2 KiB
savannah.nongnu.org/images/Savannah.theme/arrows/top.orig.png	0.0 ms	2.3 KiB

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.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:11178.027000976563 label:Time to first byte subpart:timeToFirstByte] map[duration:349.5839990234375 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-P

nodeLabel: The periodical reminders weren't active since 2016-11-30. Now they work again,…

path: 1,HTML,1,BODY,0,DIV,2,DIV,2,DIV,16,DIV,6,DIV,3,P

selector: div.indexcenter > div.box > div.boxitem > p

snippet: <p>

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
savannah.nongnu.org/	http/1.1
savannah.nongnu.org/css/Savannah.css	http/1.1
savannah.nongnu.org/images/Savannah.theme/floating.png	http/1.1
savannah.nongnu.org/images/Savannah.theme/thin-image.png	http/1.1
savannah.nongnu.org/images/Savannah.theme/arrows/top.orig.png	http/1.1
savannah.nongnu.org/css/internal/base.css	http/1.1
savannah.nongnu.org/images/Savannah.theme/leopard.png	http/1.1
savannah.nongnu.org/images/Savannah.theme/icon.png	http/1.1

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
savannah.nongnu.org/css/internal/base.css	16.6 KiB	377 ms
savannah.nongnu.org/css/Savannah.css	8.3 KiB	227 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
Back to Savannah Homepage `ul.menu > li.menulogo > a > img`	savannah.nongnu.org/images/Savannah.theme/floating.png	17.8 KiB	14.9 KiB
Support freedom `li > span.button > a > img`	savannah.nongnu.org/images/Savannah.theme/thin-image.png	5.9 KiB	4.8 KiB
Latest News `div#top > div.indexcenter > div.box > div.boxtitle`	savannah.nongnu.org/images/Savannah.theme/leopard.png	5.0 KiB	4.3 KiB

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.

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

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 11.2 KiB

URL	Transfer Size	Est Savings
savannah.nongnu.org/css/internal/base.css	16.6 KiB	6.2 KiB
savannah.nongnu.org/css/Savannah.css	8.3 KiB	4.9 KiB

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: 150 ms 14.0 KiB

URL	Transfer Size	Est Savings
savannah.nongnu.org/css/internal/base.css	16.4 KiB	14.0 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: 2.1 s

URL	Time Spent
www.nongnu.org/	975 ms
savannah.nongnu.org/	677 ms
savannah.nongnu.org/	480 ms
savannah.nongnu.org/	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 7.7 s

URL	Time Spent
savannah.nongnu.org/	7.8 s

●Time to Interactive 3.2 s

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Max Potential First Input Delay 20 ms

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 66 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.3 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 80 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

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. 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
[...] `div.box > div.boxitem > p > a`
download area `div.box > div.boxitem > p > a`
audio-vi ... .gnu.org `div.box > div.boxitem > p > a`
[...] `div.box > div.boxitem > p > a`
[...] `div.box > div.boxitemalt > p > a`
[...] `div.box > div.boxitem > p > a`
[...] `div.box > div.boxitemalt > 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
Login `div.realbody > ul.menu > li.menuitem > a.menulink`
New User `div.realbody > ul.menu > li.menuitem > a.menulink`
Language `div.realbody > ul.menu > li.menuitem > a.menulink`
Clean Reload `div.realbody > ul.menu > li.menuitem > a.menulink`
ul.menu > li.menusearch > form > input `ul.menu > li.menusearch > form > input`
Hosting requirements `div.realbody > ul.menu > li.menuitem > a.menulink`
Register New Project `div.realbody > ul.menu > li.menuitem > a.menulink`
Full List `div.realbody > ul.menu > li.menuitem > a.menulink`
Contributors Wanted `div.realbody > ul.menu > li.menuitem > a.menulink`
Statistics `div.realbody > ul.menu > li.menuitem > a.menulink`
User Docs: FAQ `div.realbody > ul.menu > li.menuitem > a.menulink`
Get Support `div.realbody > ul.menu > li.menuitem > a.menulink`
Contact Savannah `div.realbody > ul.menu > li.menuitem > a.menulink`
Help GNU `div.realbody > ul.menu > li.menuitem > a.menulink`
All GNU Packages `div.realbody > ul.menu > li.menuitem > a.menulink`
Dev Resources `div.realbody > ul.menu > li.menuitem > a.menulink`
License List `div.realbody > ul.menu > li.menuitem > a.menulink`
GNU Mirrors `div.realbody > ul.menu > li.menuitem > a.menulink`
Coming Events `div.realbody > ul.menu > li.menuitem > a.menulink`
Free Software Directory `div.realbody > ul.menu > li.menuitem > a.menulink`
GNU Savannah `div.realbody > ul.menu > li.menuitem > a.menulink`
Puszcza `div.realbody > ul.menu > li.menuitem > a.menulink`
[download] SFTP disabled `div.indexcenter > div.box > div.boxitem > a`
re-enabling reminders `div.indexcenter > div.box > div.boxitem > a`
ssh member access updated `div.indexcenter > div.box > div.boxitem > 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

●Input buttons have discernible text.

●Form elements have associated labels

●Select elements have associated label elements.

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

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Identical links have the same purpose.

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

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

○Heading elements appear in a sequentially-descending order

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

○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

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
savannah.nongnu.org/	Allowed
savannah.nongnu.org/css/Savannah.css	Allowed
savannah.nongnu.org/images/Savannah.theme/floating.png	Allowed
savannah.nongnu.org/images/Savannah.theme/thin-image.png	Allowed
savannah.nongnu.org/images/Savannah.theme/arrows/top.orig.png	Allowed
savannah.nongnu.org/css/internal/base.css	Allowed
savannah.nongnu.org/images/Savannah.theme/leopard.png	Allowed
savannah.nongnu.org/images/Savannah.theme/icon.png	Allowed

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Support freedom `li > span.button > a > img`	savannah.nongnu.org/images/Savannah.theme/thin-image.png	119 x 20 (5.95)	240 x 28 (8.57)

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.

	URL	Displayed size	Actual size	Expected size
Back to Savannah Homepage `ul.menu > li.menulogo > a > img`	savannah.nongnu.org/images/Savannah.theme/floating.png	144 x 125	144 x 125	216 x 188

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●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

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●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

○Ensure CSP is effective against XSS attacks

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`