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.

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
/s/chivomono/v11/mFThWbgRxKvF_Z5eQMO9qRMrJJrnKNtC3D7Tr6fQ...	95 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	60 ms

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: div.ssr-variant > div.framer-1hgg02o > div > img

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

selector: div.ssr-variant > div.framer-1hgg02o > div > img

snippet: <img decoding="auto" width="2096" height="1280" sizes="(min-width: 1440px) max(100vw, max((min(100vw - 80px, 1600px) - 64px) / 2,…" srcset="https://framerusercontent.com/images/JdH5nqKOTWIZ4SsZJt5Vjnk2N0.png?scale-…" src="https://framerusercontent.com/images/JdH5nqKOTWIZ4SsZJt5Vjnk2N0.png?scale-…" alt="" style="display: block; width: 100%; height: 100%; border-radius: inherit;">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

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
/vi/77xKTKUQAPQ/sddefault.jpg?sqp=-oaymwEmCIAFEOAD8quKqQM...	7200.0 s	17.6 KiB
scripts.clarity.ms/0.8.62/clarity.js	86400.0 s	25.1 KiB
events.framer.com/script?v=2	300.0 s	8.0 KiB
framer.com/edit/init.mjs	300.0 s	3.6 KiB
framer.com/bootstrap.b3492b4fb5c2d6c935c8cc17894e26a11d669113.js	3600.0 s	1.4 KiB
static.doubleclick.net/instream/ad_status.js	900.0 s	494 B

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.ssr-variant > div.framer-1hgg02o > div > img `div.ssr-variant > div.framer-1hgg02o > div > img`	/images/JdH5nqKOTWIZ4SsZJt5Vjnk2N0.png?scale-down-to=1024...	47.8 KiB	9.5 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: 899 ms

URL	Time Spent
juno-innovations.com/	899 ms
www.juno-innovations.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 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: 880 ms 249.2 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-P7TC28KH	119.0 KiB	64.3 KiB
www.googletagmanager.com/gtag/js?id=G-VJ3J3RJWC1	160.1 KiB	63.8 KiB
framerusercontent.com/sites/7JPG3cTUsWER9OUIqtsk4I/framer.ZZ2YEiGa.mjs	118.0 KiB	63.1 KiB
framerusercontent.com/sites/7JPG3cTUsWER9OUIqtsk4I/script_main.CVPilp0r.mjs	85.5 KiB	33.1 KiB
framerusercontent.com/sites/7JPG3cTUsWER9OUIqtsk4I/motion.CvTipq3W.mjs	48.1 KiB	25.0 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
framerusercontent.com/sites/7JPG3cTUsWER9OUIqtsk4I/motion.CvTipq3W.mjs	1.0 s	548 ms	0.2 ms
framerusercontent.com/sites/7JPG3cTUsWER9OUIqtsk4I/react.Bm4lFkIa.mjs	1.0 s	883 ms	0.2 ms
www.juno-innovations.com/	860 ms	47 ms	10 ms
scripts.clarity.ms/0.8.62/clarity.js	419 ms	362 ms	4.9 ms
Unattributable	391 ms	23 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-VJ3J3RJWC1	285 ms	244 ms	39 ms
www.googletagmanager.com/gtm.js?id=GTM-P7TC28KH	157 ms	134 ms	23 ms
framerusercontent.com/sites/7JPG3cTUsWER9OUIqtsk4I/framer.ZZ2YEiGa.mjs	77 ms	70 ms	1.7 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	2.5 s
Other	965 ms
Style & Layout	730 ms
Rendering	110 ms
Parse HTML & CSS	93 ms
Script Parsing & Compilation	86 ms
Garbage Collection	47 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

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●User Timing marks and measures 35 user timings

●Avoid long main-thread tasks 11 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 100 ms

●Server Backend Latencies 360 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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
GPU Time-Slice Monitor `div.ssr-variant > div > div > span`
NODE / GPU `div.ssr-variant > div > div > span`
USER `div.ssr-variant > div > div > span`
UTILIZATION `div.ssr-variant > div > div > span`
JOB `div.ssr-variant > div > div > span`
GPU 0 `div > div > div > span`
GPU 1 `div > div > div > span`
GPU 2 `div > div > div > span`
GPU 3 `div > div > div > span`
GPU 0 `div > div > div > span`
GPU 1 `div > div > div > span`
GPU 2 `div > div > div > span`
GPU 3 `div > div > div > span`
3 users · 7 GPUs active · 0 queued `div.ssr-variant > div > div > span`
Updated 9s `div.ssr-variant > div > div > span`
* Visualizations represent live cluster state and are illustrative of Orion's o… `main.framer-1k7waej > section#features > div.framer-1pmanse > p.framer-text`
Compute cost reduction `div.framer-1ae6yq8 > div.framer-9zn3fl > div.framer-8lsx3u > p.framer-text`
User request to workload running `div.framer-13uk021 > div.framer-ptb8e3 > div.framer-jz9opv > p.framer-text`
Juno Innovations provides compute orchestration software. Orion is designed for… `footer.framer-OACfa > div.framer-zhixdk > div.framer-w3asg > p.framer-text`

These are opportunities to improve the legibility of your content.

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
Running GPU and CPU workloads has meant choosing between two compromises. `div.framer-n6r9la > div.ssr-variant > div.framer-10l2sa3 > h3.framer-text`
~40% `div.framer-1ae6yq8 > div.framer-1ui2kfd > div.framer-jbawmc > 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-z3PI5 > div.framer-xmz3tp > div.framer-cm1to5 > a.framer-1hzb0g2 `div.framer-z3PI5 > div.framer-xmz3tp > div.framer-cm1to5 > a.framer-1hzb0g2`

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
Terra App Store `div.framer-1h7xzvl > div.framer-1sqrznn > p.framer-text > a.framer-text`
KubeVirt — VM Orchestration `div.framer-1h7xzvl > div.framer-1hcb4z0 > p.framer-text > a.framer-text`
Documentation `div.framer-2y62ma > div.framer-1clg6bi > p.framer-text > a.framer-text`

These items highlight common accessibility best practices.

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
Cookie Settings `div.framer-2pSaX > main.framer-1k7waej > div.framer-bm3mjy-container > button.__framer-cookie-component-button`

○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

●Input buttons have discernible text.

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

●`<frame>` or `<iframe>` elements have a title

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

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

○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
www.juno-innovations.com/	`Access to font at 'https://fonts.gstatic.com/...' from origin 'https://www.juno-innovations.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
fonts.gstatic.com/...	`Failed to load resource: net::ERR_FAILED`

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

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`