Lighthouse Mobile

· 0 checks — Mobile 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
/defaultpreferencemanager/deferredjs/E657C59F77C9120AD964...	0.0 ms	129.7 KiB
/defaultpreferencemanager/E657C59F77C9120AD9647EAA88C9573...	0.0 ms	24.6 KiB
www.redhat.com/ux/webdms/css/styles.min.css?tc3usf	86400.0 s	35.9 KiB
/defaultpreferencemanager/deferredjs/E657C59F77C9120AD964...	0.0 ms	12.1 KiB
www.redhat.com/ux/webdms/js/scripts.min.js?tc3usf	86400.0 s	24.3 KiB
consent-pref.trustarc.com/EuPreferenceManager.css	0.0 ms	7.4 KiB
www.redhat.com/akam/13/3ea9008a	21600.0 s	9.5 KiB
/notice?c=teconsent&pcookie&domain=redhat.com&gtm=1&js=nj...	3600.0 s	6.6 KiB
consent-st.trustarc.com/get?name=combined_static_cm_minified.js	0.0 ms	4.8 KiB
/c5eace8ae526/2bebe8987836/e6d73531ade7/RC3cf4ccee79674ce...	3600.0 s	4.5 KiB
static.redhat.com/libs/@redhat/marketing/latest/rh.mktg.js	86400.0 s	7.6 KiB
consent-pref.trustarc.com/images/loading.gif	0.0 ms	3.0 KiB
/defaultpreferencemanager/deferredjs/E657C59F77C9120AD964...	0.0 ms	2.7 KiB
static.redhat.com/libs/redhat/marketing/latest/trustarc/trustecm/js/trustecm.js	86400.0 s	5.7 KiB
www.redhat.com/ux/webdms/js/vendors/jquery.waypoints.min.js?tc3usf	18053.0 s	3.3 KiB
static.redhat.com/libs/redhat/marketing/latest/trustarc/trustarc.js	86400.0 s	2.5 KiB
consent-pref.trustarc.com/images/gpc-check.svg	0.0 ms	950 B
/defaultpreferencemanager/deferredjs/E657C59F77C9120AD964...	0.0 ms	912 B
/modules/contrib/red_hat_shared_libs/dist/rhds-elements/4...	136209.0 s	2.0 KiB
/c5eace8ae526/2bebe8987836/e6d73531ade7/RC43376b731ddd46c...	3600.0 s	828 B
www.redhat.com/ux/dx-web/css/projects/ansible-nav-footer.min.css?tc3usf	12642.0 s	891 B
www.redhat.com/ux/webdms/css/projects/topic-article.min.css?tc3usf	86400.0 s	1.4 KiB
/libs/redhat/marketing/latest/trustarc/trustecm/css/trust...	86400.0 s	1.4 KiB
www.redhat.com/ux/webdms/js/projects/topic-article.min.js?tc3usf	86400.0 s	1.1 KiB
/modules/contrib/red_hat_shared_libs/dist/rhds-elements/4...	52532.0 s	631 B
/rhdc/system-files/js/js_yIup-YxMYLSWqTpsnbT8Z6ZTG-aXzCP-...	818239.0 s	2.2 KiB
/modules/contrib/red_hat_shared_libs/dist/rhds-elements/4...	255233.0 s	520 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.122887] map[node:map[boundingRect:map[bottom:823 height:281 left:0 right:412 top:542 width:412] lhId:page-1-DIV nodeLabel:Your choices regarding the use of cookies on this site path:1,HTML,1,BODY,19,DIV,0,DIV selector:body.updated > div#pop-outerdiv02966567197286867 > div#pop-div204118946187821535 snippet:<div id="pop-div204118946187821535" class="truste_box_overlay"> type:node] score:0.122887 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:3330 height:107 left:31 right:381 top:3224 width:350] lhId:page-2-IMG nodeLabel:Red Hat Ansible Automation Platform logo path:1,HTML,1,BODY,1,DIV,0,ARTICLE,0,DIV,8,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,2,DIV,0,DIV,1,DIV,0,P,0,A,0,IMG selector:div.rh-generic--component > p > a > img snippet:<img alt="Red Hat Ansible Automation Platform logo" src="https://www.redhat.com/rhdc/managed-files/Logo-Red_Hat-Ansible_Automation_…" width="350px" loading="lazy"> type:node]]] type:subitems]]]

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.

URL	Est Savings
consent.trustarc.com/get?name=RedHatText-Regular.ttf	70 ms
consent.trustarc.com/get?name=RedHatDisplay-Medium.ttf	40 ms

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:381.011 label:Time to first byte subpart:timeToFirstByte] map[duration:2191.004 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-P

nodeLabel: Welcome to the Ansible® Collaborative, a destination for Ansible users, custome…

path: 1,HTML,1,BODY,1,DIV,0,ARTICLE,0,DIV,3,SECTION,0,DIV,1,DIV,0,DIV,0,DIV,2,DIV,0,DIV,3,DIV,1,P

selector: div.rh-group--layout > div.rh-group-body > div.rh-generic--component > p

snippet: <p>

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

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
www.redhat.com/ux/webdms/css/projects/osh-stack.min.css?tc3usf	0 B
/rhdc/system-files/css/css_UyPuXH-0K8GsIQjmf0HT6OiyXghLzW...	4.2 KiB	150 ms
/rhdc/system-files/css/css_IsPKZpLA_nD-nMI-6Bgp7DFLiyIJVv...	6.6 KiB
www.redhat.com/ux/webdms/css/styles.min.css?tc3usf	35.9 KiB	450 ms
/rhdc/system-files/js/js_3EBBi-lqpBgQp15IKX1Ys6Y9R67WCsum...	658 B
www.redhat.com/ux/dx-web/css/projects/ansible-nav-footer.min.css?tc3usf	891 B
www.redhat.com/ux/webdms/css/projects/topic-article.min.css?tc3usf	1.4 KiB
/rhdc/system-files/css/css_YH6UERW8F4IEHHkamiagk76PHHTdII...	17.2 KiB	150 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: 759 ms

URL	Time Spent
www.ansible.com/	759 ms
www.redhat.com/en/ansible-collaborative?intcmp=7015Y000003t7aWQAQ	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
Your choices regarding the use of cookies on this site `body.updated > div#pop-outerdiv02966567197286867 > div#pop-div204118946187821535`	0.123

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 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: 450 ms 50.7 KiB

URL	Transfer Size	Est Savings
www.redhat.com/ux/webdms/css/styles.min.css?tc3usf	35.4 KiB	35.2 KiB
/rhdc/system-files/css/css_YH6UERW8F4IEHHkamiagk76PHHTdII...	16.8 KiB	15.5 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: 150 ms 32.5 KiB

URL	Transfer Size	Est Savings
www.redhat.com/dtm.js	278.2 KiB	32.5 KiB

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	968 ms
Other	581 ms
Script Parsing & Compilation	262 ms
Style & Layout	223 ms
Garbage Collection	81 ms
Parse HTML & CSS	70 ms
Rendering	36 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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
Red Hat Ansible Automation Platform logo `div.rh-generic--component > p > a > img`	/rhdc/managed-files/Logo-Red_Hat-Ansible_Automation_Platf...
Ansible logo `div#ansible-nav-component-container > rh-navigation-secondary#primary-nav-component > a#secondary-nav-logo > img.logo`	redhat.com/rhdc/managed-files/ansible-logo_white.svg
Red Hat `div.dx-col-12 > p.dx-text-12 > a > img.dx-pl-1`	www.redhat.com/rhdc/managed-files/logo-RedHat_white.svg

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

●Optimize DOM size

●Forced reflow

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 995 KiB

●User Timing marks and measures 12 user timings

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 5 long tasks found

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 90 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#pop-outerdiv02966567197286867 > div#pop-div204118946187821535 > div#pop-div308731378467561114 > iframe#pop-frame09927888474996307 `div#pop-outerdiv02966567197286867 > div#pop-div204118946187821535 > div#pop-div308731378467561114 > iframe#pop-frame09927888474996307`

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
A gathering space to build automation skills and success `div.rh-group--layout > div.rh-group-body > div.rh-generic--component > h4`

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
Digital accessibility `div.dx-col-12 > ul.dx-list-none > li.md:dx-inline > a.ansible-footer-link`
Cookie preferences `ul.dx-list-none > li.md:dx-inline > span#teconsent > a#icon-id07416565977803347`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●ARIA attributes are used as specified for the element's role

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

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

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
www.redhat.com/ux/webdms/css/projects/osh-stack.min.css?tc3usf	`Failed to load resource: the server responded with a status of 404 ()`
www.redhat.com/ux/webdms/js/projects/osh-stack.min.js?tc3usf	`Failed to load resource: the server responded with a status of 404 ()`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
www.redhat.com/dtm.js
/modules/contrib/rh_oidc_manager/libraries/dist/js/index....	/modules/contrib/rh_oidc_manager/libraries/dist/js/index....

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

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.

Link destination	Link Text
galaxy.ansible.com/ui/namespaces/middleware_automation/	Learn more
galaxy.ansible.com/ui/repo/published/kubernetes/core/	Learn more
galaxy.ansible.com/ui/repo/published/community/vmware/	Learn more

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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`