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 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:40.179 source:map[column:137980 line:1 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/framework-bfbcaa5a2903bc7d.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:62.91 source:map[type:text value:[unattributed]]] map[reflowTime:3.486 source:map[column:21574 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319f943b4083.js urlProvider:network]] map[reflowTime:1.342 source:map[column:570689 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-dd735f07021249cc.js urlProvider:network]] map[reflowTime:9.832 source:map[column:220485 line:387 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b09b2ca44f5e5ddc.js urlProvider:network]] map[reflowTime:3.87 source:map[column:16493 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319f943b4083.js urlProvider:network]] map[reflowTime:8.429 source:map[column:15635 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319f943b4083.js urlProvider:network]] map[reflowTime:3.533 source:map[column:124944 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b09b2ca44f5e5ddc.js urlProvider:network]] map[reflowTime:4.499 source:map[column:11215 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/83686-faac451816184ca8.js urlProvider:network]] map[reflowTime:5.188 source:map[column:17297 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/63328-9e9e8032d49a619d.js urlProvider:network]] map[reflowTime:1.219 source:map[column:123203 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b09b2ca44f5e5ddc.js urlProvider:network]] map[reflowTime:1.508 source:map[column:2541 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/82954.e99b34ee9139ef41.js urlProvider:network]] map[reflowTime:35.833 source:map[column:22406 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/46687.21608bbbc5586ea3.js urlProvider:network]]]

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
www.redditstatic.com/ads/pixel.js	60.0 s	19.0 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
tag.demandbase.com/e5737616348cbfe8.min.js	3600.0 s	18.5 KiB
s.yimg.jp/images/listing/tool/cv/ytag.js	600.0 s	11.8 KiB
tag.flvcdn.net/lytag.js	600.0 s	9.5 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
js.zi-scripts.com/zi-tag.js	0.0 ms	5.7 KiB
/rp.gif?ts=1778169233398&id=t2_l4hi0cof&event=PageVisit&m...	0.0 ms	667 B
/collect/?pid=332772&url=https%3A%2F%2Fstripe.com%2F&fmt=...	0.0 ms	536 B
/attribution_trigger?pid=332772&time=1778169233432&url=ht...	0.0 ms	519 B
partners.tremorhub.com/sync?UIDM=71ad8d77-fcea-4684-b3a1-c6f94e16cbcc	0.0 ms	394 B
q.quora.com/_/ad/8a924fea65514ffb9467da930d0acaca/pixel?tag=ViewContent	0.0 ms	344 B
/collect?v=2&fmt=js&pid=332772&time=1778169233432&li_adsI...	0.0 ms	272 B
/track/cmb/generic?ttd_pid=lp1a8un&ttd_tpi=1&ttd_passthro...	0.0 ms	256 B
/tr?id=742650679237989&dl=https://stripe.com/?auth=0&ev=P...	0.0 ms	19 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.dom-graphic__content > div.payments-graphic__terminal > picture.payments-graphic__terminal-image > img `div.dom-graphic__content > div.payments-graphic__terminal > picture.payments-graphic__terminal-image > img`	/fzn2n1nzq965/1Vf8oT9Fm6dEwpnEx5PgK1/055956f38d7fd8b0cc74...	67.9 KiB	24.9 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

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: 150 ms 218.9 KiB

URL	Transfer Size	Est Savings
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b...	233.5 KiB	106.0 KiB
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-dd...	337.1 KiB	70.5 KiB
/mkt-ssr-statics/assets/_next/static/chunks/c67c952e-7f65...	55.8 KiB	42.4 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
/mkt-ssr-statics/assets/_next/static/chunks/50582.fb4a3d1...	116.7 s	2.4 s	12 ms
/mkt-ssr-statics/assets/_next/static/chunks/framework-bfb...	3.4 s	2.2 s	43 ms
Unattributable	2.6 s	141 ms	0.0 ms
stripe.com/	2.3 s	14 ms	1.5 ms
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-dd...	1.0 s	612 ms	319 ms
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b...	602 ms	390 ms	130 ms
/mkt-ssr-statics/assets/_next/static/chunks/46687.21608bb...	385 ms	233 ms	6.2 ms
/mkt-ssr-statics/assets/_next/static/chunks/81888-44c0418...	271 ms	249 ms	9.3 ms
/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319...	266 ms	15 ms	3.5 ms
/mkt-ssr-statics/assets/_next/static/chunks/main-df8f4439...	195 ms	165 ms	29 ms
/mkt-ssr-statics/assets/_next/static/chunks/c67c952e-7f65...	194 ms	166 ms	28 ms
/mkt-ssr-statics/assets/_next/static/chunks/webpack-07086...	178 ms	169 ms	6.2 ms
/mkt-ssr-statics/assets/_next/static/chunks/96834-6100e9c...	72 ms	28 ms	7.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
Other	116.0 s
Script Evaluation	7.1 s
Rendering	2.2 s
Style & Layout	2.0 s
Script Parsing & Compilation	734 ms
Garbage Collection	442 ms
Parse HTML & CSS	157 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

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Network dependency tree

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●User Timing marks and measures 4 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 42 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 260 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

100

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.

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
Accept and optimize payments globally—online and in person Pay Roastery Cartsy … `div.modular-solutions-bento > div.modular-solutions-bento__content > div.modular-solutions-bento__layout > button.modular-solutions-bento-card`
Enable any billing model Pro Plan Billed monthly Tokens $0.01 per 1,000 units U… `div.modular-solutions-bento > div.modular-solutions-bento__content > div.modular-solutions-bento__layout > button.modular-solutions-bento-card`
Read the story `div#customer-Hertz > div#detail-customer-content-Hertz > div.customer-stories__customer-content--read > a#customer-content-Hertz`
Read the story `div#customer-URBN > div#detail-customer-content-URBN > div.customer-stories__customer-content--read > a#customer-content-URBN`
Read the story `div#customer-Instacart > div#detail-customer-content-Instacart > div.customer-stories__customer-content--read > a#customer-content-Instacart`
Read the story `div#customer-LeMonde > div#detail-customer-content-LeMonde > div.customer-stories__customer-content--read > a#customer-content-LeMonde`

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●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

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

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b...
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-dd...

●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

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
stripe.com/blog/introducing-our-agentic-commerce-solutions	Read more
stripe.com/blog/introducing-our-agentic-commerce-solutions	Read more

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`