Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
about.gitea.com/img/platform-logos.png	0.0 ms	1.6 MiB
about.gitea.com/img/gitea-cloud-concept.png	0.0 ms	772.7 KiB
about.gitea.com/img/gitea-enterprise-concept.png	0.0 ms	752.7 KiB
about.gitea.com/img/integration-logos.png	0.0 ms	489.7 KiB
about.gitea.com/img/home-screenshot.png	0.0 ms	271.7 KiB
avatars.githubusercontent.com/u/21979?v=4	300.0 s	159.3 KiB
about.gitea.com/img/home-screenshot-2.png	0.0 ms	115.4 KiB
about.gitea.com/_nuxt/entry.3765936f.js	0.0 ms	79.5 KiB
about.gitea.com/img/SOC2-blue.png	0.0 ms	33.2 KiB
about.gitea.com/_nuxt/Footer.fd3f6c22.js	0.0 ms	17.8 KiB
about.gitea.com/_nuxt/Newsletter.e292cc55.js	0.0 ms	11.1 KiB
about.gitea.com/_nuxt/index.84b60db4.js	0.0 ms	10.2 KiB
about.gitea.com/_nuxt/asyncData.15a86364.js	0.0 ms	4.9 KiB
about.gitea.com/_nuxt/cookie.6a18c7a2.js	0.0 ms	3.8 KiB
about.gitea.com/img/logos/mastercard.svg	0.0 ms	3.7 KiB
about.gitea.com/img/logos/openstack.svg	0.0 ms	3.3 KiB
about.gitea.com/img/default_profile.png	0.0 ms	3.2 KiB
about.gitea.com/img/logos/mtk.svg	0.0 ms	2.5 KiB
about.gitea.com/img/logos/google.svg	0.0 ms	2.4 KiB
about.gitea.com/gitea-text.svg	0.0 ms	2.3 KiB
about.gitea.com/img/logos/two-sigma.svg	0.0 ms	2.0 KiB
about.gitea.com/_nuxt/cookie.529380eb.js	0.0 ms	1.7 KiB
js.hs-scripts.com/44783791.js	90.0 s	1.1 KiB
about.gitea.com/_nuxt/entry.8c3139fb.css	0.0 ms	795 B
/61044/original?auto=compress&codec=mozjpeg&cs=strip&auto...	43200.0 s	1.5 KiB
about.gitea.com/_nuxt/use-tree-walker.92dce54b.js	0.0 ms	734 B
about.gitea.com/_nuxt/PrivacyPolicyLink.2d385212.js	0.0 ms	668 B
about.gitea.com/_nuxt/_plugin-vue_export-helper.c27b6911.js	0.0 ms	462 B

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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:72.984 source:map[type:text value:[unattributed]]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Product screenshot `div.mx-auto > div.mt-20 > div.shadow-lg > img.w-[48rem]`	about.gitea.com/img/platform-logos.png	1.6 MiB	1.5 MiB
section.mx-auto > div.mt-8 > div.w-80 > img.h-24 `section.mx-auto > div.mt-8 > div.w-80 > img.h-24`	about.gitea.com/img/gitea-cloud-concept.png	772.3 KiB	765.2 KiB
section.mx-auto > div.mt-8 > div.w-80 > img.h-24 `section.mx-auto > div.mt-8 > div.w-80 > img.h-24`	about.gitea.com/img/gitea-enterprise-concept.png	752.3 KiB	745.2 KiB
Product screenshot `div.mx-auto > div.mt-20 > div.shadow-lg > img.w-[48rem]`	about.gitea.com/img/integration-logos.png	489.4 KiB	470.6 KiB
App screenshot `div.py-12 > div.mt-5 > div.-m-2 > img.rounded-md`	about.gitea.com/img/home-screenshot.png	271.4 KiB	232.8 KiB
Product screenshot `div.mx-auto > div.mx-auto > div.flex > img.w-[48rem]`	about.gitea.com/img/home-screenshot-2.png	115.1 KiB	101.4 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
about.gitea.com/_nuxt/entry.8c3139fb.css	795 B	60 ms

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 724 ms

URL	Time Spent
gitea.com/	724 ms
about.gitea.com/	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 50 ms 229.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-FN940L7CL7	173.1 KiB	68.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-KW5NFLQL	145.1 KiB	65.6 KiB
www.googletagmanager.com/gtag/js?id=AW-16517062921&cx=c&gtm=4e64h1	146.6 KiB	57.2 KiB
about.gitea.com/_nuxt/entry.3765936f.js	79.2 KiB	37.8 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
about.gitea.com/img/platform-logos.png	1.6 MiB
about.gitea.com/img/gitea-cloud-concept.png	772.7 KiB
about.gitea.com/img/gitea-enterprise-concept.png	752.7 KiB
about.gitea.com/img/integration-logos.png	489.7 KiB
about.gitea.com/img/home-screenshot.png	271.7 KiB
www.googletagmanager.com/gtag/js?id=G-FN940L7CL7	173.5 KiB
avatars.githubusercontent.com/u/21979?v=4	159.3 KiB
www.googletagmanager.com/gtag/js?id=AW-16517062921&cx=c&gtm=4e64h1	146.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-KW5NFLQL	145.2 KiB
about.gitea.com/img/home-screenshot-2.png	115.4 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
App screenshot `div.py-12 > div.mt-5 > div.-m-2 > img.rounded-md`	about.gitea.com/img/home-screenshot.png
SOC 2 Type 2 Certified `div.xl:grid > div.space-y-8 > div.flex > img.h-24`	about.gitea.com/img/SOC2-blue.png
nav.mx-auto > div.flex > a.-m-1.5 > img.h-12 `nav.mx-auto > div.flex > a.-m-1.5 > img.h-12`	about.gitea.com/gitea-text.svg
div.mx-auto > figure.rounded-2xl > figcaption.flex > img.h-10 `div.mx-auto > figure.rounded-2xl > figcaption.flex > img.h-10`	about.gitea.com/img/logos/mtk.svg

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

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 10 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.6 s

●Avoid long main-thread tasks 1 long task found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 40 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 0 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Docker Pulls `div.mx-auto > dl.grid > div.mx-auto > dt.text-base`
Github Stars `div.mx-auto > dl.grid > div.mx-auto > dt.text-base`
Installations `div.mx-auto > dl.grid > div.mx-auto > dt.text-base`
Contributors `div.mx-auto > dl.grid > div.mx-auto > dt.text-base`
Dev/Deploy faster `div.bg-white > div.mx-auto > div.mx-auto > h2.text-base`
GitHub Actions `div.relative > dd.mt-2 > span > a.text-main-600`
Cargo `div.relative > dd.mt-2 > span > a.text-main-600`
Chef `div.relative > dd.mt-2 > span > a.text-main-600`
Composer `div.relative > dd.mt-2 > span > a.text-main-600`
Conan `div.relative > dd.mt-2 > span > a.text-main-600`
Conda `div.relative > dd.mt-2 > span > a.text-main-600`
Container `div.relative > dd.mt-2 > span > a.text-main-600`
Helm `div.relative > dd.mt-2 > span > a.text-main-600`
Maven `div.relative > dd.mt-2 > span > a.text-main-600`
NPM `div.relative > dd.mt-2 > span > a.text-main-600`
NuGet `div.relative > dd.mt-2 > span > a.text-main-600`
Pub `div.relative > dd.mt-2 > span > a.text-main-600`
PyPI `div.relative > dd.mt-2 > span > a.text-main-600`
RubyGems `div.relative > dd.mt-2 > span > a.text-main-600`
Vagrant `div.relative > dd.mt-2 > span > a.text-main-600`
Test, Deploy Faster `div.mx-auto > div.lg:ml-auto > div.lg:max-w-lg > h2.text-base`
Testimonials `div.relative > div.mx-auto > div.mx-auto > h2.text-lg`
$19 `div > div.ring-gray-200 > p.mt-6 > span.text-xl`
[1] `ul.text-gray-600 > li.flex > div > a.text-main-600`
privacy policy `div.mx-auto > div.w-full > p.mt-4 > a.font-semibold`
© 2026 CommitGo, Inc. All rights reserved. `div.xl:grid > div.space-y-8 > div.mt-16 > p.text-xs`

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
GitHub Actions `div.relative > dd.mt-2 > span > a.text-main-600`
Cargo `div.relative > dd.mt-2 > span > a.text-main-600`
Chef `div.relative > dd.mt-2 > span > a.text-main-600`
Composer `div.relative > dd.mt-2 > span > a.text-main-600`
Conan `div.relative > dd.mt-2 > span > a.text-main-600`
Conda `div.relative > dd.mt-2 > span > a.text-main-600`
Container `div.relative > dd.mt-2 > span > a.text-main-600`
Helm `div.relative > dd.mt-2 > span > a.text-main-600`
Maven `div.relative > dd.mt-2 > span > a.text-main-600`
NPM `div.relative > dd.mt-2 > span > a.text-main-600`
NuGet `div.relative > dd.mt-2 > span > a.text-main-600`
Pub `div.relative > dd.mt-2 > span > a.text-main-600`
PyPI `div.relative > dd.mt-2 > span > a.text-main-600`
RubyGems `div.relative > dd.mt-2 > span > a.text-main-600`
Vagrant `div.relative > dd.mt-2 > span > a.text-main-600`
[1] `ul.text-gray-600 > li.flex > div > a.text-main-600`

These are opportunities to improve the legibility of your content.

Navigation

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Gitea Cloud `div.mt-8 > div.w-80 > div.p-4 > h3.text-center`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

●`[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]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●ARIA toggle fields have accessible names

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

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

●Links have a discernible name

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○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

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

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

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
about.gitea.com/_nuxt/entry.3765936f.js line 12, col 54687	Executing inline script violates the following Content Security Policy directive 'script-src 'self' 'unsafe-inline' 'unsafe-eval' https://.gitea.com https://js.hs-scripts.com https://www.google-analytics.com https://avatars.githubusercontent.com https://forms.hscollectedforms.net https://www.googletagmanager.com https://plausible.io https://www.google.com https://googleads.g.doubleclick.net https://.hotjar.com https://*.hubspot.com 'sha256-6bOg0+lK47EBtruG5SsS775ShlAU8HySVBFG4JcDTFw=' 'sha384-P+FHlBmpB8T9B2+Z000KGOCtLCH7j8QzzBkJp4YTqGmhyFodHeTXKi7SfNmr3L2m' 'sha384-Wwt5Mdfp5LOjZyx0HdH7xhQLsWBYsnUFZiMi0k5QR0VyNzRt7SPyLDXpSdiipN5c' 'sha384-FNBCcgUnD1xsO/2deYCgZLZ3nSQFmKe54VQ3KrksEPX17Tsh40sfg3b2yRN5V0MI' 'sha384-vHmVfVrgmLxIN0m1reVb6uyaJWB9NZW+/hWcj/u2Ye7DFln0yukonWRWDvMMFZVF' 'sha384-wV/FyIfkoKuneA9gx32UbcC1rWydYJhlr+cMCHu0oN57ZtVcBz8nUCI/A5rPOyHo' 'sha384-dZxCwc6vU0CuhhgIyamLk/Glusart6mILBWtHLLDll8ImcoSV8avkVOfzAs9AtdM' 'sha384-H5lV+X4ArIi7UbTW1dbFOP7yUdafNa32kqlMY4klPH4jNHcZUPZnoA/sbauJ8J+p' 'sha384-SGi8/+reH11PtBjDk3wXAewiXTyKG97UEeSo2DbN55eHdo9ivl3S7y7hWZi/6tRz' 'sha384-fqUoYDFnkrB+Nc0PQKyrn0ndJw8V9U+utR3yEXBz7iAyKMk8LmbfDAEJl7BmTB6f' 'sha384-wtjKWFJGuMmMwIkPGhuEMp26ujkXc4D918kqpymUl96Ivce+KGkF+n5Wj9X35q4R''. Note that 'unsafe-inline' is ignored if either a hash or nonce value is present in the source list. The action has been blocked.
about.gitea.com/favicon.ico	`Failed to load resource: the server responded with a status of 403 ()`
js.hs-scripts.com/44783791.js line 2, col 311	Loading the script 'https://js.hs-analytics.net/analytics/1776803100000/44783791.js' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' 'unsafe-eval' https://.gitea.com https://js.hs-scripts.com https://www.google-analytics.com https://avatars.githubusercontent.com https://forms.hscollectedforms.net https://www.googletagmanager.com https://plausible.io https://www.google.com https://googleads.g.doubleclick.net https://.hotjar.com https://*.hubspot.com 'sha256-6bOg0+lK47EBtruG5SsS775ShlAU8HySVBFG4JcDTFw=' 'sha384-P+FHlBmpB8T9B2+Z000KGOCtLCH7j8QzzBkJp4YTqGmhyFodHeTXKi7SfNmr3L2m' 'sha384-Wwt5Mdfp5LOjZyx0HdH7xhQLsWBYsnUFZiMi0k5QR0VyNzRt7SPyLDXpSdiipN5c' 'sha384-FNBCcgUnD1xsO/2deYCgZLZ3nSQFmKe54VQ3KrksEPX17Tsh40sfg3b2yRN5V0MI' 'sha384-vHmVfVrgmLxIN0m1reVb6uyaJWB9NZW+/hWcj/u2Ye7DFln0yukonWRWDvMMFZVF' 'sha384-wV/FyIfkoKuneA9gx32UbcC1rWydYJhlr+cMCHu0oN57ZtVcBz8nUCI/A5rPOyHo' 'sha384-dZxCwc6vU0CuhhgIyamLk/Glusart6mILBWtHLLDll8ImcoSV8avkVOfzAs9AtdM' 'sha384-H5lV+X4ArIi7UbTW1dbFOP7yUdafNa32kqlMY4klPH4jNHcZUPZnoA/sbauJ8J+p' 'sha384-SGi8/+reH11PtBjDk3wXAewiXTyKG97UEeSo2DbN55eHdo9ivl3S7y7hWZi/6tRz' 'sha384-fqUoYDFnkrB+Nc0PQKyrn0ndJw8V9U+utR3yEXBz7iAyKMk8LmbfDAEJl7BmTB6f' 'sha384-wtjKWFJGuMmMwIkPGhuEMp26ujkXc4D918kqpymUl96Ivce+KGkF+n5Wj9X35q4R'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.
js.hs-scripts.com/44783791.js line 8, col 296	Loading the script 'https://js.hs-banner.com/v2/44783791/banner.js' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' 'unsafe-eval' https://.gitea.com https://js.hs-scripts.com https://www.google-analytics.com https://avatars.githubusercontent.com https://forms.hscollectedforms.net https://www.googletagmanager.com https://plausible.io https://www.google.com https://googleads.g.doubleclick.net https://.hotjar.com https://*.hubspot.com 'sha256-6bOg0+lK47EBtruG5SsS775ShlAU8HySVBFG4JcDTFw=' 'sha384-P+FHlBmpB8T9B2+Z000KGOCtLCH7j8QzzBkJp4YTqGmhyFodHeTXKi7SfNmr3L2m' 'sha384-Wwt5Mdfp5LOjZyx0HdH7xhQLsWBYsnUFZiMi0k5QR0VyNzRt7SPyLDXpSdiipN5c' 'sha384-FNBCcgUnD1xsO/2deYCgZLZ3nSQFmKe54VQ3KrksEPX17Tsh40sfg3b2yRN5V0MI' 'sha384-vHmVfVrgmLxIN0m1reVb6uyaJWB9NZW+/hWcj/u2Ye7DFln0yukonWRWDvMMFZVF' 'sha384-wV/FyIfkoKuneA9gx32UbcC1rWydYJhlr+cMCHu0oN57ZtVcBz8nUCI/A5rPOyHo' 'sha384-dZxCwc6vU0CuhhgIyamLk/Glusart6mILBWtHLLDll8ImcoSV8avkVOfzAs9AtdM' 'sha384-H5lV+X4ArIi7UbTW1dbFOP7yUdafNa32kqlMY4klPH4jNHcZUPZnoA/sbauJ8J+p' 'sha384-SGi8/+reH11PtBjDk3wXAewiXTyKG97UEeSo2DbN55eHdo9ivl3S7y7hWZi/6tRz' 'sha384-fqUoYDFnkrB+Nc0PQKyrn0ndJw8V9U+utR3yEXBz7iAyKMk8LmbfDAEJl7BmTB6f' 'sha384-wtjKWFJGuMmMwIkPGhuEMp26ujkXc4D918kqpymUl96Ivce+KGkF+n5Wj9X35q4R'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.
js.hs-scripts.com/44783791.js line 4, col 299	Loading the script 'https://js.hscollectedforms.net/collectedforms.js' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' 'unsafe-eval' https://.gitea.com https://js.hs-scripts.com https://www.google-analytics.com https://avatars.githubusercontent.com https://forms.hscollectedforms.net https://www.googletagmanager.com https://plausible.io https://www.google.com https://googleads.g.doubleclick.net https://.hotjar.com https://*.hubspot.com 'sha256-6bOg0+lK47EBtruG5SsS775ShlAU8HySVBFG4JcDTFw=' 'sha384-P+FHlBmpB8T9B2+Z000KGOCtLCH7j8QzzBkJp4YTqGmhyFodHeTXKi7SfNmr3L2m' 'sha384-Wwt5Mdfp5LOjZyx0HdH7xhQLsWBYsnUFZiMi0k5QR0VyNzRt7SPyLDXpSdiipN5c' 'sha384-FNBCcgUnD1xsO/2deYCgZLZ3nSQFmKe54VQ3KrksEPX17Tsh40sfg3b2yRN5V0MI' 'sha384-vHmVfVrgmLxIN0m1reVb6uyaJWB9NZW+/hWcj/u2Ye7DFln0yukonWRWDvMMFZVF' 'sha384-wV/FyIfkoKuneA9gx32UbcC1rWydYJhlr+cMCHu0oN57ZtVcBz8nUCI/A5rPOyHo' 'sha384-dZxCwc6vU0CuhhgIyamLk/Glusart6mILBWtHLLDll8ImcoSV8avkVOfzAs9AtdM' 'sha384-H5lV+X4ArIi7UbTW1dbFOP7yUdafNa32kqlMY4klPH4jNHcZUPZnoA/sbauJ8J+p' 'sha384-SGi8/+reH11PtBjDk3wXAewiXTyKG97UEeSo2DbN55eHdo9ivl3S7y7hWZi/6tRz' 'sha384-fqUoYDFnkrB+Nc0PQKyrn0ndJw8V9U+utR3yEXBz7iAyKMk8LmbfDAEJl7BmTB6f' 'sha384-wtjKWFJGuMmMwIkPGhuEMp26ujkXc4D918kqpymUl96Ivce+KGkF+n5Wj9X35q4R'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`