Skip to content
https://www.jenkins.io

Lighthouse Mobile

· 0 checks — Mobile 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.

71

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.jenkins.io/images/post-images/2025/07/24/redesigning-jenkins-part-two.png172800.0 s895.0 KiB
www.jenkins.io/images/post-images/2025/06/Jenkins-2025-CDF-Awards.png172800.0 s319.9 KiB
www.jenkins.io/images/post-images/2026/04/02/redesigned-credentials-plugin.png172800.0 s304.3 KiB
www.jenkins.io/images/post-images/2026/04/plugin_of_the_month_april.png172800.0 s190.1 KiB
www.jenkins.io/images/post-images/2025/12/yeswehack-jenkins.jpg172800.0 s96.4 KiB
/images/post-images/2025/01/22/2025-01-22-devops-dozen-20...172800.0 s93.2 KiB
/u/155388736?u=55db0be9d035475d94636dc312ead3848aa650d7&v=4300.0 s24.2 KiB
www.jenkins.io/images/cdf/cdf-background-wide.jpg172800.0 s72.2 KiB
www.jenkins.io/images/avatars/stefan_spieker.png172800.0 s60.2 KiB
i.ytimg.com/vi_webp/_MXtbjwsz3A/sddefault.webp7200.0 s17.6 KiB
www.jenkins.io/images/avatars/krisstern.png172800.0 s42.6 KiB
www.jenkins.io/assets/bower/bootstrap/css/bootstrap.min.css172800.0 s42.1 KiB
www.jenkins.io/assets/bower/jquery/jquery.min.js172800.0 s35.6 KiB
www.jenkins.io/images/logos/needs-you/Jenkins_Needs_You-transparent.png172800.0 s34.0 KiB
www.jenkins.io/images/post-images/2026/04/06/jenkins-as-one-of-best-ci-tools.png172800.0 s27.6 KiB
www.jenkins.io/images/logos/jenkins/jenkins.png172800.0 s23.3 KiB
www.jenkins.io/assets/bower/bootstrap/js/bootstrap.min.js172800.0 s20.2 KiB
www.jenkins.io/stylesheets/styles.css172800.0 s16.7 KiB
www.jenkins.io/images/post-images/jenkins-is-the-way/jenkins-is-the-way.png172800.0 s13.3 KiB
cdn.jsdelivr.net/npm/@docsearch/js@3604800.0 s35.7 KiB
www.jenkins.io/images/logos/jenkins/jenkins.svg172800.0 s10.4 KiB
mirrors.creativecommons.org/presskit/buttons/88x31/svg/by-sa.svg43200.0 s6.1 KiB
www.jenkins.io/css/jenkins.css172800.0 s9.1 KiB
cdn.jsdelivr.net/npm/@jenkinsci/jenkins-io-components/+esm604800.0 s26.0 KiB
www.jenkins.io/assets/bower/@popperjs/core/umd/popper.min.js172800.0 s8.1 KiB
www.jenkins.io/css/font-awesome.min.css172800.0 s7.0 KiB
www.jenkins.io/assets/bower/anchor-js/anchor.min.js172800.0 s2.7 KiB
static.doubleclick.net/instream/ad_status.js900.0 s495 B
www.jenkins.io/js/copy-to-clipboard.js172800.0 s1.4 KiB
cdn.jsdelivr.net/npm/@docsearch/css@3604800.0 s3.7 KiB
www.jenkins.io/css/copy-to-clipboard.css172800.0 s854 B
www.jenkins.io/css/footer.css172800.0 s410 B

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.

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
div.row > div.col-md-12 > a > img div.row > div.col-md-12 > a > img
www.jenkins.io/images/post-images/2025/07/24/redesigning-jenkins-part-two.png894.5 KiB871.3 KiB
Redesigned Credentials in Jenkins li.app-card > a > div.app-card__preview > img
www.jenkins.io/images/post-images/2026/04/02/redesigned-credentials-plugin.png304.0 KiB245.2 KiB
Plugin of the Month – April 2026: Pipeline Graph View li.app-card > a > div.app-card__preview > img
www.jenkins.io/images/post-images/2026/04/plugin_of_the_month_april.png189.9 KiB130.4 KiB
Stefan Spieker div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image
www.jenkins.io/images/avatars/stefan_spieker.png60.1 KiB59.7 KiB
Kris Stern div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image
www.jenkins.io/images/avatars/krisstern.png42.5 KiB42.1 KiB
JetBrains Report Highlights Jenkins as a Popular CI/CD Tool in 2026 li.app-card > a > div.app-card__preview > img
www.jenkins.io/images/post-images/2026/04/06/jenkins-as-one-of-best-ci-tools.png27.5 KiB12.7 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: div.container > div.row > div.col-md-5 > img
path: 1,HTML,1,BODY,3,DIV,1,DIV,1,DIV,1,DIV,0,IMG
selector: div.container > div.row > div.col-md-5 > img
snippet: <img src="/images/logos/jenkins/jenkins.svg" style="width: 256px;">

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.1 KiB
URLTransfer SizeEst Savings
www.jenkins.io/css/jenkins.css9.1 KiB2.1 KiB

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: 0.0 ms 29.6 KiB
URLTransfer SizeEst Savings
cdn.jsdelivr.net/npm/@docsearch/js@335.5 KiB29.6 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
div.row > div.col-md-12 > a > img div.row > div.col-md-12 > a > img
www.jenkins.io/images/post-images/2025/07/24/redesigning-jenkins-part-two.png
Stefan Spieker div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image
www.jenkins.io/images/avatars/stefan_spieker.png
Stefan Spieker div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image
www.jenkins.io/images/avatars/stefan_spieker.png
Stefan Spieker div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image
www.jenkins.io/images/avatars/stefan_spieker.png
Stefan Spieker div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image
www.jenkins.io/images/avatars/stefan_spieker.png
Stefan Spieker div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image
www.jenkins.io/images/avatars/stefan_spieker.png
Kris Stern div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image
www.jenkins.io/images/avatars/krisstern.png
div.container > div.row > div.col-md-5 > img div.container > div.row > div.col-md-5 > img
www.jenkins.io/images/logos/jenkins/jenkins.svg
Jan Faracik div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image
Tim Jacomb div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image
Jan Faracik div.app-card__details__authors > a.app-author-link > div.app-avatar > img.app-avatar__image

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

●Max Potential First Input Delay 130 ms
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Reduce unused CSS
●JavaScript execution time 0.3 s
●Minimizes main-thread work 1.3 s
●Avoid long main-thread tasks 3 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 60 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 0 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
71

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button.active div#ProjectCarousel_590 > div.container > div.carousel-indicators > button.active
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.row > div.col-md-5 > img div.container > div.row > div.col-md-5 > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.section > div.video > iframe div.container > div.section > div.video > iframe

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
div.container > div.row > div.col-md-12 > a div.container > div.row > div.col-md-12 > a
div.sponsors > ul > li > a div.sponsors > ul > li > a
div.sponsors > ul > li > a div.sponsors > ul > li > a
div.sponsors > ul > li > a div.sponsors > ul > li > a
div.sponsors > ul > li > a div.sponsors > ul > li > a
div.sponsors > ul > li > a div.sponsors > ul > li > 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.

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
Download div.row > div.col-md-5 > div > a.app-button
Atlassian div.supporters > ul > li > a
Datadog div.supporters > ul > li > a
DigitalOcean div.supporters > ul > li > a
Discourse div.supporters > ul > li > a
Fastly div.supporters > ul > li > a
IBM div.supporters > ul > li > a
Netlify div.supporters > ul > li > a
PagerDuty div.supporters > ul > li > a
Sentry div.supporters > ul > li > a
Tsinghua University div.supporters > ul > li > a
XMission div.supporters > ul > li > a
Belnet div.supporters > ul > li > a
RWTH Aachen University div.supporters > ul > li > a
Hostico div.supporters > ul > li > a
FreeDif div.supporters > ul > li > a
Servana div.supporters > ul > li > a
Yamagata University div.supporters > ul > li > a
ProthamD div.contributor-data > div.desc-div > p > a
contributor-spotlight div.contributor-data > div.desc-div > p > 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
Continuous Integration and Continuous Delivery div.row > div.col-md-6 > div.box > h5
Plugin of the Month – April 2026: Pipeline Graph View ul.app-cards > li.app-card > a > h5.app-card__title

These are opportunities to improve keyboard navigation in your application.

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
Plugins div.div-mar > ul.resources > li > a
Security div.div-mar > ul.resources > li > a
Roadmap div.div-mar > ul.project > li > a
GitHub div.div-mar > ul.project > li > a
Forum div.div-mar > ul.community > li > a
Events div.div-mar > ul.community > li > a
LinkedIn div.div-mar > ul.community > li > a
Bluesky div.div-mar > ul.community > li > a
Mastodon div.div-mar > ul.community > li > a
Youtube div.div-mar > ul.community > li > a
Reddit div.div-mar > ul.community > li > a
Artwork div.div-mar > ul.other > li > a
Awards div.div-mar > ul.other > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.hydrated html.hydrated

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
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
○`[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
○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
○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
○`<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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Identical links have the same purpose.
○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
●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
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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.row > div.col-md-5 > img div.container > div.row > div.col-md-5 > img

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
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback