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
transcend-cdn.com/cm/fa619274-3c15-4155-bbec-c0cb75733259/ui.js	60.0 s	98.7 KiB
transcend-cdn.com/cm/fa619274-3c15-4155-bbec-c0cb75733259/airgap.js	60.0 s	52.8 KiB
transcend-cdn.com/cm/fa619274-3c15-4155-bbec-c0cb75733259/cm.css	60.0 s	4.2 KiB
js.adsrvr.org/universal_pixel.js	0.0 ms	958 B
1password.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	2819.0 s	826 B
/sti?cb=11566138312063832&shaid=32860&plh=https%3A%2F%2F1...	0.0 ms	470 B

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.

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:115.053 label:Time to first byte subpart:timeToFirstByte] map[duration:2741.139 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-P

nodeLabel: This site uses cookies to store information on your device. Some are essential …

path: 1,HTML,2,DIV,a,#document-fragment,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,P

selector: div.column-content > div > div > p.paragraph

snippet: <p class="paragraph">

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

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.

	URL	Resource Size	Est Savings
div.w-full > div.overflow-hidden > div.w-full > img.w-full `div.w-full > div.overflow-hidden > div.w-full > img.w-full`	/2h488pz7kgfv/4qBihzvaunRR7hoLlihHAF/c0b5918a1552f39947da...	109.1 KiB	107.4 KiB
div.mx-auto > div.w-full > div.w-full > img.w-full `div.mx-auto > div.w-full > div.w-full > img.w-full`	/2h488pz7kgfv/4YXoxMAEHcmqarZJ6ibIjp/9bc1909cd2ea00448bdc...	47.0 KiB	44.2 KiB
SaaS management dashboard showing annual spend, newly discovered applications, … `div.grid > div.group > div.flex > img.w-full`	/2h488pz7kgfv/4USR0K5t7QgedhH2QN8zGF/f0408183fa8732933bb7...	15.8 KiB	12.6 KiB
AI access dashboard showing employees using AI apps and unique secrets accessib… `div.grid > div.group > div.flex > img.w-full`	/2h488pz7kgfv/Sx9JsXUK6juqLX4udCk0A/b26e1717a73b92f63d8b1...	15.7 KiB	12.5 KiB
Password risk exposure dashboard showing weak and reused credentials and items … `div.grid > div.group > div.flex > img.w-full`	/2h488pz7kgfv/7FEVTKyiFHciBRqX5YZGle/ba6f2044c87b91634f5c...	14.6 KiB	11.6 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: 811 ms

URL	Time Spent
www.1password.com/	811 ms
1password.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

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.

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

URL	Transfer Size	Est Savings
/_next/static/css/776567fbd6210af8.css?dpl=dpl_3ETtrf6YZY...	362.8 KiB	357.9 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: 1.7 s 285.0 KiB

URL	Transfer Size	Est Savings
/_next/static/chunks/1380-23d45b7c0830f5df.js?dpl=dpl_3ET...	133.6 KiB	64.2 KiB
/_next/static/chunks/pages/_app-b5117911cac3e570.js?dpl=d...	133.4 KiB	43.9 KiB
transcend-cdn.com/cm/fa619274-3c15-4155-bbec-c0cb75733259/ui.js	98.3 KiB	37.6 KiB
/_next/static/chunks/3171-baaca19acadc507b.js?dpl=dpl_3ET...	60.0 KiB	32.6 KiB
/_next/static/chunks/6563-54aa583b2aa4597d.js?dpl=dpl_3ET...	47.2 KiB	30.9 KiB
/_next/static/chunks/4064-c74433f99dc46b66.js?dpl=dpl_3ET...	60.2 KiB	29.8 KiB
/_next/static/chunks/3447-687e2c50eea3ba65.js?dpl=dpl_3ET...	63.0 KiB	25.5 KiB
transcend-cdn.com/cm/fa619274-3c15-4155-bbec-c0cb75733259/airgap.js	52.4 KiB	20.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	2.4 s	908 ms	0.0 ms
/_next/static/chunks/framework-b9fd9bcc3ecde907.js?dpl=dp...	2.2 s	1.8 s	25 ms
1password.com/	1.5 s	2.0 ms	0.0 ms
/_next/static/chunks/pages/[[...slug]]-e8c27fe4287662cf.j...	446 ms	444 ms	0.6 ms
/_next/static/chunks/bc1a11eb-39d6b105a12c9d8e.js?dpl=dpl...	429 ms	406 ms	22 ms
/_next/static/chunks/3171-baaca19acadc507b.js?dpl=dpl_3ET...	329 ms	188 ms	25 ms
/_next/static/css/776567fbd6210af8.css?dpl=dpl_3ETtrf6YZY...	306 ms	0.0 ms	0.0 ms
transcend-cdn.com/cm/fa619274-3c15-4155-bbec-c0cb75733259/ui.js	292 ms	235 ms	53 ms
1password.com/6si.min.js	283 ms	258 ms	4.7 ms
/_next/static/chunks/pages/_app-b5117911cac3e570.js?dpl=d...	257 ms	175 ms	81 ms
/_next/static/chunks/main-27d7eeb94db5f181.js?dpl=dpl_3ET...	256 ms	204 ms	50 ms
1password.com/gtag-prod.min.js	179 ms	155 ms	22 ms
transcend-cdn.com/cm/fa619274-3c15-4155-bbec-c0cb75733259/airgap.js	145 ms	117 ms	18 ms
1password.com/analytics.bundle.min.js	95 ms	86 ms	8.4 ms
/_next/static/chunks/3447-687e2c50eea3ba65.js?dpl=dpl_3ET...	65 ms	4.7 ms	26 ms
/_next/static/chunks/1380-23d45b7c0830f5df.js?dpl=dpl_3ET...	63 ms	1.9 ms	60 ms
1password.com/vimeo-ga4.js	52 ms	46 ms	5.4 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	5.3 s
Other	2.7 s
Script Parsing & Compilation	497 ms
Style & Layout	496 ms
Parse HTML & CSS	335 ms
Garbage Collection	219 ms
Rendering	71 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

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
unpkg.com/@rive-app/canvas@2.32.0/rive.wasm	524.5 KiB
/_next/static/css/776567fbd6210af8.css?dpl=dpl_3ETtrf6YZY...	365.9 KiB
/2h488pz7kgfv/36SlPIEBpvvdygJXWP3svG/116f0a2688298ecc2134...	287.4 KiB
www.googletagmanager.com/gtag/js?id=G-G2KE51TPE4	176.1 KiB
1password.com/	165.5 KiB
/_next/static/chunks/pages/_app-b5117911cac3e570.js?dpl=d...	136.9 KiB
/_next/static/chunks/1380-23d45b7c0830f5df.js?dpl=dpl_3ET...	136.7 KiB
/2h488pz7kgfv/4qBihzvaunRR7hoLlihHAF/c0b5918a1552f39947da...	109.6 KiB
transcend-cdn.com/cm/fa619274-3c15-4155-bbec-c0cb75733259/ui.js	98.7 KiB
/2h488pz7kgfv/6DYvsGZ8EAyTnjvlAWP5CJ/ce324c243cd19c0d3841...	86.3 KiB

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

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 4 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Network Requests

●Network Round Trip Times 180 ms

●Server Backend Latencies 260 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

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

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Downloads `div.flex > div.bg-transparent > div > div.mb-3`
1Password products `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Features `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Solutions `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Resources `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Developers `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Support `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Company `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Partners `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Downloads `div.bg-transparent > div > div.mb-3 > h6.flex-[0_1_0%]`

These are opportunities to improve keyboard navigation in your application.

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

●ARIA input fields have accessible names

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

○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

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

Source	Description
1password.com/	Loading the image 'https://pixel.rubiconproject.com/tap.php?v=8981&nid=2307&put=fc3a5563-5d44-476a-9862-b93bc8fba613&gdpr=0&gdpr_consent=&expires=30&next=https%3A%2F%2Fmatch.adsrvr.org%2Ftrack%2Fcmf%2Frubicon' violates the following Content Security Policy directive: "img-src 'self' blob: https://images.ctfassets.net:* https://www.google.com https://www.google-analytics.com https://sst.1passwordservices.com https://cm.g.doubleclick.net https://stats.g.doubleclick.net https://insight.adsrvr.org https://px.mountain.com https://b.6sc.co https://px.ads.linkedin.com/". The action has been blocked.

1password.com/

Loading the image 'https://pixel.rubiconproject.com/tap.php?v=8981&nid=2307&put=fc3a5563-5d44-476a-9862-b93bc8fba613&gdpr=0&gdpr_consent=&expires=30&next=https%3A%2F%2Fmatch.adsrvr.org%2Ftrack%2Fcmf%2Frubicon' violates the following Content Security Policy directive: "img-src 'self' blob: https://images.ctfassets.net:* https://www.google.com https://www.google-analytics.com https://sst.1passwordservices.com https://cm.g.doubleclick.net https://stats.g.doubleclick.net https://insight.adsrvr.org https://px.mountain.com https://b.6sc.co https://px.ads.linkedin.com/". The action has been blocked.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

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/pages/_app-b5117911cac3e570.js?dpl=d...

●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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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`