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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:37.847 source:map[column:183835 line:1 type:source-location url:https://kit.com/_next/static/chunks/framework-a071c7e3156668e1.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:85.626 source:map[type:text value:[unattributed]]] map[reflowTime:1.957 source:map[column:83942 line:0 type:source-location url:https://kit.com/_next/static/chunks/42309-acba324af0a7a98c.js urlProvider:network]] map[reflowTime:1.37 source:map[column:21838 line:0 type:source-location url:https://kit.com/_next/static/chunks/42309-acba324af0a7a98c.js urlProvider:network]] map[reflowTime:35.519 source:map[column:3684 line:0 type:source-location url:https://kit.com/_next/static/chunks/53234-62720af5e422a456.js urlProvider:network]] map[reflowTime:4.442 source:map[column:88599 line:0 type:source-location url:https://kit.com/_next/static/chunks/68563-5ae8d773d8aebd21.js urlProvider:network]] map[reflowTime:1.692 source:map[column:15337 line:0 type:source-location url:https://kit.com/_next/static/chunks/42309-acba324af0a7a98c.js urlProvider:network]]]

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
Nisha Vora `div.hero-image-container > div.shrink-0 > picture > img.object-cover`	/images/pages/home/nisha-vora-kit.jpg?q=75&fm=webp&auto=f...	123.6 KiB	34.8 KiB
Send feature screenshot `div.rounded-xl > div.absolute > picture > img.rounded-xl`	/images/pages/home/product/send-1-mobile.jpg?q=75&fm=webp...	66.0 KiB	22.6 KiB
Ali Abdaal `div.hero-image-container > div.shrink-0 > picture > img.object-cover`	/images/pages/home/ali-abdaal-kit.jpg?q=75&fm=webp&auto=f...	104.3 KiB	16.4 KiB
Anne-Laure Le Cunff `div.hero-image-container > div.shrink-0 > picture > img.object-cover`	/images/pages/home/anne-laure-le-cunff_kit.jpg?q=75&fm=we...	89.1 KiB	14.0 KiB
Matthew McConaughey `div.hero-image-container > div.shrink-0 > picture > img.object-cover`	/images/pages/home/matthew-mcconaughey-kit.jpg?q=75&fm=we...	84.3 KiB	13.3 KiB
Earn feature screenshot `div.rounded-xl > div.absolute > picture > img.rounded-xl`	/images/pages/home/product/earn-1-mobile.jpg?q=75&fm=webp...	37.2 KiB	12.7 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-3-IMG

nodeLabel: Anne-Laure Le Cunff

path: 1,HTML,1,BODY,0,DIV,1,DIV,1,MAIN,0,DIV,1,SECTION,0,DIV,0,DIV,1,DIV,1,DIV,0,PICTURE,1,IMG

selector: div.hero-image-container > div.shrink-0 > picture > img.object-cover

snippet: <img alt="Anne-Laure Le Cunff" loading="lazy" width="476" height="587" decoding="async" data-nimg="1" class="object-cover absolute top-0 left-0 w-full h-full transition-opacity opacit…" style="color:transparent" src="https://media.kit.com/images/pages/home/anne-laure-le-cunff_kit.jpg?q=75&f…">

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
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 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: 1.1 s

URL	Time Spent
www.convertkit.com/	1.1 s
kit.com/	0.0 ms

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.

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: 500 ms 64.1 KiB

URL	Transfer Size	Est Savings
kit.com/_next/static/chunks/framework-a071c7e3156668e1.js	59.5 KiB	22.2 KiB
kit.com/_next/static/chunks/68563-5ae8d773d8aebd21.js	41.3 KiB	21.8 KiB
kit.com/_next/static/chunks/pages/_app-67844995a9b7e744.js	45.7 KiB	20.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
kit.com/	1.2 s	23 ms	0.5 ms
kit.com/_next/static/chunks/framework-a071c7e3156668e1.js	1.0 s	718 ms	21 ms
kit.com/_next/static/chunks/68563-5ae8d773d8aebd21.js	642 ms	99 ms	16 ms
Unattributable	604 ms	26 ms	0.0 ms
kit.com/_next/static/chunks/pages/index-9a22a715266f8c88.js	221 ms	219 ms	0.9 ms
kit.com/_next/static/chunks/webpack-b4f49bdf80a6e621.js	117 ms	102 ms	2.8 ms
kit.com/_next/static/chunks/pages/_app-67844995a9b7e744.js	91 ms	76 ms	14 ms
kit.com/_next/static/chunks/main-ff96fca99dd86bec.js	84 ms	71 ms	12 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	1.4 s
Other	1.4 s
Style & Layout	667 ms
Rendering	482 ms
Script Parsing & Compilation	168 ms
Parse HTML & CSS	61 ms
Garbage Collection	6.9 ms

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

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

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 7 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 120 ms

●Server Backend Latencies 60 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 80 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
Focus on what you love, automate more with Kit `div.Container_Container__Ak6Oe > div.flex > div.grow > h3._hdg`
Email marketing `div.flex > span > div.flex > h6._hdg`
SavvyCal `div.grid > div.flex > div.flex-1 > h6.hyphens-manual`

These are opportunities to improve keyboard navigation in your application.

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
Reject all `div.__className_853013 > div.cookie-banner > div.cookieConsent > button#rcc-decline-button`
Accept all `div.__className_853013 > div.cookie-banner > div.cookieConsent > button#rcc-confirm-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

●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

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

●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

●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

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

○Form elements have associated labels

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

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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

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