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
proxyhog.prisma-data.net/static/posthog-recorder.js?v=1.364.4	14400.0 s	77.0 KiB
proxyhog.prisma-data.net/static/surveys.js?v=1.364.4	14400.0 s	29.5 KiB
kit.fontawesome.com/ad485975d2.js	60.0 s	5.7 KiB
kit.fontawesome.com/c1448b716e.js	60.0 s	5.7 KiB
/array/phc_cmc85avbWyuJ2JyKdGPdv7dxXli8xLdWDBPbvIXWJfs/co...	14400.0 s	4.8 KiB
cdn-cookieyes.com/assets/images/close.svg	36000.0 s	868 B

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:72.383 source:map[column:17280 line:1 type:source-location url:https://www.prisma.io/site-static/_next/static/chunks/156abb6c90a0c7cc.js?dpl=dpl_HgPvUg6EwrBqd6TdZZuBdzdW8hZj 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:44.337 source:map[type:text value:[unattributed]]] map[reflowTime:53.337 source:map[column:82978 line:0 type:source-location url:https://www.prisma.io/site-static/_next/static/chunks/156abb6c90a0c7cc.js?dpl=dpl_HgPvUg6EwrBqd6TdZZuBdzdW8hZj urlProvider:network]] map[reflowTime:45.866 source:map[column:39295 line:0 type:source-location url:https://www.prisma.io/site-static/_next/static/chunks/37ed35ca710f52e9.js?dpl=dpl_HgPvUg6EwrBqd6TdZZuBdzdW8hZj urlProvider:network]] map[reflowTime:72.231 source:map[column:137848 line:0 type:source-location url:https://proxyhog.prisma-data.net/static/posthog-recorder.js?v=1.364.4 urlProvider:network]] map[reflowTime:0.152 source:map[column:14089 line:0 type:source-location url:https://proxyhog.prisma-data.net/static/posthog-recorder.js?v=1.364.4 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

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
/site-static/_next/static/chunks/ce7d09c07ef18cd7.css?dpl...	40.3 KiB	450 ms
/site-static/_next/static/chunks/665dc3aa4aa2d85c.css?dpl...	4.1 KiB

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.

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: 1.6 s 311.6 KiB

URL	Transfer Size	Est Savings
/site-static/_next/static/chunks/23e9b289b6d26136.js?dpl=...	151.0 KiB	120.9 KiB
/site-static/_next/static/chunks/2724685019ebc7c1.js?dpl=...	65.0 KiB	47.5 KiB
proxyhog.prisma-data.net/static/posthog-recorder.js?v=1.364.4	76.9 KiB	45.8 KiB
/site-static/_next/static/chunks/156abb6c90a0c7cc.js?dpl=...	57.2 KiB	26.7 KiB
/site-static/_next/static/chunks/55ab220829433019.js?dpl=...	69.8 KiB	25.0 KiB
/site-static/_next/static/chunks/8566c171816e342a.js?dpl=...	26.1 KiB	23.3 KiB
proxyhog.prisma-data.net/static/surveys.js?v=1.364.4	29.4 KiB	22.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
www.prisma.io/	3.8 s	28 ms	25 ms
/site-static/_next/static/chunks/0b67ccd61ccae070.js?dpl=...	2.7 s	1.3 s	4.3 ms
/site-static/_next/static/chunks/156abb6c90a0c7cc.js?dpl=...	1.4 s	819 ms	50 ms
proxyhog.prisma-data.net/static/posthog-recorder.js?v=1.364.4	1.2 s	1.2 s	25 ms
Unattributable	1.2 s	60 ms	0.0 ms
/site-static/_next/static/chunks/55ab220829433019.js?dpl=...	1.2 s	858 ms	20 ms
kit.fontawesome.com/c1448b716e.js	137 ms	134 ms	2.3 ms
cdn-cookieyes.com/client_data/96980f76df67ad5235fc3f0d/banner.js	107 ms	56 ms	2.2 ms
/site-static/_next/static/chunks/fed6255c55e7e67f.js?dpl=...	61 ms	35 ms	14 ms
/site-static/_next/static/chunks/23e9b289b6d26136.js?dpl=...	53 ms	2.7 ms	50 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	4.5 s
Style & Layout	4.4 s
Other	2.0 s
Rendering	550 ms
Script Parsing & Compilation	296 ms
Parse HTML & CSS	160 ms
Garbage Collection	128 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

●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 1,716 KiB

●Avoid long main-thread tasks 15 long tasks 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 200 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

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

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

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4 `body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4`
45.7K `body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Create database `div.content > div.flex > a.flex > span`
npx prisma init `div.content > div.flex > button.flex > span.text-foreground-neutral-weak`
Explore Pricing `div.web-cta > div.content > a.flex > span`
500k `div.px-4 > div.max-w-[1240px] > h5.[&>b]:text-background-ppg-reverse-strong > b`
Create your first Database `div.mx-auto > div.flex > a.flex > span`
All Systems Operational `div.gap-6 > a.flex > span > p.underline`

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
TRUSTED BY MORE THAN 500k MONTHLY ACTIVE DEVELOPERS GLOBALLY `section.my-12 > div.px-4 > div.max-w-[1240px] > h5.[&>b]:text-background-ppg-reverse-strong`
Free to get started, no credit card needed. `div.mx-auto > div.p-4 > div.mx-auto > h6.mb-0!`

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.max-w-7xl > ul.gap-4 > li.relative > a.focus-visible:ring-ring/50 `div.max-w-7xl > ul.gap-4 > li.relative > a.focus-visible:ring-ring/50`

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
45.7K `body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4`

These are opportunities to improve the experience of reading tabular or list data using 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-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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

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

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`