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
assets.ot.digital/fonts/Inter-roman.var.woff2?v=3.19	10800.0 s	222.2 KiB
app.gatedcontent.com/scripts/25583474/app.js	1800.0 s	65.0 KiB
cdn.cookielaw.org/scripttemplates/202510.2.0/otBannerSdk.js	86400.0 s	124.1 KiB
secure.marketinghub.opentext.com/es/1955/c/0/u/optimostSetup.js	3600.0 s	22.9 KiB
app.gatedcontent.com/styles/25583474/app.css	86400.0 s	15.2 KiB
s.go-mpulse.net/boomerang/ZHN4T-KPGPJ-F8GJF-7KJFE-XJT75	604800.0 s	56.8 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
www.opentext.com/assets/scripts/customScripts.js	604800.0 s	3.7 KiB
www.opentext.com/assets/css/inter.css	604800.0 s	1.9 KiB

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.

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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.

URL	Transfer Size	Duration
assets.ot.digital/min/m/v1/js/opentext.min.js	89.4 KiB	2.0 s
assets.ot.digital/min/m/v1/css/opentext.min.css	69.9 KiB	1.8 s
assets.ot.digital/min/m/v1/js/language-alert.min.js	4.3 KiB	893 ms
assets.ot.digital/min/m/v1/js/gtm-alert.min.js	1.3 KiB	732 ms
secure.marketinghub.opentext.com/es/1955/c/0/u/optimostSetup.js	22.9 KiB	1.3 s
www.opentext.com/assets/scripts/customScripts.js	3.7 KiB
www.opentext.com/assets/css/inter.css	1.9 KiB

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: 2.3 s

URL	Time Spent
microfocus.com/	1.3 s
www.microfocus.com/	852 ms
www.microfocus.com/en-us/home	150 ms
www.opentext.com/about/brands/microfocus	0.0 ms

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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 24.7 KiB

URL	Transfer Size	Est Savings
inline: // Copyright 2022 The Chromium Authors …	55.4 KiB	21.8 KiB
secure.marketinghub.opentext.com/es/1955/c/0/u/optimostSetup.js	22.6 KiB	2.8 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: 150 ms 82.0 KiB

URL	Transfer Size	Est Savings
assets.ot.digital/min/m/v1/css/opentext.min.css	69.6 KiB	67.2 KiB
app.gatedcontent.com/styles/25583474/app.css	14.8 KiB	14.8 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: 20 ms 336.1 KiB

URL	Transfer Size	Est Savings
cdn.cookielaw.org/scripttemplates/202510.2.0/otBannerSdk.js	124.0 KiB	75.2 KiB
assets.ot.digital/min/m/v1/js/opentext.min.js	89.2 KiB	59.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-TBD3JCM	149.4 KiB	58.0 KiB
www.googletagmanager.com/gtag/js?id=G-8LWPJ50ZXY&cx=c&gtm=4e64k1	179.4 KiB	52.5 KiB
chromewebdata/	55.4 KiB	39.3 KiB
app.gatedcontent.com/scripts/25583474/app.js	64.2 KiB	26.4 KiB
s.go-mpulse.net/boomerang/ZHN4T-KPGPJ-F8GJF-7KJFE-XJT75	56.6 KiB	25.4 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	770 ms	114 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-8LWPJ50ZXY&cx=c&gtm=4e64k1	722 ms	635 ms	75 ms
www.googletagmanager.com/gtm.js?id=GTM-TBD3JCM	620 ms	496 ms	73 ms
app.gatedcontent.com/scripts/25583474/app.js	610 ms	291 ms	35 ms
assets.ot.digital/min/m/v1/js/opentext.min.js	547 ms	434 ms	56 ms
www.opentext.com/about/brands/microfocus	498 ms	61 ms	7.9 ms
s.go-mpulse.net/boomerang/ZHN4T-KPGPJ-F8GJF-7KJFE-XJT75	287 ms	208 ms	42 ms
cdn.cookielaw.org/scripttemplates/202510.2.0/otBannerSdk.js	185 ms	90 ms	68 ms
j.6sc.co/6si.min.js	170 ms	136 ms	9.4 ms
chromewebdata/	110 ms	32 ms	39 ms
secure.marketinghub.opentext.com/es/1955/c/0/u/optimostSetup.js	105 ms	70 ms	14 ms
assets.ot.digital/min/m/v1/css/opentext.min.css	74 ms	0.0 ms	0.0 ms
app.gatedcontent.com/assets/js/countries.js	58 ms	24 ms	32 ms

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	3.1 s
Other	963 ms
Script Parsing & Compilation	463 ms
Parse HTML & CSS	454 ms
Style & Layout	216 ms
Garbage Collection	98 ms
Rendering	35 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
The page has an unload handler in a sub frame.	Actionable

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 1,226 KiB

●User Timing marks and measures 11 user timings

●Avoid long main-thread tasks 20 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 190 ms

●Server Backend Latencies 510 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

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.ot-sitenav-new__inner > nav.sitenav-right > div.sitenav-login-dropdown > button#sitenav-login-button `div.ot-sitenav-new__inner > nav.sitenav-right > div.sitenav-login-dropdown > button#sitenav-login-button`

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. 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
OpenText Analytics Cloud `div.row > div.col-md-10 > p > a`
OpenText DevOps Cloud `div.row > div.col-md-10 > p > a`
OpenText Cybersecurity Cloud `div.row > div.col-md-10 > p > a`
OpenText Observability and Service Management Cloud `div.row > div.col-md-10 > p > a`
Portfolio `div.row > div.col-md-10 > p > a`
Products A-Z listing `div.row > div.col-md-10 > p > a`
Product Name Changes. `div.row > div.col-md-10 > p > a`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●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

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

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

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

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

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

○Identical links have the same purpose.

○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

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	s.go-mpulse.net/boomerang/ZHN4T-KPGPJ-F8GJF-7KJFE-XJT75 line 9, col 11504
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.	assets.ot.digital/min/m/v1/js/opentext.min.js line 24, col 119620

●Uses HTTPS

●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

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
www.opentext.com/solutions/enterprise-applications/sap	Learn more
www.opentext.com/solutions/enterprise-applications/microsoft	Learn more
www.opentext.com/solutions/enterprise-applications/salesforce	Learn more
www.opentext.com/partners/opentext-on-amazon-web-services	Learn more
www.opentext.com/partners/opentext-on-google-cloud	Learn more
www.opentext.com/partners/opentext-on-microsoft-azure	Learn more
www.opentext.com/partners/sap	Learn more
www.opentext.com/partners/microsoft	Learn more
www.opentext.com/partners/salesforce	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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes