Skip to content
Audit Complete

Results for https://www.fedoraproject.org

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 20:27 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

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%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

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

Top Priorities (5)

1

Content-Security-Policy header is missing

Security › Security Headers
2

No Content-Security-Policy header found

Security › Content Security Policy
3

1 button(s) with no accessible text

Accessibility › Link & Button Quality
4

17 image(s) missing alt attribute

Accessibility › Alt Text Quality
5

4 image-in-link without alt text

Accessibility › Alt Text Quality
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fedoraproject.org)](https://beavercheck.com/results/670542e0-6791-f4ea-a889-96fde02fd4f9)
<a href="https://beavercheck.com/results/670542e0-6791-f4ea-a889-96fde02fd4f9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fedoraproject.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fedoraproject.org

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

83
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
67
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
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.

1.36 s

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

4.66 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.018

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

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

4.68 s

Detailed Report

Audit breakdown by category with detailed findings.

83

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
www.fedoraproject.org/assets/webfonts/fa-solid-900.woff20.0 ms110.7 KiB
www.fedoraproject.org/fonts/montserrat/Montserrat-Bold.ttf0.0 ms86.9 KiB
www.fedoraproject.org/fonts/montserrat/Montserrat-SemiBold.ttf0.0 ms86.3 KiB
www.fedoraproject.org/fonts/open-sans/OpenSans-Medium.ttf0.0 ms77.5 KiB
www.fedoraproject.org/fonts/open-sans/OpenSans-Regular.ttf0.0 ms77.3 KiB
www.fedoraproject.org/fonts/open-sans/OpenSans-SemiBold.ttf0.0 ms77.1 KiB
www.fedoraproject.org/fonts/open-sans/OpenSans-Bold.ttf0.0 ms75.2 KiB
www.fedoraproject.org/assets/css/fontawesome.min.css0.0 ms20.2 KiB
www.fedoraproject.org/_nuxt/entry.BZUDMrtA.css0.0 ms13.2 KiB
www.fedoraproject.org/assets/images/cloud-logo-light.png604800.0 s22.6 KiB
www.fedoraproject.org/assets/images/digital-public-goods.svg0.0 ms2.2 KiB
www.fedoraproject.org/assets/images/cloud-logo-dark.png604800.0 s20.8 KiB
www.fedoraproject.org/assets/images/IoT-logo-light.png604800.0 s16.3 KiB
www.fedoraproject.org/assets/images/workstation-logo-light.png604800.0 s15.9 KiB
www.fedoraproject.org/_nuxt/default.DOs1B96t.css0.0 ms1.6 KiB
www.fedoraproject.org/assets/images/IoT-logo-dark.png604800.0 s15.1 KiB
www.fedoraproject.org/assets/images/workstation-logo-dark.png604800.0 s13.1 KiB
www.fedoraproject.org/assets/svgs/weblate.svg0.0 ms1.2 KiB
www.fedoraproject.org/assets/images/coreos-logo-light.png604800.0 s11.5 KiB
www.fedoraproject.org/assets/images/server-logo-light.png604800.0 s11.4 KiB
www.fedoraproject.org/assets/images/logos/fedora-blue.png604800.0 s10.0 KiB
www.fedoraproject.org/assets/images/server-logo-dark.png604800.0 s9.8 KiB
www.fedoraproject.org/assets/images/kde-logo-dark.png604800.0 s9.8 KiB
www.fedoraproject.org/assets/images/coreos-logo-dark.png604800.0 s9.7 KiB
www.fedoraproject.org/assets/images/kde-logo-light.png604800.0 s9.6 KiB
www.fedoraproject.org/assets/images/logo-sponsored-by-red-hat.png604800.0 s8.5 KiB
www.fedoraproject.org/assets/svgs/matrix-favicon.svg0.0 ms820 B
www.fedoraproject.org/js/darkmode.js0.0 ms690 B
www.fedoraproject.org/assets/svgs/life-preserver.svg0.0 ms442 B
www.fedoraproject.org/_nuxt/FpImage.ChWhdJEV.css0.0 ms307 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/cloud-logo-light.png22.5 KiB20.0 KiB
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/IoT-logo-light.png16.2 KiB14.3 KiB
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/workstation-logo-light.png15.8 KiB12.0 KiB
Fedora Logo section.p-4 > div.mx-auto > div.w-[200px] > img.FPImage
www.fedoraproject.org/assets/images/logos/fedora-blue.png9.9 KiB8.8 KiB
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/coreos-logo-light.png11.4 KiB8.8 KiB
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/server-logo-light.png11.3 KiB8.8 KiB
Sponsored by Red Hat Logo section.bg-black > div.mx-auto > div.w-[200px] > img.FPImage
www.fedoraproject.org/assets/images/logo-sponsored-by-red-hat.png8.3 KiB7.2 KiB
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/kde-logo-light.png9.5 KiB6.9 KiB

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.

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.

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

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.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 300 ms 31.2 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/kde-logo-light.png
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/workstation-logo-light.png
Fedora Logo section.p-4 > div.mx-auto > div.w-[200px] > img.FPImage
www.fedoraproject.org/assets/images/logos/fedora-blue.png
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/coreos-logo-light.png
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/server-logo-light.png
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/cloud-logo-light.png
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/IoT-logo-light.png
section.align-end > a > div.flex > img.FPImage section.align-end > a > div.flex > img.FPImage
www.fedoraproject.org/assets/images/digital-public-goods.svg
Sponsored by Red Hat Logo section.bg-black > div.mx-auto > div.w-[200px] > img.FPImage
www.fedoraproject.org/assets/images/logo-sponsored-by-red-hat.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused JavaScript
Avoids enormous network payloads Total size was 844 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.6 s
Avoid long main-thread tasks 2 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 10 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 60 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
67

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.

Failing Elements
Latest release header.-mb-1 > section.container > a.my-4 > p.text-xs
43 header.-mb-1 > section.container > a.my-4 > p.text-5xl
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Failing Elements
Editions Workstation KDE Plasma Server Cloud CoreOS IoT footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Atomic Desktops Silverblue Kinoite Sway Atomic Budgie Atomic COSMIC Atomic footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Spins Xfce Desktop Cinnamon Desktop MATE+Compiz Desktop i3 Tiling WM LXQt Deskt… footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Labs Astronomy Design Suite Games Jam Python Classroom Scientific Security Lab footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Languages العربية Беларуская Bulgarian Català Čeština Deutsch Ελληνικά English … footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Failing Elements
The leading Linux desktop div.container > div.relative > a > h3.bg-gradient-to-r

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Failing Elements
html.scroll-smooth html.scroll-smooth

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.section-headers > div#section-header-3 > div.m-icon > img.FPImage div.section-headers > div#section-header-3 > div.m-icon > img.FPImage
section.align-end > a > div.flex > img.FPImage section.align-end > a > div.flex > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Failing Elements
div#__nuxt > div#app > nav#mobile > input#expander div#__nuxt > div#app > nav#mobile > input#expander

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
main.w-full > header.-mb-1 > section.align-end > a main.w-full > header.-mb-1 > section.align-end > a

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.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Document has a main landmark.
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
`[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
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 a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
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.
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
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.section-headers > div#section-header-3 > div.m-icon > img.FPImage div.section-headers > div#section-header-3 > div.m-icon > img.FPImage
section.align-end > a > div.flex > img.FPImage section.align-end > a > div.flex > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage

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
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

99
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
67
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
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.

334 ms

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

654 ms

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

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

377 ms

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

654 ms

Detailed Report

Audit breakdown by category with detailed findings.

99

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
www.fedoraproject.org/assets/webfonts/fa-solid-900.woff20.0 ms110.7 KiB
www.fedoraproject.org/fonts/montserrat/Montserrat-Bold.ttf0.0 ms86.9 KiB
www.fedoraproject.org/fonts/montserrat/Montserrat-SemiBold.ttf0.0 ms86.3 KiB
www.fedoraproject.org/fonts/montserrat/Montserrat-Regular.ttf0.0 ms86.2 KiB
www.fedoraproject.org/fonts/open-sans/OpenSans-Medium.ttf0.0 ms77.5 KiB
www.fedoraproject.org/fonts/open-sans/OpenSans-Regular.ttf0.0 ms77.3 KiB
www.fedoraproject.org/fonts/open-sans/OpenSans-SemiBold.ttf0.0 ms77.1 KiB
www.fedoraproject.org/fonts/open-sans/OpenSans-Bold.ttf0.0 ms75.2 KiB
www.fedoraproject.org/assets/css/fontawesome.min.css0.0 ms20.2 KiB
www.fedoraproject.org/_nuxt/entry.BZUDMrtA.css0.0 ms13.2 KiB
www.fedoraproject.org/assets/images/cloud-logo-light.png604800.0 s22.6 KiB
www.fedoraproject.org/assets/images/digital-public-goods.svg0.0 ms2.2 KiB
www.fedoraproject.org/assets/images/cloud-logo-dark.png604800.0 s20.8 KiB
www.fedoraproject.org/assets/images/IoT-logo-light.png604800.0 s16.3 KiB
www.fedoraproject.org/_nuxt/default.DOs1B96t.css0.0 ms1.6 KiB
www.fedoraproject.org/assets/images/workstation-logo-light.png604800.0 s15.9 KiB
www.fedoraproject.org/assets/images/IoT-logo-dark.png604800.0 s15.1 KiB
www.fedoraproject.org/assets/images/workstation-logo-dark.png604800.0 s13.1 KiB
www.fedoraproject.org/assets/images/coreos-logo-light.png604800.0 s11.5 KiB
www.fedoraproject.org/assets/images/server-logo-light.png604800.0 s11.4 KiB
www.fedoraproject.org/assets/svgs/weblate.svg0.0 ms1.1 KiB
www.fedoraproject.org/assets/images/logos/fedora-blue.png604800.0 s10.0 KiB
www.fedoraproject.org/assets/svgs/matrix-favicon.svg0.0 ms1007 B
www.fedoraproject.org/assets/images/server-logo-dark.png604800.0 s9.8 KiB
www.fedoraproject.org/assets/images/kde-logo-dark.png604800.0 s9.8 KiB
www.fedoraproject.org/assets/images/coreos-logo-dark.png604800.0 s9.7 KiB
www.fedoraproject.org/assets/images/kde-logo-light.png604800.0 s9.6 KiB
www.fedoraproject.org/assets/images/logo-sponsored-by-red-hat.png604800.0 s8.3 KiB
www.fedoraproject.org/js/darkmode.js0.0 ms690 B
www.fedoraproject.org/assets/svgs/life-preserver.svg0.0 ms442 B
www.fedoraproject.org/_nuxt/FpImage.ChWhdJEV.css0.0 ms307 B

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.

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.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/cloud-logo-light.png22.5 KiB20.0 KiB
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/IoT-logo-light.png16.2 KiB14.3 KiB
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/workstation-logo-light.png15.8 KiB12.0 KiB
Fedora Logo section.p-4 > div.mx-auto > div.w-[200px] > img.FPImage
www.fedoraproject.org/assets/images/logos/fedora-blue.png9.9 KiB8.8 KiB
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/coreos-logo-light.png11.4 KiB8.8 KiB
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/server-logo-light.png11.3 KiB8.8 KiB
Sponsored by Red Hat Logo section.bg-black > div.mx-auto > div.w-[200px] > img.FPImage
www.fedoraproject.org/assets/images/logo-sponsored-by-red-hat.png8.3 KiB7.2 KiB
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/kde-logo-light.png9.5 KiB7.0 KiB

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

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 40 ms 30.4 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/kde-logo-light.png
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/workstation-logo-light.png
Fedora Logo section.p-4 > div.mx-auto > div.w-[200px] > img.FPImage
www.fedoraproject.org/assets/images/logos/fedora-blue.png
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/coreos-logo-light.png
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/server-logo-light.png
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/cloud-logo-light.png
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/IoT-logo-light.png
section.align-end > a > div.flex > img.FPImage section.align-end > a > div.flex > img.FPImage
www.fedoraproject.org/assets/images/digital-public-goods.svg
Sponsored by Red Hat Logo section.bg-black > div.mx-auto > div.w-[200px] > img.FPImage
www.fedoraproject.org/assets/images/logo-sponsored-by-red-hat.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Time to Interactive 0.7 s
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused JavaScript
Avoids enormous network payloads Total size was 930 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.2 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 10 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 60 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
67

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Failing Elements
div.section-headers > div.px-2 > div.group > button#themeSwitch div.section-headers > div.px-2 > div.group > button#themeSwitch

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
section.align-end > a > div.flex > img.FPImage section.align-end > a > div.flex > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Failing Elements
nav#desktop > div.section-headers > div.section-header > input#button-downloads-a nav#desktop > div.section-headers > div.section-header > input#button-downloads-a
nav#desktop > div.section-headers > div.section-header > input#button-downloads-b nav#desktop > div.section-headers > div.section-header > input#button-downloads-b
nav#desktop > div.section-headers > div.section-header > input#button-contributors-a nav#desktop > div.section-headers > div.section-header > input#button-contributors-a
nav#desktop > div.section-headers > div.section-header > input#button-contributors-b nav#desktop > div.section-headers > div.section-header > input#button-contributors-b
nav#desktop > div.section-headers > div.section-header > input#button-connections-a nav#desktop > div.section-headers > div.section-header > input#button-connections-a
nav#desktop > div.section-headers > div.section-header > input#button-connections-b nav#desktop > div.section-headers > div.section-header > input#button-connections-b
nav#desktop > div.section-headers > div.section-header > input#button-help-a nav#desktop > div.section-headers > div.section-header > input#button-help-a
nav#desktop > div.section-headers > div.section-header > input#button-help-b nav#desktop > div.section-headers > div.section-header > input#button-help-b
nav#desktop > div.section-headers > div.section-header > input#button-languages-a nav#desktop > div.section-headers > div.section-header > input#button-languages-a
nav#desktop > div.section-headers > div.section-header > input#button-languages-b nav#desktop > div.section-headers > div.section-header > input#button-languages-b

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Latest release header.-mb-1 > section.container > a.my-4 > p.text-xs
43 header.-mb-1 > section.container > a.my-4 > p.text-5xl
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Failing Elements
Editions Workstation KDE Plasma Server Cloud CoreOS IoT footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Atomic Desktops Silverblue Kinoite Sway Atomic Budgie Atomic COSMIC Atomic footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Spins Xfce Desktop Cinnamon Desktop MATE+Compiz Desktop i3 Tiling WM LXQt Deskt… footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Labs Astronomy Design Suite Games Jam Python Classroom Scientific Security Lab footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Failing Elements
A Registered Digital Public Good section.align-end > a > div.flex > h3.hidden

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Failing Elements
html.scroll-smooth html.scroll-smooth

These are opportunities to improve the interpretation of your content by users in different locales.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
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
Touch targets have sufficient size and spacing.
Document has a main landmark.
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
`[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
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 a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
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.
96

Best Practices

User Experience

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

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
www.fedoraproject.org/assets/images/kde-logo-light.png352 x 80 (4.40)700 x 154 (4.55)
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
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
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
section.align-end > a > div.flex > img.FPImage section.align-end > a > div.flex > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage

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
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback