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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2	40 ms
fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2	5.0 ms

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: div > div.Ufej2c > div.Ufej2c > img

path: 1,HTML,1,BODY,1,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,4,DIV,0,DIV,0,IMG

selector: div > div.Ufej2c > div.Ufej2c > img

snippet: <img draggable="false" alt="" decoding="async" src="blob:https://www.google.fr/a9b53a3c-ea7a-4ccb-aef9-5c686e337810">

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

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.zc8u2b > div.FovMle > div.rWrsVd > img.GZdVwd `div.zc8u2b > div.FovMle > div.rWrsVd > img.GZdVwd`	/images/branding/productlogos/maps_2025/v1/web-96dp/logo_...	17.9 KiB	16.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: 776 ms

URL	Time Spent
maps.google.fr/	776 ms
maps.google.fr/maps	0.0 ms
www.google.fr/maps	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 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: 900 ms 189.2 KiB

URL	Transfer Size	Est Savings
www.google.fr/maps	197.6 KiB	89.2 KiB
/maps/_/js/k=maps.lite.en.ZZHowdlwmgQ.2021.O/ck=maps.lite...	170.1 KiB	64.6 KiB
/maps/_/js/k=maps.lite.en.ZZHowdlwmgQ.2021.O/ck=maps.lite...	49.9 KiB	35.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.google.fr/maps	1.3 s	585 ms	216 ms
/maps/_/js/k=maps.lite.en.ZZHowdlwmgQ.2021.O/m=bootstrap,...	1.2 s	941 ms	0.0 ms
Unattributable	1.0 s	42 ms	0.0 ms
www.google.com/js/bg/Zd2qDcyUX2wIvPkBdt0eA2aanqqmvid5ojTkZH9iEf0.js	452 ms	441 ms	8.5 ms
/maps/_/js/k=maps.lite.en.ZZHowdlwmgQ.2021.O/ck=maps.lite...	268 ms	126 ms	13 ms
/maps/_/js/k=maps.lite.en.ZZHowdlwmgQ.2021.O/ck=maps.lite...	215 ms	111 ms	102 ms
/maps/_/js/k=maps.lite.en.ZZHowdlwmgQ.2021.O/ck=maps.lite...	105 ms	97 ms	3.3 ms
/maps/_/js/k=maps.lite.en.ZZHowdlwmgQ.2021.O/ck=maps.lite...	93 ms	58 ms	9.8 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	2.5 s
Other	1.3 s
Style & Layout	434 ms
Script Parsing & Compilation	387 ms
Garbage Collection	115 ms
Parse HTML & CSS	87 ms
Rendering	53 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
ParserAborted	Actionable
Modal dialog such as form resubmission or http password dialog was shown for the page upon navigating away.	Pending browser support
The page did not finish loading before navigating away.	Not actionable

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: 0.0 ms 98.2 KiB

URL	Transfer Size	Est Savings
.ZuFBwf{display:-webkit-box;display:-webkit-flex;display:flex;-webkit-box-pack:justify; … } …	64.4 KiB	64.2 KiB
html,body{height:100%} …	46.5 KiB	34.0 KiB

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
Google Maps `div.LDyojc > div.sT82ee > div.yxqbQ > img.SO6acc`	www.google.com/images/branding/lockups/2x/lockup_maps_color_131x24dp.png

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 916 KiB

●User Timing marks and measures 9 user timings

●Avoid long main-thread tasks 15 long tasks found

●Network Requests

●Network Round Trip Times 20 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 140 ms

○INP breakdown

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

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●The page contains a heading, skip link, or landmark region

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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 have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

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

○Heading elements appear in a sequentially-descending order

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

○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

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

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

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
www.google.fr/maps?entry=ml&utm_campaign=ml-ardi&coh=230964	Allowed

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
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/1b2f5d0b-cd75-4e49-ba03-17b228e5b00f	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/52cb1cd6-b17a-40c6-8ac4-1db6040f4df0	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/59cdb4b7-bd36-4623-a105-8514ad513049	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/9b976417-6ca7-4973-adc2-474ab6d4ad58	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/a6e62241-3c02-4cc4-83b5-cf74c51f08d8	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/a9b53a3c-ea7a-4ccb-aef9-5c686e337810	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/b1cd3fed-55d2-4357-a43a-bd73103702b2	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/c96dac51-ddb0-4398-9dd2-366da976c394	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/ca19d455-bbed-4f78-861f-7e2c858f6936	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/dabea5da-4c1b-4bb9-8bf1-6d7998aa2336	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/ddb9c4dd-d547-4156-b540-9e37e9db52c7	256 x 256	256 x 256	384 x 384
div > div.Ufej2c > div.Ufej2c > img `div > div.Ufej2c > div.Ufej2c > img`	blob:https://www.google.fr/f725c8ab-2227-483a-bbcf-272dd21ad12d	256 x 256	256 x 256	384 x 384

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
/maps/_/js/k=maps.lite.en.ZZHowdlwmgQ.2021.O/ck=maps.lite...
www.google.fr/maps
www.google.com/js/bg/Zd2qDcyUX2wIvPkBdt0eA2aanqqmvid5ojTkZH9iEf0.js

●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

●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

○Ensure CSP is effective against XSS attacks

○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
`x-robots-tag: noindex,nofollow`

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

○Structured data is valid

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