Lighthouse Report

Performance

First Contentful Paint

24.3 s

First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Speed Index

24.3 s

Speed Index shows how quickly the contents of a page are visibly populated. Learn more.

Largest Contentful Paint

24.5 s

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More

Time to Interactive

27.3 s

Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Total Blocking Time

1,160 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.

Cumulative Layout Shift

0.004

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.

Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.

Enable text compression

20.7 s

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL	Transfer Size	Potential Savings
…master/MAINTAINERS (codeberg.org)	4,573 KiB	4,147.1 KiB

Reduce initial server response time

3.49 s

Keep the server response time for the main document short because all other requests depend on it. Learn more.

URL	Time Spent
…master/MAINTAINERS (codeberg.org)	3,590 ms

Remove unused JavaScript

1.2 s

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

URL	Transfer Size	Potential Savings
…js/index.js?v=1.21.5~0-51-g40d2791 (codeberg.org)	345.9 KiB	220.5 KiB
…./web_src/fomantic/build/semantic.js	54.6 KiB	44.1 KiB
…./node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js	21.3 KiB	32.6 KiB
…./node_modules/@vue/compiler-core/dist/compiler-core.esm-bundler.js	17.2 KiB	30.5 KiB
…./node_modules/jquery/dist/jquery.js	27.7 KiB	23.7 KiB
…./node_modules/vue-bar-graph/dist/vue-bar-graph.common.js	38 KiB	20.5 KiB

Avoid serving legacy JavaScript to modern browsers

0.15 s

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More

URL		Potential Savings
…js/index.js?v=1.21.5~0-51-g40d2791 (codeberg.org)		11.4 KiB
…js/index.js?v=1.21.5~0-51-g40d2791:17:1031 (codeberg.org)	Array.prototype.filter
…js/index.js?v=1.21.5~0-51-g40d2791:17:1240 (codeberg.org)	Array.from
…js/index.js?v=1.21.5~0-51-g40d2791:17:2004 (codeberg.org)	Array.prototype.map
…js/index.js?v=1.21.5~0-51-g40d2791:17:8295 (codeberg.org)	Object.getOwnPropertyDescriptors
…js/index.js?v=1.21.5~0-51-g40d2791:17:8789 (codeberg.org)	Object.keys
…js/index.js?v=1.21.5~0-51-g40d2791:17:9022 (codeberg.org)	Object.values
…js/index.js?v=1.21.5~0-51-g40d2791:17:14693 (codeberg.org)	Object.getOwnPropertyNames

Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn more.

Remove unused CSS

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid an excessive DOM size 90,493 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

Statistic	Element	Value
Total DOM Elements		NaN
Maximum DOM Depth	<path d="M.75 3h14.5a.75.75 0 0 1 0 1.5H.75a.75.75 0 0 1 0-1.5ZM3 7.75A.75.75 0 0 1…">	13
Maximum Child Elements	<tbody>	NaN

All text remains visible during webfont loads

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Does not use passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.

URL	Location
…js/index.js?v=1.21.5~0-51-g40d2791 (codeberg.org)	line: 10

Avoid enormous network payloads Total size was 5,037 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL	Transfer Size
…master/MAINTAINERS (codeberg.org)	4,583.5 KiB
…js/index.js?v=1.21.5~0-51-g40d2791 (codeberg.org)	345.9 KiB
…css/index.css?v=1.21.5~0-51-g40d2791 (codeberg.org)	86.1 KiB
…js/webcomponents.js?v=1.21.5~0-51-g40d2791 (codeberg.org)	10.6 KiB
…css/theme-codeberg-auto.css?v=1.21.5~0-51-g40d2791 (codeberg.org)	4.3 KiB
/logo-kit/icon_inverted.svg (design.codeberg.org)	2.9 KiB
…img/favicon.png (codeberg.org)	2.5 KiB
…img/favicon.svg (codeberg.org)	1.1 KiB

Minimize main-thread work 4.0 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

Category	Time Spent
Style & Layout	3,025 ms
Other	538 ms
Parse HTML & CSS	187 ms
Script Evaluation	173 ms
Rendering	16 ms
Script Parsing & Compilation	13 ms

Avoid chaining critical requests 4 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Maximum critical path latency: 5,160 ms

Initial Navigation

…master/MAINTAINERS

(codeberg.org)

…js/webcomponents.js?v=1.21.5~0-51-g40d2791

(codeberg.org)

- 20 ms, 10.62 KiB

…css/index.css?v=1.21.5~0-51-g40d2791

(codeberg.org)

- 20 ms, 86.06 KiB

…css/theme-codeberg-auto.css?v=1.21.5~0-51-g40d2791

(codeberg.org)

- 20 ms, 4.29 KiB

…js/index.js?v=1.21.5~0-51-g40d2791

(codeberg.org)

- 50 ms, 345.93 KiB

Keep request counts low and transfer sizes small 8 requests • 5,037 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type	Requests	Transfer Size
Total	8	5,036.8 KiB
Document	1	4,583.5 KiB
Script	2	356.5 KiB
Stylesheet	2	90.4 KiB
Other	2	3.5 KiB
Image	1	2.9 KiB
Media	0	0 KiB
Font	0	0 KiB
Third-party	0	0 KiB

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport. Learn More

Element
Please try to follow the guidelines below. This will make things <td rel="L5" class="lines-code chroma">

Avoid large layout shifts 5 elements found

These DOM elements contribute most to the CLS of the page.

Element	CLS Contribution
List of maintainers and how to submit kernel changes <td rel="L3" class="lines-code chroma">	0.001
easier on the maintainers. Not all of these guidelines matter for every <td rel="L6" class="lines-code chroma">	0.001
1. Always _test_ your changes, however small, on at least 4 or <td rel="L9" class="lines-code chroma">	0.001
Please try to follow the guidelines below. This will make things <td rel="L5" class="lines-code chroma">	0.001
<td rel="L4" class="lines-code chroma">	0

Avoid long main-thread tasks 10 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

URL	Start Time	Duration
…master/MAINTAINERS (codeberg.org)	24,535 ms	1,077 ms
…master/MAINTAINERS (codeberg.org)	24,312 ms	114 ms
…master/MAINTAINERS (codeberg.org)	24,426 ms	109 ms
…master/MAINTAINERS (codeberg.org)	23,979 ms	105 ms
…master/MAINTAINERS (codeberg.org)	23,763 ms	101 ms
…master/MAINTAINERS (codeberg.org)	24,094 ms	100 ms
…master/MAINTAINERS (codeberg.org)	24,204 ms	98 ms
…master/MAINTAINERS (codeberg.org)	23,874 ms	95 ms
…js/index.js?v=1.21.5~0-51-g40d2791 (codeberg.org)	27,365 ms	75 ms
…js/index.js?v=1.21.5~0-51-g40d2791 (codeberg.org)	27,301 ms	50 ms

Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn more.

Serve images in next-gen formats

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Preconnect to required origins

Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn more.

Preload key requests

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.

Use HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Learn more.

Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more

Remove duplicate modules in JavaScript bundles

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

Uses efficient cache policy on static assets 1 resource found

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

URL	Cache TTL	Transfer Size
/logo-kit/icon_inverted.svg (design.codeberg.org)	None	3 KiB

User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

JavaScript execution time 0.2 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL	Total CPU Time	Script Evaluation	Script Parse
…master/MAINTAINERS (codeberg.org)	3,641 ms	2 ms	1 ms
…js/index.js?v=1.21.5~0-51-g40d2791 (codeberg.org)	232 ms	153 ms	12 ms
Unattributable	58 ms	0 ms	0 ms

Minimize third-party usage

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Avoids document.write()

For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.

Avoid non-composited animations

Animations which are not composited can be janky and increase CLS. Learn more

Avoids large JavaScript libraries with smaller alternatives 0 large libraries found

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size. Learn more.

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.

<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.

Definition list items are wrapped in <dl> elements

Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.

Presentational <table> elements avoid using <th>, <caption> or the [summary] attribute.

A table being used for layout purposes should not include data elements, such as the th or caption elements or the summary attribute, because this can create a confusing experience for screen reader users. Learn more.

Lists contain only <li> elements and script supporting elements (<script> and <template>).

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.

List items (<li>) are contained within <ul> or <ol> parent elements

Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.

Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.

Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.

<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.

Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.

The page has a logical tab order

Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.

Interactive elements indicate their purpose and state

Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.

The user's focus is directed to new content added to the page

If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.

User focus is not accidentally trapped in a region

A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.

Custom controls have associated labels

Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.

Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles. Learn more.

Visual order on the page follows DOM order

DOM order matches the visual order, improving navigation for assistive technology. Learn more.

Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true. Learn more.

HTML5 landmark elements are used to improve navigation

Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.