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.

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
framerusercontent.com/assets/JEdA86oNqHX1i1CLD92Q7jTxV8.woff2	60 ms
fonts.gstatic.com/s/geistmono/v4/or3nQ6H-1_WfwkMZI_qYFrcdmg.woff2	60 ms

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.framer-2l5ilk > div.framer-1oadk8c-container > div > div `div.framer-2l5ilk > div.framer-1oadk8c-container > div > div`	framerusercontent.com/images/g0QcWrxr87K0ufOxIUFBakwYA8.png	117.2 KiB	91.1 KiB
image of Alex `div.framer-1q7n0h8 > div.framer-10klwk5 > div > img`	/images/x9BRSBloqqpsuFkdeQOAqrjsjWc.jpg?scale-down-to=512...	39.2 KiB	38.9 KiB
image of Luca `div.framer-1q7n0h8 > div.framer-10klwk5 > div > img`	/images/hgXzehpOz3L4ttPpPndrMIXqgvs.jpg?scale-down-to=512...	31.1 KiB	31.0 KiB
image of Maya `div.framer-1q7n0h8 > div.framer-10klwk5 > div > img`	/images/J1suVARxyNDnlvwxo92RWn1pGw.jpg?scale-down-to=512&...	25.4 KiB	25.3 KiB
image of James `div.framer-1q7n0h8 > div.framer-10klwk5 > div > img`	/images/N0Whl1787fQpv7Szbn5o8lCuWU.jpg?scale-down-to=512&...	24.5 KiB	24.3 KiB
image of Sarah `div.framer-1q7n0h8 > div.framer-10klwk5 > div > img`	/images/HFc0wt3UAqZImsGznWHCPSjVI8.jpg?scale-down-to=512&...	17.0 KiB	16.8 KiB
image of Nia `div.framer-1q7n0h8 > div.framer-10klwk5 > div > img`	/images/GssuinUQXd1zqlweWZJeKjYHVU.jpg?scale-down-to=512&...	14.2 KiB	14.2 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: div.framer-2l5ilk > div.framer-1oadk8c-container > div > div

path: 3,HTML,1,BODY,3,DIV,3,DIV,2,DIV,0,MAIN,0,SECTION,1,DIV,2,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,1,DIV,1,DIV

selector: div.framer-2l5ilk > div.framer-1oadk8c-container > div > div

snippet: <div style="position: absolute; inset: 0px; background-image: url("https://framerusercontent.…");">

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
t.contentsquare.net/uxa/49b01a0009cbb.js	0.0 ms	127.6 KiB
events.framer.com/script?v=2	300.0 s	8.0 KiB
framer.com/edit/init.mjs	300.0 s	3.6 KiB

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

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

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
framerusercontent.com/sites/6iRDEeF0Z6KaPD1c5Mix9g/react.CvwZcBQj.mjs	12.8 s	2.3 s	0.2 ms
framerusercontent.com/sites/6iRDEeF0Z6KaPD1c5Mix9g/S73kH8mB9.BLmFSsx6.mjs	7.6 s	56 ms	0.1 ms
tocstudio.co/	1.4 s	32 ms	8.4 ms
framerusercontent.com/sites/6iRDEeF0Z6KaPD1c5Mix9g/motion.CFwufept.mjs	818 ms	63 ms	0.2 ms
Unattributable	669 ms	159 ms	0.0 ms
t.contentsquare.net/uxa/49b01a0009cbb.js	623 ms	533 ms	37 ms
framerusercontent.com/sites/6iRDEeF0Z6KaPD1c5Mix9g/b9YkMtvvF.CW1Sbt5S.mjs	553 ms	138 ms	0.5 ms
framerusercontent.com/sites/6iRDEeF0Z6KaPD1c5Mix9g/Dither_Archive.Ck280ZQO.mjs	375 ms	369 ms	0.1 ms
www.googletagmanager.com/gtag/js?id=G-JRPRN62PGF	302 ms	262 ms	33 ms
framerusercontent.com/sites/6iRDEeF0Z6KaPD1c5Mix9g/framer.B6aMYipu.mjs	93 ms	84 ms	1.9 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
Other	18.9 s
Script Evaluation	4.0 s
Style & Layout	1.4 s
Rendering	681 ms
Parse HTML & CSS	117 ms
Garbage Collection	99 ms
Script Parsing & Compilation	87 ms

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

URL	Transfer Size	Est Savings
t.contentsquare.net/uxa/49b01a0009cbb.js	127.1 KiB	69.7 KiB
www.googletagmanager.com/gtag/js?id=G-JRPRN62PGF	156.8 KiB	66.2 KiB
framerusercontent.com/sites/6iRDEeF0Z6KaPD1c5Mix9g/framer.B6aMYipu.mjs	126.7 KiB	64.3 KiB
framerusercontent.com/sites/6iRDEeF0Z6KaPD1c5Mix9g/motion.CFwufept.mjs	48.2 KiB	27.6 KiB

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,375 KiB

●User Timing marks and measures 34 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 50 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 350 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 20 ms

○INP breakdown

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

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
Websites designed for B2B service companies that want to be taken seriously onl… `div.framer-utgkb0 > div.framer-xbqly6 > div#lightning-fast-sites-in-a-single-click-1654kat > h3.framer-text`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.framer-13233yh > div.ssr-variant > div.framer-ly05gp-container > a.framer-yy7Ux `div.framer-13233yh > div.ssr-variant > div.framer-ly05gp-container > a.framer-yy7Ux`
div.framer-evmzau > div.ssr-variant > div.framer-sxmsc9-container > a.framer-yy7Ux `div.framer-evmzau > div.ssr-variant > div.framer-sxmsc9-container > a.framer-yy7Ux`

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.

○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

●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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○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

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

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

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

100

Best Practices

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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

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
Logo Container `div.framer-1uamf99 > div.framer-9ndkvo > div.framer-cyg0jp-container > a.framer-L6N2M`

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

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`