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
www.here.com/_next/static/media/FiraGO-Regular.4dac550f.woff2	130 ms
www.here.com/_next/static/media/FiraGO-Bold.a0025726.woff2	95 ms
www.here.com/_next/static/media/FiraGO-Medium.55351f37.woff2	85 ms
www.here.com/_next/static/media/hds-iconlibrary-core-ui-24px.3f02d47d.woff2	75 ms
www.here.com/_next/static/media/hds-iconlibrary-core-ui-16px.377d5356.woff2	35 ms
/_next/static/media/hds-iconlibrary-third-party-logos-24p...	30 ms
www.here.com/_next/static/media/hds-iconlibrary-core-ui-8px.e3b51c22.woff2	25 ms

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:142.854 source:map[column:128608 line:1 type:source-location url:https://www.here.com/_next/static/chunks/2f4795b2-a291ac5e844adca2.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:63.526 source:map[type:text value:[unattributed]]] map[reflowTime:30.424 source:map[column:68441 line:0 type:source-location url:https://www.here.com/_next/static/chunks/437-c7edadd3c6de200b.js urlProvider:network]] map[reflowTime:51.479 source:map[column:20742 line:0 type:source-location url:https://www.here.com/_next/static/chunks/890-8e1f839b04419223.js urlProvider:network]] map[reflowTime:9.441 source:map[column:123044 line:0 type:source-location url:https://www.here.com/_next/static/chunks/47-9d239b5a5ffa1436.js urlProvider:network]] map[reflowTime:2.265 source:map[column:119479 line:0 type:source-location url:https://www.here.com/_next/static/chunks/47-9d239b5a5ffa1436.js urlProvider:network]] map[reflowTime:2.45 source:map[column:164700 line:0 type:source-location url:https://www.here.com/_next/static/chunks/47-9d239b5a5ffa1436.js urlProvider:network]] map[reflowTime:1.093 source:map[column:237201 line:0 type:source-location url:https://www.here.com/_next/static/chunks/47-9d239b5a5ffa1436.js urlProvider:network]] map[reflowTime:57.238 source:map[column:29693 line:0 type:source-location url:https://www.here.com/_next/static/chunks/app/layout-98feebfe8bc6b53a.js urlProvider:network]] map[reflowTime:4.589 source:map[column:241361 line:0 type:source-location url:https://www.here.com/_next/static/chunks/47-9d239b5a5ffa1436.js urlProvider:network]] map[reflowTime:34.764 source:map[column:27770 line:0 type:source-location url:https://www.here.com/_next/static/chunks/47-9d239b5a5ffa1436.js urlProvider:network]]]

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
Automated driving `div.relative > div.h-full > picture > img.w-full`	/x7rx8ayph7ee/9a61d4b4-2c67-4b6a-973f-30cfc940e032/595643...	111.3 KiB	40.7 KiB
SDV Accelerator `div.relative > div.h-full > picture > img.w-full`	/x7rx8ayph7ee/7INICEppniOots9oGbqI3R/db5d4e73780fffc99d37...	50.4 KiB	29.2 KiB
Digital Cockpit `div.relative > div.h-full > picture > img.w-full`	/x7rx8ayph7ee/6bRmnp0xGEnmdRnx22qXRl/0d5f88335e8a214dc91b...	78.9 KiB	28.8 KiB
HERE Technologies 2025 `div.mt-0 > div.relative > picture.w-full > img.object-cover`	/x7rx8ayph7ee/4zw6WO48VSxPF8wuMHioRq/04451f0cafeda13648e0...	81.7 KiB	14.9 KiB

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
www.here.com/_next/static/css/d28e46d8eec39c7c.css	26.0 KiB	450 ms
www.here.com/_next/static/css/cc848a0dd9dd43a9.css	18.2 KiB	300 ms
www.here.com/_next/static/css/c101dd2e29bf381b.css	8.7 KiB	150 ms
www.here.com/_next/static/css/a94deb4675677438.css	7.9 KiB	150 ms
www.here.com/_next/static/css/58f4444584148f0c.css	2.1 KiB
www.here.com/_next/static/css/c263f21dcaa707a5.css	5.0 KiB
js.api.here.com/v3/3.1/mapsjs-ui.css	4.1 KiB	752 ms

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
/videos/ZQpeb9N6VdX2Wh3iI006qA/hd.mp4?vrJDkUal5oqylxVxZxw...	0.0 ms	3.9 MiB
/videos/ZQpeb9N6VdX2Wh3iI006qA/sd.mp4?dkJOU2F3Gb7T4LmC6QP...	0.0 ms	1.4 MiB
tags.tiqcdn.com/utag/here/herecomcorporate/prod/utag.js	300.0 s	52.3 KiB
app-ab31.marketo.com/js/forms2/js/forms2.min.js	14400.0 s	67.5 KiB
cdn.vidyard.com/thumbnails/ZQpeb9N6VdX2Wh3iI006qA/69350becbb1b140f3c5987.jpg	0.0 ms	38.3 KiB
/?api-key=2b4d8313b5b2882f554f24341f311b85db660fdd8123cff...	0.0 ms	1.0 KiB
tags.tiqcdn.com/utag/here/herecomcorporate/prod/utag.sync.js	300.0 s	991 B
cdn.vidyard.com/thumbnails/ZQpeb9N6VdX2Wh3iI006qA/69350becbb1b140f3c5987.jpg	0.0 ms	0 B

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.

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: 850 ms

URL	Time Spent
here.com/	850 ms
www.here.com/	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

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

URL	Transfer Size	Est Savings
www.here.com/_next/static/css/d28e46d8eec39c7c.css	24.1 KiB	20.1 KiB
www.here.com/_next/static/css/cc848a0dd9dd43a9.css	16.4 KiB	15.3 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: 300 ms 212.5 KiB

URL	Transfer Size	Est Savings
app-ab31.marketo.com/js/forms2/js/forms2.min.js	67.0 KiB	51.9 KiB
www.here.com/_next/static/chunks/494-c70bcdb9608f1fbf.js	56.6 KiB	49.0 KiB
tags.tiqcdn.com/utag/here/herecomcorporate/prod/utag.js	51.5 KiB	29.2 KiB
www.here.com/_next/static/chunks/279-61f25823861eb048.js	54.0 KiB	28.1 KiB
www.here.com/_next/static/chunks/844-97e49dc3b5e571a7.js	34.1 KiB	27.3 KiB
www.here.com/_next/static/chunks/47-9d239b5a5ffa1436.js	74.8 KiB	27.0 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.here.com/_next/static/chunks/2f4795b2-a291ac5e844adca2.js	10.8 s	9.0 s	28 ms
Unattributable	1.8 s	142 ms	0.0 ms
www.here.com/_next/static/chunks/552-ea968a77fab22b45.js	1.7 s	1.4 s	16 ms
www.here.com/	1.7 s	128 ms	367 ms
www.here.com/_next/static/chunks/279-61f25823861eb048.js	418 ms	150 ms	11 ms
app-ab31.marketo.com/js/forms2/js/forms2.min.js	229 ms	152 ms	19 ms
www.here.com/_next/static/chunks/844-97e49dc3b5e571a7.js	196 ms	186 ms	9.1 ms
www.here.com/_next/static/chunks/494-c70bcdb9608f1fbf.js	91 ms	69 ms	21 ms
tags.tiqcdn.com/utag/here/herecomcorporate/prod/utag.js	68 ms	46 ms	21 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	11.3 s
Other	2.1 s
Style & Layout	1.4 s
Garbage Collection	1.2 s
Script Parsing & Compilation	545 ms
Parse HTML & CSS	340 ms
Rendering	173 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/videos/ZQpeb9N6VdX2Wh3iI006qA/hd.mp4?vrJDkUal5oqylxVxZxw...	3.9 MiB
/videos/ZQpeb9N6VdX2Wh3iI006qA/sd.mp4?dkJOU2F3Gb7T4LmC6QP...	1.4 MiB
www.here.com/_next/static/media/FiraGO-Medium.55351f37.woff2	255.7 KiB
www.here.com/_next/static/media/FiraGO-Bold.a0025726.woff2	255.3 KiB
www.here.com/_next/static/media/FiraGO-Regular.4dac550f.woff2	249.0 KiB
/x7rx8ayph7ee/9a61d4b4-2c67-4b6a-973f-30cfc940e032/595643...	111.9 KiB
/x7rx8ayph7ee/4zw6WO48VSxPF8wuMHioRq/04451f0cafeda13648e0...	82.3 KiB
/x7rx8ayph7ee/6bRmnp0xGEnmdRnx22qXRl/0d5f88335e8a214dc91b...	79.4 KiB
www.here.com/_next/static/chunks/47-9d239b5a5ffa1436.js	76.6 KiB
app-ab31.marketo.com/js/forms2/js/forms2.min.js	67.5 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoid long main-thread tasks 20 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 100 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 4 layout shifts found

○INP breakdown

○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
Get in touch `section.flex > div.flex > section.flex > h2.heading-1`
Let's talk about how you can use a unified live map to build superior experienc… `div.flex > section.flex > div.mt-4 > p.paragraph`
"Privacy/Cookie Policy" `div.t_cm_ec_modal > div.t_cm_ec_modal_body > div.privacy_prompt_main_description > a.t_cm_ec_normalize_links`

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
read more on HERE360 `div.flex > div > p.paragraph > a.text-action`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Why HERE `div.flex > div.w-full > nav.flex > button.paragraph-small`
Why HERE `div.w-full > nav.flex > button.paragraph-small > a.w-full`

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

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

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

●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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○No form fields have multiple labels

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

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

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

○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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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
www.here.com/omdia-2025	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`