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.

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.

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

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
mktg.tags.f5.com/main/prod/utag.sync.js	300.0 s	54.6 KiB
mktg.tags.f5.com/main/prod/utag.js	300.0 s	49.5 KiB
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js	600.0 s	25.1 KiB
js.clrt.ai/11186.js	43200.0 s	24.3 KiB
/client/63iw3vww/0/stub.js?disableSelector=true&manuallyS...	600.0 s	11.6 KiB
/notice?domain=f5.com&c=teconsent&js=nj&noticeType=bb&tex...	3600.0 s	13.2 KiB
mktg.tags.f5.com/main/prod/utag.2.js?utv=ut4.48.202512190037	300.0 s	7.5 KiB
de-de-63iw3vww.app.easyling.com/__inject/fix-meta.js	86400.0 s	1.1 KiB
tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=f5/main/202604022110&cb=1776358894018	300.0 s	434 B
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js	600.0 s	0 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.

URL	Est Savings
consent.trustarc.com/get?name=NeusaBold.woff	15 ms
consent.trustarc.com/get?name=proxima-nova-regular.ttf	15 ms
consent.trustarc.com/get?name=proxima-nova-semibold.ttf	10 ms

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
www.f5.com/css/prism.css	1.0 KiB

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

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.

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

URL	Time Spent
nginx.com/	816 ms
www.nginx.com/	991 ms
www.f5.com/products/nginx	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.2 s

URL	Time Spent
www.f5.com/products/nginx	1.3 s

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

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
/_next/static/chunks/549ca77c-9261eb57d3bef9bc.js?dpl=dpl...	1.9 s	751 ms	1.2 s
/_next/static/chunks/1684-c2a4dfbf19bd03d1.js?dpl=dpl_42Z...	1.3 s	1.1 s	41 ms
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js	1.1 s	1.1 s	47 ms
Unattributable	1.1 s	9.7 ms	0.0 ms
www.f5.com/products/nginx	695 ms	29 ms	66 ms
mktg.tags.f5.com/main/prod/utag.js	503 ms	354 ms	28 ms
mktg.tags.f5.com/main/prod/utag.sync.js	230 ms	171 ms	28 ms
consent.trustarc.com/asset/notice.js/v/v1.7-1729	220 ms	161 ms	24 ms
/notice?domain=f5.com&c=teconsent&js=nj&noticeType=bb&tex...	118 ms	82 ms	6.3 ms
mktg.tags.f5.com/main/prod/utag.2.js?utv=ut4.48.202512190037	102 ms	86 ms	4.0 ms
/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl...	74 ms	35 ms	36 ms
/client/63iw3vww/0/stub.js?disableSelector=true&manuallyS...	62 ms	56 ms	4.3 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	4.0 s
Script Parsing & Compilation	1.7 s
Other	1.2 s
Style & Layout	448 ms
Garbage Collection	213 ms
Parse HTML & CSS	157 ms
Rendering	75 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

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 1.7 MiB

URL	Transfer Size	Est Savings
/_next/static/chunks/549ca77c-9261eb57d3bef9bc.js?dpl=dpl...	1.5 MiB	1.5 MiB
mktg.tags.f5.com/main/prod/utag.sync.js	54.2 KiB	41.6 KiB
/_next/static/chunks/8274-5040ec944eb9c798.js?dpl=dpl_42Z...	37.8 KiB	34.0 KiB
mktg.tags.f5.com/main/prod/utag.js	49.0 KiB	28.6 KiB
/_next/static/chunks/3564-1cb1b7fade2873c4.js?dpl=dpl_42Z...	34.6 KiB	27.9 KiB
consent.trustarc.com/asset/notice.js/v/v1.7-1729	36.0 KiB	22.0 KiB

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 2,667 KiB

●Avoid long main-thread tasks 20 long tasks found

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

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 50 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○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

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
Featured `div.container > div.grid > div.space-y-gutter-md > h6.d-supplementary`

These are opportunities to improve keyboard navigation in your application.

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
NGINX One The core NGINX data plane software enhanced with SaaS-based tools for… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
F5 WAF for NGINX and F5 DoS for NGINX Comprehensive WAF security and denial-of-… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINXaaS for Azure An Infrastructure-as-a-Service version of NGINX that enables… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
F5 NGINXaaS for Google Cloud Enhance app delivery and security in Google Cloud … `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINX Plus An all-in-one, cloud-native load balancer, reverse proxy, web server… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
F5 WAF for NGINX A comprehensive WAF security solution designed to protect apps… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINX Instance Manager Identify, secure, manage, and monitor all NGINX Open Sou… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINX Ingress Controller Implements unified API gateways, load balancers, and i… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINX Gateway Fabric Streamlines app, service, and API connectivity across hybr… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINX One Console Configure, secure, monitor and manage NGINX instances at scal… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
2024 TrustRadius Top Rated Award `div.grid-cols-1 > span.w-full > div.h-full > a.group`
Contact us Find out how F5 products and solutions can enable you to achieve you… `div.flex > div.flex > div.w-full > a.group`
Explore packaging options Explore the best options for your organization. Explo… `div.flex > div.flex > div.w-full > a.group`
Try NGINX One for Free Try the NGINX ecosystem with data plane and traffic mana… `div.flex > div.flex > div.w-full > a.group`

○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

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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

○`[accesskey]` values are unique

○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

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

○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

○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

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.

Description
`Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured header parser.`

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
/_next/static/chunks/549ca77c-9261eb57d3bef9bc.js?dpl=dpl...

●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

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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.

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

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