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
/PqryjIvWSxIXnk07kIPf/YOYubXhcSYLp8DLa1m/MBUmAQ/JXZbB/G1N...	21600.0 s	174.9 KiB
www.americanexpress.com/akam/13/4854a19b	21600.0 s	9.5 KiB

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.

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

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
/cdaas/one/statics/@americanexpress/dls/6.23.1/package/di...	46.9 KiB	1.1 s
/cdaas/one/statics/@americanexpress/homepage-frontend/3.1...	7.4 KiB
/etc.clientlibs/homepage/clientlibs/core-homepage/styles....	2.8 KiB

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
a.flex > div.product-nav-item-content > div.dls-card > img.dls-card `a.flex > div.product-nav-item-content > div.dls-card > img.dls-card`	/content/dam/amex/es-es/negocios/sbs_plat_metal_es_no_cm_...	43.4 KiB	41.5 KiB
Programa Membership Rewards® `div.card > div.image-wrap > div.offer-link1 > div.card-detail-image`	/content/dam/amex/es-es/homepage/offers/spain-homepage-pr...	18.4 KiB	4.6 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.8 s

URL	Time Spent
americanexpress.com/	843 ms
www.americanexpress.com/	787 ms
www.americanexpress.com/es/	151 ms
www.americanexpress.com/es-es/	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: 300 ms 45.2 KiB

URL	Transfer Size	Est Savings
/cdaas/one/statics/@americanexpress/dls/6.23.1/package/di...	46.2 KiB	45.2 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: 660 ms 196.5 KiB

URL	Transfer Size	Est Savings
www.americanexpress.com/etc.clientlibs/enterprise/clientlibs/enterprise.min.js	135.0 KiB	114.3 KiB
/PqryjIvWSxIXnk07kIPf/YOYubXhcSYLp8DLa1m/MBUmAQ/JXZbB/G1N...	173.7 KiB	36.4 KiB
/cdaas/one/statics/@americanexpress/dls/6.23.1/package/di...	25.3 KiB	23.8 KiB
/cdaas/one/statics/@americanexpress/homepage-frontend/3.1...	32.5 KiB	22.1 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
/PqryjIvWSxIXnk07kIPf/YOYubXhcSYLp8DLa1m/MBUmAQ/JXZbB/G1N...	682 ms	632 ms	37 ms
Unattributable	494 ms	31 ms	0.0 ms
www.americanexpress.com/es-es/	391 ms	7.8 ms	2.3 ms
www.americanexpress.com/etc.clientlibs/enterprise/clientlibs/enterprise.min.js	148 ms	93 ms	47 ms
www.americanexpress.com/akam/13/4854a19b	122 ms	112 ms	3.2 ms
/cdaas/one-tag/tagging/groups/group-747/v1.319.0/filter-d...	120 ms	104 ms	16 ms
www.aexp-static.com/cdaas/user-consent-management/ucm/v1.18.19/UCM.js	105 ms	42 ms	37 ms
/cdaas/one-tag/tagging/groups/group-747/data/data-60699-s...	78 ms	63 ms	0.3 ms
/akamai/one/statics/@americanexpress/dls-icons/0.5.0/pack...	76 ms	25 ms	26 ms
/cdaas/one/dxt-script-supplier-helper/1.4.7/dxt-script-su...	55 ms	46 ms	6.5 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	532 ms
Style & Layout	258 ms
Script Parsing & Compilation	222 ms
Parse HTML & CSS	124 ms
Rendering	57 ms
Garbage Collection	35 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
a.flex > div.product-nav-item-content > div.dls-card > img.dls-card `a.flex > div.product-nav-item-content > div.dls-card > img.dls-card`	/content/dam/amex/es-es/negocios/sbs_plat_metal_es_no_cm_...
a.flex > div.product-nav-item-content > div.dls-card > img.dls-card `a.flex > div.product-nav-item-content > div.dls-card > img.dls-card`	/content/dam/amex/es/tarjetas/chg_gold_metal_es_no_cm_160...
España `div._body1_ji473_3243 > span > span#footer-flag-ES > img`	/cdaas/one/statics/@americanexpress/static-assets/2.32.1/...
a.flex > div.product-nav-item-content > div.dls-card > img.dls-card `a.flex > div.product-nav-item-content > div.dls-card > img.dls-card`	/content/dam/amex/es-es/homepage/cards/spain-homepage-pro...
a.flex > div.product-nav-item-content > div.dls-card > img.dls-card `a.flex > div.product-nav-item-content > div.dls-card > img.dls-card`	/content/dam/amex/es-es/homepage/cards/spain-homepage-pro...
American Express `div._pad3T_ji473_125 > div._col_ji473_770 > span#amex-logo > img`	/cdaas/one/statics/axp-static-assets/1.7.1/package/dist/i...

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●Avoid long main-thread tasks 12 long tasks found

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 160 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 2 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○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
Instalar `div.appbanner > div.appbanner__container > a#appbanner-button-homepage > span.appbanner-button__text`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
American Express Company. `div._padB_ji473_18 > div.none > p > a.none`

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
Ofertas y servicios de American Express `div > div.richtext > div.pad-3-t > h5`

These are opportunities to improve keyboard navigation in your application.

○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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

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

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

○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

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
a.flex > div.product-nav-item-content > div.dls-card > img.dls-card `a.flex > div.product-nav-item-content > div.dls-card > img.dls-card`	/content/dam/amex/es-es/homepage/cards/spain-homepage-pro...	79 x 50	79 x 50	119 x 75
a.flex > div.product-nav-item-content > div.dls-card > img.dls-card `a.flex > div.product-nav-item-content > div.dls-card > img.dls-card`	/content/dam/amex/es-es/homepage/cards/spain-homepage-pro...	79 x 50	79 x 50	119 x 75

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
/PqryjIvWSxIXnk07kIPf/YOYubXhcSYLp8DLa1m/MBUmAQ/JXZbB/G1N...
www.americanexpress.com/etc.clientlibs/enterprise/clientlibs/enterprise.min.js

●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

●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

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

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