Skip to content
https://redmine.org

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

97

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.

RequestCache TTLTransfer Size
www.redmine.org/javascripts/jquery-3.6.1-ui-1.13.2-ujs-5.2.8.1.js?16793021290.0 ms101.5 KiB
/pagead/managed/js/adsense/m202604170101/show_ads_impl_fy...1209600.0 s177.5 KiB
www.redmine.org/javascripts/application.js?16793021290.0 ms9.1 KiB
www.redmine.org/javascripts/tribute-5.1.3.min.js?16793021290.0 ms9.1 KiB
www.redmine.org/stylesheets/application.css?167930212986400.0 s16.2 KiB
www.redmine.org/javascripts/jquery-migrate-3.3.2.min.js?16793021290.0 ms4.4 KiB
www.redmine.org/stylesheets/jquery/jquery-ui-1.13.2.css?167930212986400.0 s8.1 KiB
www.redmine.org/stylesheets/responsive.css?167930212986400.0 s5.0 KiB
www.redmine.org/javascripts/tablesort-5.2.1.min.js?16793021290.0 ms1.6 KiB
www.redmine.org/javascripts/responsive.js?16793021290.0 ms972 B
www.redmine.org/javascripts/tablesort-5.2.1.number.min.js?16793021290.0 ms655 B
www.redmine.org/stylesheets/tribute-5.1.3.css?167930212986400.0 s623 B
www.redmine.org/images/arrow_right.png86400.0 s586 B
www.redmine.org/images/arrow_left.png86400.0 s572 B
www.redmine.org/images/arrow_down.png86400.0 s556 B
www.redmine.org/images/external.png86400.0 s434 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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
/s/googlesans/v67/4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iq...50 ms
/s/googlesans/v67/4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iq...45 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.redmine.org/http/1.1
www.redmine.org/stylesheets/jquery/jquery-ui-1.13.2.css?1679302129http/1.1
www.redmine.org/stylesheets/tribute-5.1.3.css?1679302129http/1.1
www.redmine.org/stylesheets/application.css?1679302129http/1.1
www.redmine.org/stylesheets/responsive.css?1679302129http/1.1
www.redmine.org/javascripts/jquery-3.6.1-ui-1.13.2-ujs-5.2.8.1.js?1679302129http/1.1
www.redmine.org/javascripts/jquery-migrate-3.3.2.min.js?1679302129http/1.1
www.redmine.org/javascripts/tribute-5.1.3.min.js?1679302129http/1.1
www.redmine.org/javascripts/tablesort-5.2.1.min.js?1679302129http/1.1
www.redmine.org/javascripts/tablesort-5.2.1.number.min.js?1679302129http/1.1
www.redmine.org/javascripts/application.js?1679302129http/1.1
www.redmine.org/javascripts/responsive.js?1679302129http/1.1
www.redmine.org/attachments/download/8856/mastering_redmine.jpghttp/1.1
www.redmine.org/attachments/download/13894/plugin_dev.pnghttp/1.1
www.redmine.org/attachments/download/14647/redmine_cookbook.pnghttp/1.1
www.redmine.org/images/arrow_down.pnghttp/1.1
www.redmine.org/images/external.pnghttp/1.1
www.redmine.org/images/arrow_right.pnghttp/1.1
www.redmine.org/images/arrow_left.pnghttp/1.1
www.redmine.org/favicon.ico?1679302129http/1.1

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
www.redmine.org/javascripts/jquery-3.6.1-ui-1.13.2-ujs-5.2.8.1.js?1679302129101.5 KiB418 ms
www.redmine.org/javascripts/application.js?16793021299.1 KiB61 ms
www.redmine.org/javascripts/tablesort-5.2.1.number.min.js?1679302129655 B61 ms
www.redmine.org/javascripts/responsive.js?1679302129972 B61 ms
www.redmine.org/stylesheets/application.css?167930212916.2 KiB240 ms
www.redmine.org/javascripts/tribute-5.1.3.min.js?16793021299.1 KiB61 ms
www.redmine.org/javascripts/jquery-migrate-3.3.2.min.js?16793021294.4 KiB180 ms
www.redmine.org/stylesheets/responsive.css?16793021295.0 KiB180 ms
pagead2.googlesyndication.com/pagead/show_ads.js13.0 KiB296 ms
www.redmine.org/javascripts/tablesort-5.2.1.min.js?16793021291.6 KiB61 ms
www.redmine.org/stylesheets/tribute-5.1.3.css?1679302129623 B180 ms
www.redmine.org/stylesheets/jquery/jquery-ui-1.13.2.css?16793021298.1 KiB61 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
tr > td > a > img tr > td > a > img
www.redmine.org/attachments/download/14647/redmine_cookbook.png14.2 KiB12.9 KiB

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

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: 140 ms 229.8 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/adsense/m202604170101/show_ads_impl_fy...177.5 KiB124.4 KiB
www.redmine.org/javascripts/jquery-3.6.1-ui-1.13.2-ujs-5.2.8.1.js?1679302129101.2 KiB78.5 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js54.2 KiB26.8 KiB

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 4.7 KiB
URLTransfer SizeEst Savings
www.redmine.org/stylesheets/application.css?167930212916.2 KiB2.5 KiB
www.redmine.org/stylesheets/responsive.css?16793021295.0 KiB2.2 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: 0.0 ms 14.4 KiB
URLTransfer SizeEst Savings
www.redmine.org/stylesheets/application.css?167930212915.9 KiB14.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
tr > td > a > img tr > td > a > img
www.redmine.org/attachments/download/8856/mastering_redmine.jpg
tr > td > a > img tr > td > a > img
www.redmine.org/attachments/download/13894/plugin_dev.png
tr > td > a > img tr > td > a > img
www.redmine.org/attachments/download/14647/redmine_cookbook.png

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: 257 ms
URLTime Spent
redmine.org/257 ms
www.redmine.org/0.0 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Optimize viewport for mobile
●Time to Interactive 1.0 s
●Max Potential First Input Delay 30 ms
●Minify JavaScript
●Avoids enormous network payloads Total size was 554 KiB
●JavaScript execution time 0.1 s
●Minimizes main-thread work 0.3 s
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 20 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 80 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
○Avoid large layout shifts
84

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
Search div#quick-search > form > label > a
Overview div#main-menu > ul > li > a.overview
Download div#main-menu > ul > li > a.download
Activity div#main-menu > ul > li > a.activity
Roadmap div#main-menu > ul > li > a.roadmap
Issues div#main-menu > ul > li > a.issues
News div#main-menu > ul > li > a.news
Forums div#main-menu > ul > li > a.boards
Repository div#main-menu > ul > li > a.repository
Table of contents div.wiki > ul.toc > li > strong
Powered by Redmine © 2006-2023 Jean-Philippe Lang div#wrapper > div#wrapper2 > div#wrapper3 > div#footer

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
wiki div.wiki > ul > li > a.wiki-page
forums div.wiki > ul > li > a.wiki-page
Custom fields div.wiki > ul > li > a.wiki-page
SCM integration div.wiki > ul > li > a.wiki-page
Redmine features div#content > div.wiki > p > a.wiki-page
Submission guidelines div#content > div.wiki > p > a.wiki-page
Contribute div#content > div.wiki > p > a.wiki-page
Teams div#content > div.wiki > p > a.wiki-page
Redmine Donors page div#content > div.wiki > p > a.wiki-page
This page lists div#content > div.wiki > p > a.wiki-page
Redmine div#wrapper2 > div#wrapper3 > div#footer > a

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
Latest releases div#main > div#sidebar > div.wiki > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
tbody > tr > td > a tbody > tr > td > a
tbody > tr > td > a tbody > tr > td > a
tbody > tr > td > a tbody > tr > td > 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.

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
5.1.12 (2026-03-16) div#sidebar > div.wiki > p > a.wiki-page
6.0.9 (2026-03-16) div#sidebar > div.wiki > p > a.wiki-page
6.1.2 (2026-03-16) div#sidebar > div.wiki > p > a.wiki-page
User's Guide div#sidebar > div.wiki > p > a.wiki-page
Developer's Guide div#sidebar > div.wiki > p > a.wiki-page
Privacy Policy div#sidebar > div.wiki > p > a.wiki-page
Start page div#sidebar > ul > li > a
Index by title div#sidebar > ul > li > a
Index by date div#sidebar > ul > li > a
Redmine div.wiki > ul.toc > li > a
Features li > ul > li > a
Documentation li > ul > li > a
Online demo li > ul > li > a
Support & getting help li > ul > li > a
Contributing and helping out li > ul > li > a
Who uses Redmine? li > ul > li > a
Redmine books li > ul > li > a
Multiple projects support div.wiki > ul > li > a.wiki-page
Time tracking div.wiki > ul > li > a.wiki-page
Issue creation via email div.wiki > ul > li > a.wiki-page
User's Guide div.wiki > ul > li > a.wiki-page
Developer's Guide div.wiki > ul > li > a.wiki-page
Changelog div.wiki > ul > li > a.wiki-page
Security Advisories div.wiki > ul > li > a.wiki-page
Frequently Asked Questions div.wiki > ul > li > a.wiki-page
HowTos div.wiki > ul > li > a.wiki-page
Plugins div.wiki > ul > li > a.wiki-page
Themes div.wiki > ul > li > a.wiki-page
Logo and Icon div.wiki > ul > li > a.wiki-page
Third Party Tools div.wiki > ul > li > a.wiki-page

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●`[accesskey]` values are unique
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching 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
○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
○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 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.
○`<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.
○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
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
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