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
sgtm.fairmont.com/qg2bvifzdqcxwc2.js?aw=TXVGDVH2	600.0 s	168.9 KiB
d1et0fu7hk.kameleoon.eu/kameleoon.js	3600.0 s	50.5 KiB
tags.pw.adn.cloud/BSVP26/activation.js	14400.0 s	43.6 KiB
/SIE/?Q_ZID=ZN_xgdX2u2TIwS032F	3600.0 s	4.6 KiB
/dxjsmodule/12.1a2b7192fd54e87d3971.chunk.js?Q_CLIENTVERS...	604800.0 s	35.8 KiB
/dxjsmodule/CoreModule.js?Q_CLIENTVERSION=2.46.0&Q_CLIENT...	604800.0 s	30.9 KiB
/dxjsmodule/FeedbackButtonModule.js?Q_CLIENTVERSION=2.46....	604800.0 s	19.4 KiB
/dxjsmodule/37.7ea1ffe71ad8c0799cc1.chunk.js?Q_CLIENTVERS...	604800.0 s	18.6 KiB
rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js	3600.0 s	1.0 KiB
/dxjsmodule/1.bc67e778235741631577.chunk.js?Q_CLIENTVERSI...	604800.0 s	7.1 KiB
/dxjsmodule/7.f7df015b06d8a90ce822.chunk.js?Q_CLIENTVERSI...	604800.0 s	1.4 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.

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-0-IMG

nodeLabel: Fairmont

path: 1,HTML,1,BODY,6,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG

selector: div.country-language-selector > div.ace-country-flag > div.flag-accor-logo > img

snippet: <img src="/content/dam/brands/fai/global-marketing/brand-identity/logos/full-monochr…" alt="Fairmont">

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
cdn.signalfx.com/o11y-gdi-rum/v1.1.1/splunk-otel-web.js	88.0 KiB	1.7 s
/etc.clientlibs/ace/clientlibs/clientlib-pos.lc-7291861b0...	1.3 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.5 s

URL	Time Spent
fairmont.com/	782 ms
www.fairmont.com/	757 ms
www.fairmont.com/select-country.html	0.0 ms

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 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: 780 ms 182.0 KiB

URL	Transfer Size	Est Savings
/bc7c8544f73f6b27961e590e984e15e4d795a02230dcc1bfa7804efe...	186.5 KiB	182.0 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: 2.1 s 484.1 KiB

URL	Transfer Size	Est Savings
/bc7c8544f73f6b27961e590e984e15e4d795a02230dcc1bfa7804efe...	368.2 KiB	295.2 KiB
sgtm.fairmont.com/qg2bvifzdqcxwc2.js?aw=TXVGDVH2	168.6 KiB	67.4 KiB
cdn.signalfx.com/o11y-gdi-rum/v1.1.1/splunk-otel-web.js	87.5 KiB	40.7 KiB
/bc7c8544f73f6b27961e590e984e15e4d795a02230dcc1bfa7804efe...	41.2 KiB	35.0 KiB
tags.pw.adn.cloud/BSVP26/activation.js	43.3 KiB	24.7 KiB
/dxjsmodule/12.1a2b7192fd54e87d3971.chunk.js?Q_CLIENTVERS...	35.7 KiB	21.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
cdn.signalfx.com/o11y-gdi-rum/v1.1.1/splunk-otel-web.js	549 ms	466 ms	31 ms
Unattributable	484 ms	113 ms	0.0 ms
www.fairmont.com/select-country.html	423 ms	78 ms	7.3 ms
sgtm.fairmont.com/qg2bvifzdqcxwc2.js?aw=TXVGDVH2	181 ms	129 ms	50 ms
d1et0fu7hk.kameleoon.eu/kameleoon.js	172 ms	133 ms	19 ms
tags.pw.adn.cloud/BSVP26/activation.js	124 ms	111 ms	12 ms
/bc7c8544f73f6b27961e590e984e15e4d795a02230dcc1bfa7804efe...	89 ms	87 ms	0.1 ms
/dxjsmodule/12.1a2b7192fd54e87d3971.chunk.js?Q_CLIENTVERS...	76 ms	62 ms	10.0 ms
/_Incapsula_Resource?SWJIYLWA=719d34d31c8e3a6e6fffd425f7e...	62 ms	51 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.3 s
Other	447 ms
Style & Layout	217 ms
Script Parsing & Compilation	176 ms
Parse HTML & CSS	107 ms
Rendering	31 ms

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
Fairmont `div.country-language-selector > div.ace-country-flag > div.flag-accor-logo > img`	/content/dam/brands/fai/global-marketing/brand-identity/l...

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

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●Avoid long main-thread tasks 11 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 140 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

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

○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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

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

○No element has a `[tabindex]` value greater than 0

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

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

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	Map URL
sgtm.fairmont.com/qg2bvifzdqcxwc2.js?aw=TXVGDVH2
cdn.signalfx.com/o11y-gdi-rum/v1.1.1/splunk-otel-web.js	cdn.signalfx.com/o11y-gdi-rum/v1.1.1/splunk-otel-web.js.map

●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

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

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

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`head > meta`

To appear in search results, crawlers need access to your app.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid

●Document has a `<title>` element

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