Skip to content
https://www.gitpod.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.

50

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.

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.

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: figure.relative > figure.w-full > div.w-full > img.object-cover
path: 1,HTML,1,BODY,5,DIV,1,SECTION,0,DIV,0,FIGURE,0,FIGURE,0,DIV,0,IMG
selector: figure.relative > figure.w-full > div.w-full > img.object-cover
snippet: <img alt="" loading="lazy" decoding="async" data-nimg="fill" class="object-cover absolute inset-0" style="position: absolute; height: 100%; width: 100%; inset: 0px;" sizes="100vw" srcset="/_next/image?url=%2Fimages%2Fcontent%2Fsanity%2Fbe9e51124e0f8ee6db80d47b3e…" src="https://ona.com/_next/image?url=%2Fimages%2Fcontent%2Fsanity%2Fbe9e51124e0…">

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.

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.

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.floating-announcement_pill__sYal_ > a.floating-announcement_pillLink__ZJHXu > span.floating-announcement_iconWrap__lhEGv > img.floating-announcement_iconImage__D3kX5 div.floating-announcement_pill__sYal_ > a.floating-announcement_pillLink__ZJHXu > span.floating-announcement_iconWrap__lhEGv > img.floating-announcement_iconImage__D3kX5
ona.com/images/banner-generic-image.webp8.8 KiB8.7 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: 847 ms
URLTime Spent
www.gitpod.io/847 ms
ona.com/0.0 ms

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.

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.

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.

CategoryTime Spent
Script Evaluation2.5 s
Other1.1 s
Style & Layout358 ms
Script Parsing & Compilation313 ms
Rendering155 ms
Garbage Collection60 ms
Parse HTML & CSS50 ms

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
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 9 user timings
●Avoid long main-thread tasks 15 long tasks found
●Avoid non-composited animations 4 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 120 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
○INP breakdown
○Avoid large layout shifts
86

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.

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
Top 100 global company div.overflow-y-clip > section.container > div.bg-grey-450 > p.text-body-160
productivity increase section.container > div.grid > div.bg-grey-400 > p.text-body-110
of PRs co-authored by Ona section.container > div.grid > div.bg-grey-400 > p.text-body-110
Python repos modernized in 6 months section.container > div.grid > div.bg-grey-400 > p.text-body-110
Compliant, certified, and trusted by Fortune 500 companies. section.container > div.flex > h2.text-[1.125rem] > span.text-grey-700
The adversary can reason now, and our security tools weren't built for that. section.container > div.flex > a.flex > p.text-body-160
Background agents that write, test, and ship code on a schedule. Ona Automation… section.container > div.flex > a.flex > p.text-body-160
The companies winning with background agents didn't start with better models. T… section.container > div.flex > a.flex > p.text-body-160

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > div.flex > div.w-full > input.cursor-pointer div.flex > div.flex > div.w-full > input.cursor-pointer

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
1x div.text-white > div.flex > div.flex > button.flex
Unmute div.text-white > div.flex > div.flex > button.flex
Fullscreen div.text-white > div.flex > div.flex > button.flex
Automations div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Environments div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Governance div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Pricing div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
AI code review div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Code migration div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
CVE remediation div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Standardization div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Devin div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Codex div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Factory div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Blog div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Docs div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Changelog div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Events div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Newsletter div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Templates div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Videos div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Reports div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
About div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Careers div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Media div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Contact div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Status div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Security div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Imprint div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Terms of service div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Terms of use div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Privacy policy div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Cookie policy div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]

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

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.
●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.
●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
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[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
○`<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
○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
○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.
81

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 / WarningSource
AttributionReporting

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.

●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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
100

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.

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

Send Feedback