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:118.627 source:map[column:1408 line:2 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/285j93odz-mc6.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:43.045 source:map[type:text value:[unattributed]]] map[reflowTime:0.622 source:map[column:567 line:1 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1-5u47uvn-y4d.js urlProvider:network]] map[reflowTime:42.588 source:map[column:23615 line:27 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/31zr8snds05pa.js urlProvider:network]] map[reflowTime:30.076 source:map[column:53174 line:54 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3m3duol34qvrp.js urlProvider:network]] map[reflowTime:45.341 source:map[column:3670 line:11 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2m1696-0wail1.js urlProvider:network]] map[reflowTime:42.254 source:map[column:7642 line:15 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2m1696-0wail1.js urlProvider:network]]]

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
/vc-ap-vercel-marketing/_next/static/immutable/chunks/17t...	22.6 KiB	150 ms
/vc-ap-vercel-marketing/_next/static/immutable/chunks/29z...	19.5 KiB	150 ms
/vc-ap-vercel-marketing/_next/static/immutable/chunks/37l...	2.3 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/3jk...	87.4 KiB	450 ms
/vc-ap-vercel-marketing/_next/static/immutable/chunks/2q_...	21.0 KiB	150 ms

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.5 s

URL	Time Spent
vercel.app/	752 ms
vercel.com/	790 ms
vercel.app/	0.0 ms
vercel.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 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: 370 ms 39.5 KiB

URL	Transfer Size	Est Savings
/vc-ap-vercel-marketing/_next/static/immutable/chunks/17t...	22.4 KiB	20.6 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/2q_...	20.8 KiB	18.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: 220 ms 367.7 KiB

URL	Transfer Size	Est Savings
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0-yecpdkl3vib.js	98.1 KiB	68.0 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3m3duol34qvrp.js	62.9 KiB	49.2 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2tnyci7ul9ujx.js	47.4 KiB	39.2 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2-ps3j9g79j1c.js	32.5 KiB	32.3 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2_j8wuiqfyszj.js	36.2 KiB	27.0 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/04rh4d4an7qnl.js	26.8 KiB	26.8 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3i232-eoz6nwc.js	26.8 KiB	26.7 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0d_c5upx5wk18.js	29.8 KiB	26.5 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/03bh8a1gjhil-.js	27.9 KiB	25.7 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/25-1zn0yv5qp-.js	24.2 KiB	23.6 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0t-hs-9sw4q5_.js	51.1 KiB	22.8 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
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/285j93odz-mc6.js	3.2 s	2.5 s	47 ms
vercel.com/	1.2 s	147 ms	156 ms
Unattributable	629 ms	21 ms	0.0 ms
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1jzv8nh4kvk-b.js	276 ms	253 ms	20 ms
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2n1seda456yr8.js	241 ms	134 ms	28 ms
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2yp89-bm2g-hn.js	207 ms	200 ms	6.3 ms
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2m1696-0wail1.js	197 ms	3.9 ms	12 ms
/vc-ap-vercel-marketing/_next/static/immutable/chunks/3jk...	61 ms	0.0 ms	0.0 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	3.5 s
Style & Layout	1.3 s
Script Parsing & Compilation	811 ms
Other	809 ms
Parse HTML & CSS	206 ms
Garbage Collection	121 ms
Rendering	62 ms

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

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 2 user timings

●Avoid long main-thread tasks 18 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 40 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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
LOADING STATUS… `div.footer-module__ESbTrq__statusRow > a.link-module__Q1NRQq__link > div.status-indicator-module__razUwq__content > p.text-copy-14`

These are opportunities to improve the legibility of your content.

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#header-wrapper > header.header-module__6nzVrW__header > div.flex > a#menu-button-_R_ab5tj9abqpfivbH1_ `div#header-wrapper > header.header-module__6nzVrW__header > div.flex > a#menu-button-_R_ab5tj9abqpfivbH1_`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Vercel logo `nav > div.grid > div > ul.list-none`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○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

●Form elements have associated labels

●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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

○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

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
vercel.com/api/jwt	`Failed to load resource: the server responded with a status of 403 ()`
/api/4507726617772032/envelope/?sentry_key=285c77642188fe...	`Failed to load resource: the server responded with a status of 429 ()`
vercel.com/ line 118, col 0	`Loading the font 'https://k2mkucxia43oc7fa.public.blob.vercel-storage.com/front/fonts/space-mono/space-mono-v11-latin-regular.woff2' violates the following Content Security Policy directive: "font-src 'self' vercel.com assets.vercel.com vercel.live fonts.gstatic.com *.vercel.sh". The action has been blocked.`
vercel.com/	Loading the image 'https://py8fhxnkzwtsqdo9.public.blob.vercel-storage.com/front/favicon/vercel/android-chrome-192x192.png' violates the following Content Security Policy directive: "img-src 'self' blob: data: .github.io avatars.githubusercontent.com user-images.githubusercontent.com vercel.com vercel.live .vercel.sh assets.vercel.com cdn.raster.app https://images.ctfassets.net https://www.google.com https://i.ytimg.com https://s3.amazonaws.com pbs.twimg.com https://www.gravatar.com https://lishhsx6kmthaacj.public.blob.vercel-storage.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

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes