https://insightcenter.b2clogin.com/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/authorize?client_id=b1cf1b94-be82-4e12-a3ef-23c9154c772b&scope=https%3A%2F%2Finsightcenter.onmicrosoft.com%2Feservice-api-prd%2Fuser_impersonation%20openid%20profile%20offline_access&redirect_uri=https%3A%2F%2Fservice.stryker.com%2FloginSSO&client-request-id=019eb605-6af2-7793-98db-bf244f7a8554&response_mode=fragment&response_type=code&x-client-SKU=msal.js.browser&x-client-VER=3.30.0&client_info=1&code_challenge=BRub9pEd4Ln2tN_VOD8VCubek0OyYIqUDzff1E1zHMo&code_challenge_method=S256&nonce=019eb605-6af5-7490-9771-b2ecca73ccf4&state=eyJpZCI6IjAxOWViNjA1LTZhZjQtN2ZhZC1iZjQ3LWMzYmE1MmVjYjZiNyIsIm1ldGEiOnsiaW50ZXJhY3Rpb25UeXBlIjoicmVkaXJlY3QifX0%3D

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
js.monitor.azure.com/scripts/b/ai.2.min.js	1800.0 s	46.2 KiB
az416426.vo.msecnd.net/scripts/a/ai.0.js	1800.0 s	21.6 KiB

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
insightcenter.stryker.com/assets/fonts/380F54_2_0.woff2	595 ms
insightcenter.stryker.com/assets/fonts/380F54_0_0.woff2	330 ms
insightcenter.stryker.com/assets/fonts/380F54_1_0.woff2	330 ms
insightcenter.stryker.com/assets/fonts/380F54_2_0.woff2	325 ms
insightcenter.stryker.com/assets/fonts/380F54_2_0.woff	310 ms
insightcenter.stryker.com/assets/fonts/380F54_2_0.woff	310 ms
insightcenter.stryker.com/assets/fonts/380F54_1_0.woff	290 ms
/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/~...	75 ms

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

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

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: 220 ms 36.2 KiB

URL	Transfer Size	Est Savings
/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/a...	67.8 KiB	36.2 KiB

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 the main frame.	Actionable
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

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 26.8 KiB

URL	Transfer Size	Est Savings
/! Bootstrap v4.1.3 (https://getbootstrap.com/) * Copyright 2011-2018 The Bootstrap Authors *…	27.5 KiB	26.8 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.header-body > div.row > div.col > img.app-brand-logo `div.header-body > div.row > div.col > img.app-brand-logo`	insightcenter.stryker.com/assets/images/logo.png

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

●Max Potential First Input Delay 100 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 699 KiB

●JavaScript execution time 0.5 s

●Minimizes main-thread work 1.1 s

●Avoid long main-thread tasks 6 long tasks found

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 280 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 240 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○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

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.header-body > div.row > div.col > img.app-brand-logo `div.header-body > div.row > div.col > img.app-brand-logo`

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
Having issues signing in? `div.col > div.row > div.col > 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 `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>`

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

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

●Buttons have an accessible name

●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

●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

●Heading elements appear in a sequentially-descending order

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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 have all required `[aria-*]` attributes

○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

○`[role]` values are valid

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

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○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

○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.	js.monitor.azure.com/scripts/b/ai.2.min.js line 4, col 20534

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
/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/a...	`Access to font at 'https://insightcenter.stryker.com/assets/fonts/380F54_0_0.woff2' from origin 'https://insightcenter.b2clogin.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/a...	`Access to font at 'https://insightcenter.stryker.com/assets/fonts/380F54_1_0.woff' from origin 'https://insightcenter.b2clogin.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/a...	`Access to font at 'https://insightcenter.stryker.com/assets/fonts/380F54_1_0.woff2' from origin 'https://insightcenter.b2clogin.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/a...	`Access to font at 'https://insightcenter.stryker.com/assets/fonts/380F54_2_0.woff' from origin 'https://insightcenter.b2clogin.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/a...	`Access to font at 'https://insightcenter.stryker.com/assets/fonts/380F54_2_0.woff' from origin 'https://insightcenter.b2clogin.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/a...	`Access to font at 'https://insightcenter.stryker.com/assets/fonts/380F54_2_0.woff2' from origin 'https://insightcenter.b2clogin.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/a...	`Access to font at 'https://insightcenter.stryker.com/assets/fonts/380F54_2_0.woff2' from origin 'https://insightcenter.b2clogin.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
insightcenter.stryker.com/assets/fonts/380F54_2_0.woff2	`Failed to load resource: net::ERR_FAILED`
insightcenter.stryker.com/assets/fonts/380F54_0_0.woff2	`Failed to load resource: net::ERR_FAILED`
insightcenter.stryker.com/assets/fonts/380F54_1_0.woff2	`Failed to load resource: net::ERR_FAILED`
insightcenter.stryker.com/assets/fonts/380F54_2_0.woff2	`Failed to load resource: net::ERR_FAILED`
insightcenter.stryker.com/assets/fonts/380F54_1_0.woff	`Failed to load resource: net::ERR_FAILED`
insightcenter.stryker.com/assets/fonts/380F54_2_0.woff	`Failed to load resource: net::ERR_FAILED`
insightcenter.stryker.com/assets/fonts/380F54_2_0.woff	`Failed to load resource: net::ERR_FAILED`
/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/~...	`Failed to load resource: the server responded with a status of 404 (Not Found)`
az416426.vo.msecnd.net/scripts/a/ai.0.js	`Uncaught [object Object]`
az416426.vo.msecnd.net/scripts/a/ai.0.js	`Uncaught [object Object]`

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

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.header-body > div.row > div.col > img.app-brand-logo `div.header-body > div.row > div.col > img.app-brand-logo`

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
What is this? `ul > li.TextBox > div.attrEntry > a.helpLink`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`