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
element.atl30309.com/fonts/inter-latin-600-normal.69a8d1d.woff2	0.0 ms	24.1 KiB
element.atl30309.com/fonts/inter-latin-400-normal.eca1e21.woff2	0.0 ms	23.3 KiB
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/mobileguide.css	0.0 ms	13.7 KiB
element.atl30309.com/mobile_guide/assets/app-store-badge.svg	0.0 ms	4.1 KiB
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/mobileguide.js	0.0 ms	3.9 KiB
element.atl30309.com/mobile_guide/assets/google-play-badge.svg	0.0 ms	3.2 KiB
element.atl30309.com/mobile_guide/assets/element-logo.svg	0.0 ms	2.4 KiB
element.atl30309.com/mobile_guide/assets/bottom-gradient.275f51c.svg	0.0 ms	1.1 KiB

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

nodeLabel: body > footer > div.mx_BottomGradient

path: 2,HTML,1,BODY,2,FOOTER,0,DIV

selector: body > footer > div.mx_BottomGradient

snippet: <div class="mx_BottomGradient">

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

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
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/mobileguide.css	13.7 KiB	164 ms

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

URL	Time Spent
atl30309.com/	777 ms
element.atl30309.com/	3.0 s
element.atl30309.com/mobile_guide/	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.

Estimated savings: 6.5 s 1.3 MiB

URL	Transfer Size	Est Savings
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/9544.js	845.8 KiB	727.5 KiB
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js	519.9 KiB	456.7 KiB
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/3264.js	100.4 KiB	67.0 KiB
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/8996.js	57.8 KiB	45.3 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
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/9544.js	1.5 s	911 ms	597 ms
Unattributable	630 ms	23 ms	0.0 ms
element.atl30309.com/mobile_guide/	454 ms	7.5 ms	1.2 ms
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js	400 ms	8.1 ms	379 ms
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/bundle.js	157 ms	120 ms	6.1 ms
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/3264.js	146 ms	3.4 ms	142 ms
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/8996.js	72 ms	2.6 ms	69 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 Parsing & Compilation	1.2 s
Script Evaluation	1.1 s
Other	661 ms
Style & Layout	412 ms
Parse HTML & CSS	50 ms
Rendering	31 ms
Garbage Collection	21 ms

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●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,058 KiB

●Avoid long main-thread tasks 9 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

100

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.

○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-hidden="true"]` is not present on the document `<body>`

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

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

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

○Buttons have an accessible name

○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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○Elements with visible text labels have matching accessible names.

○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

Browser Compatibility

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
element.atl30309.com/favicon.ico	`Failed to load resource: the server responded with a status of 404 ()`
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js	ReferenceError: Cannot access 'B' before initialization at Object.J (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:61221) at l.start (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1260383) at d.start (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1238231) at https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1427189 at ./src/stores/widgets/WidgetMessagingStore.ts (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1427200) at a (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/bundle.js:2:16556) at ./src/stores/ActiveWidgetStore.ts (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1234791) at a (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/bundle.js:2:16556) at ./src/stores/WidgetStore.ts (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1264951) at a (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/bundle.js:2:16556)
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js	ReferenceError: Cannot access 'B' before initialization at Object.J (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:61221) at l.start (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1260383) at h.start (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1238231) at https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1268151 at ./src/stores/WidgetStore.ts (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1268162) at a (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/bundle.js:2:16556) at ./src/modules/ModuleRunner.ts (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1117161) at a (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/bundle.js:2:16556) at ./src/SecurityManager.ts (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:119887) at a (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/bundle.js:2:16556)
element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js	ReferenceError: Cannot access 'B' before initialization at Object.J (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:61221) at y.start (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1260383) at get instance (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1375510) at ./src/stores/widgets/WidgetLayoutStore.ts (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1383476) at a (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/bundle.js:2:16556) at ./src/utils/WidgetUtils.ts (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1484617) at a (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/bundle.js:2:16556) at ./src/stores/ActiveWidgetStore.ts (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1234757) at a (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/bundle.js:2:16556) at ./src/stores/WidgetStore.ts (https://element.atl30309.com/bundles/a87b303cdb1da5ea6d71/init.js:1:1264951)

●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

●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

●Page has valid source maps

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`