Skip to content
Audit Complete

Results for https://nongnu.org

Visit site

URL substituted: You submitted https://nongnu.org but we scanned https://www.nongnu.org instead — the HTTPS certificate on the submitted hostname didn't cover that name, so we retried on the www. variant

Spain Spain · Madrid Completed: Apr 22, 2026 20:30 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C73

Site Health

Score: 73 / 100

Based on 6 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%Infrastructure 10%Compliance 8%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

HSTS · 2029 peers
You 73
·
Avg 74
At average
0 50 100
Better than 33% of HSTS sites See full HSTS benchmark →
Apache · 377 peers
You 73
·
Avg 72
At average
0 50 100
Better than 45% of Apache sites See full Apache benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
3

No favicon or icon links detected

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Favicon & Branding
4

10 third-party resources (99% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
5

Cross-Origin-Embedder-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fnongnu.org)](https://beavercheck.com/results/e8cc36a4-42cf-49e8-947d-61cd2b8d9845)
<a href="https://beavercheck.com/results/e8cc36a4-42cf-49e8-947d-61cd2b8d9845"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnongnu.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fnongnu.org

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 3.2s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.
Your LCP is 3.2s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

1 critical 3 warning

4 barrier(s) likely increasing bounce by ~26%.

Speed (1)

Page loads in 3.2s

+5% bounce

Every additional 100ms above 2.5s costs conversions — you're 688ms over

Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$500 investment → $1,296/month returns + USD 7,500 risk avoided

Payback period: < 1 month First-year ROI: +3011%

Investment

$500

5h · 5 findings

Monthly returns

$1,296 /mo

~$15,555 / year

  • Conversions recovered $1,296
  • Bandwidth savings $0.02

Regulatory risk avoided

USD 7,500

if kept compliant

  • CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$150 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$625 / month at risk

~$7,500 / year if left unfixed

Compliance Risk

$7,500

CCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500

Bandwidth Waste

$0.02 /mo

203.8 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~20 KB per page load
    Saves $0.02/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 3 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

78
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
86
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
69
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.96 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.19 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

17.33 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

3.20 s

Detailed Report

Audit breakdown by category with detailed findings.

78

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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>

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
savannah.nongnu.org/css/internal/base.css16.6 KiB377 ms
savannah.nongnu.org/css/Savannah.css8.3 KiB227 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.

URLResource SizeEst Savings
Back to Savannah Homepage ul.menu > li.menulogo > a > img
savannah.nongnu.org/images/Savannah.theme/floating.png17.8 KiB14.9 KiB
Support freedom li > span.button > a > img
savannah.nongnu.org/images/Savannah.theme/thin-image.png5.9 KiB4.8 KiB
Latest News div#top > div.indexcenter > div.box > div.boxtitle
savannah.nongnu.org/images/Savannah.theme/leopard.png5.0 KiB4.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
URLTransfer SizeEst Savings
savannah.nongnu.org/css/internal/base.css16.6 KiB6.2 KiB
savannah.nongnu.org/css/Savannah.css8.3 KiB4.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
URLTransfer SizeEst Savings
savannah.nongnu.org/css/internal/base.css16.4 KiB14.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

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
URLTime 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
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. 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.
69

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.

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.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
Support freedom li > span.button > a > img
savannah.nongnu.org/images/Savannah.theme/thin-image.png119 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.

URLDisplayed sizeActual sizeExpected size
Back to Savannah Homepage ul.menu > li.menulogo > a > img
savannah.nongnu.org/images/Savannah.theme/floating.png144 x 125144 x 125216 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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

85
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
86
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.21 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.23 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

9.88 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.24 s

Detailed Report

Audit breakdown by category with detailed findings.

85

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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:15781.031000976562 label:Time to first byte subpart:timeToFirstByte] map[duration:358.0219990234375 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-P
nodeLabel: Paraphrasing Bob: Up until now all git services have been served by one solo v…
path: 1,HTML,1,BODY,0,DIV,2,DIV,2,DIV,16,DIV,2,DIV,3,P
selector: div.indexcenter > div.box > div.boxitem > p
snippet: <p>

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
savannah.nongnu.org/css/internal/base.css16.6 KiB162 ms
savannah.nongnu.org/css/Savannah.css8.3 KiB122 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.

URLResource SizeEst Savings
Back to Savannah Homepage ul.menu > li.menulogo > a > img
savannah.nongnu.org/images/Savannah.theme/floating.png17.8 KiB14.9 KiB
Support freedom li > span.button > a > img
savannah.nongnu.org/images/Savannah.theme/thin-image.png5.9 KiB5.5 KiB
Latest News div#top > div.indexcenter > div.box > div.boxtitle
savannah.nongnu.org/images/Savannah.theme/leopard.png5.0 KiB4.3 KiB

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: 40 ms 11.2 KiB
URLTransfer SizeEst Savings
savannah.nongnu.org/css/internal/base.css16.6 KiB6.2 KiB
savannah.nongnu.org/css/Savannah.css8.3 KiB4.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: 40 ms 14.0 KiB
URLTransfer SizeEst Savings
savannah.nongnu.org/css/internal/base.css16.4 KiB14.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: 809 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: 12.0 s
URLTime Spent
savannah.nongnu.org/12.1 s
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
Optimize viewport for mobile
Time to Interactive 1.2 s
Max Potential First Input Delay 20 ms
Minify JavaScript
Reduce unused JavaScript
Avoids enormous network payloads Total size was 66 KiB
Minimizes main-thread work 0.1 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
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. 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

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

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.

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.

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

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
Serves images with appropriate resolution
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`

Send Feedback