Skip to content
https://iveco.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

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.

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:0.272 source:map[column:29287 line:2 type:source-location url:https://www.iveco.com/dist/ivgcorporate/static/js/main.e751f011.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:3.972 source:map[column:2975 line:0 type:source-location url:https://www.iveco.com/dist/ivgcorporate/static/js/QuickActionsModule.c2dca7eb.chunk.js urlProvider:network]] map[reflowTime:7.508 source:map[type:text value:[unattributed]]] map[reflowTime:38.298 source:map[column:44931 line:1 type:source-location url:https://www.iveco.com/dist/ivgcorporate/static/js/95717.d7322101.chunk.js urlProvider:network]] map[reflowTime:0.156 source:map[column:6509 line:0 type:source-location url:https://www.iveco.com/dist/ivgcorporate/static/js/32463.11c121d6.chunk.js urlProvider:network]] map[reflowTime:0.272 source:map[column:1200 line:0 type:source-location url:https://www.iveco.com/dist/ivgcorporate/static/js/GlobalMenuModule.ecba1226.chunk.js urlProvider:network]] map[reflowTime:0.869 source:map[column:1688 line:0 type:source-location url:https://www.iveco.com/dist/ivgcorporate/static/js/HeroSliderModule.b369c662.chunk.js urlProvider:network]] map[reflowTime:0.818 source:map[column:24170 line:0 type:source-location url:https://www.iveco.com/dist/ivgcorporate/static/js/HeroSliderModule.b369c662.chunk.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.

URLResource SizeEst Savings
div > div.hero-slider-wrapper > div.hero-slide-image > img div > div.hero-slider-wrapper > div.hero-slide-image > img
/spain/-/media/IVECOdotcom/Spain/Promotions/2026/VNL_CAB0...124.0 KiB88.1 KiB
div > div.hero-slider-wrapper > div.hero-slide-image > img div > div.hero-slider-wrapper > div.hero-slide-image > img
/spain/-/media/IVECOdotcom/Spain/Promotions/2026/Tarjeta-...122.9 KiB87.0 KiB
div > div.hero-slider-wrapper > div.hero-slide-image > img div > div.hero-slider-wrapper > div.hero-slide-image > img
/spain/-/media/IVECOdotcom/Spain/Promotions/2026/VNL_VAN-...115.5 KiB79.6 KiB

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.

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

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.

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.0 s
URLTime Spent
www.iveco.com/spain2.1 s

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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

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.

CategoryTime Spent
Script Evaluation2.3 s
Other1.3 s
Style & Layout703 ms
Rendering360 ms
Script Parsing & Compilation308 ms
Parse HTML & CSS173 ms
Garbage Collection69 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.

div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image

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
●Modern HTTP
●Network dependency tree
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 2,365 KiB
●Avoid non-composited animations 1 animated element found
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 190 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
○INP breakdown
○LCP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid large layout shifts
85

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main > section#{6D13E0FC-5DA7-4AF6-8887-03CBE9388B6C} > div.hero-slider-pagination > button.slick-prev main > section#{6D13E0FC-5DA7-4AF6-8887-03CBE9388B6C} > div.hero-slider-pagination > button.slick-prev
main > section#{6D13E0FC-5DA7-4AF6-8887-03CBE9388B6C} > div.hero-slider-pagination > button.slick-next main > section#{6D13E0FC-5DA7-4AF6-8887-03CBE9388B6C} > div.hero-slider-pagination > button.slick-next

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.product-image-wrapper > img.product-image div > div.hero-slider-wrapper > div.product-image-wrapper > img.product-image

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
Política de Cookies div.bottom-links > ul > li > a#ot-sdk-btn
Política de privacidad div.bottom-links > ul > li > a#spainweb_Home_footer_Políticadeprivacidad
Aviso legal div.bottom-links > ul > li > a#spainweb_Home_footer_Avisolegal
Empleo div.bottom-links > ul > li > a#spainweb_Home_footer_Empleo

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
*Plazo 24 meses, 25 cuotas de 1.353,76€. Importe total adeudado 34.351,66 €. Pr… div > a#spainweb_Home_cardsCarousel_card > div.card-content > h5.card-grid-title
Conduce de forma más inteligente. Mantén el control. Impulsa tu negocio. div > a#spainweb_Home_cardsCarousel_card > div.card-content > h5.card-grid-title

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
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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.
92

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Connecting to 'https://ipinfo.io/json' violates the following Content Security Policy directive: "connect-src 'self' 'unsafe-inline' https://jswpowersports.com.au/ https://ipapi.co https://carsales.com.au https://www.google.com.au https://*.akamaihd.net https://*.adsrvr.org https://*.adform.net https://www.cognitoforms.com/ https://widget.cdn.sprii.shop https://mw-fanshop.ivecogroup.com https://www.googletagmanager.com https://profir.it.infrontfinance.com *.apnic.net www.formations-irisbus-iveco.com www.formation-bus-ivecofrance.com https://trial-eum-clienttons-s.akamaihd.net https://trial-eum-clientnsv4-s.akamaihd.net https://rdap.registro.br https://dealerchatbothd-qual.iveco.com https://dealerchatbothd.iveco.com https://rdap.lacnic.net https://welcome-c.iveco.com https://welcome.iveco.com *.adfixus.com https://cpqr-cert.iveco.com https://cpqr.iveco.com https://dealerchatbothd-qual.iveco.com https://dealerchatbothd.iveco.com data: https://az-eu-sitec-app-p-020.azurewebsites.net *.clarity.ms https://www.clarity.ms https://westeurope-sandbox.ordercloud.io https://westeurope-production.ordercloud.io https://az-eu-sitec-app-c-010.azurewebsites.net https://adservice.google.com *.googlesyndication.com https://www.google.com https://api.ipify.org https://rdap.arin.net https://maps.googleapis.com https://rdap.db.ripe.net *.akstat.io https://c.go-mpulse.net https://analytics.google.com https://dataplane.rum.eu-central-1.amazonaws.com https://sts.eu-central-1.amazonaws.com https://cognito-identity.eu-central-1.amazonaws.com https://px.ads.linkedin.com https://13750033.fls.doubleclick.net *.fls.doubleclick.net *.doubleclick.net https://www.facebook.com *.contentsquare.net https://iveco.com.br https://privacyportal-eu.onetrust.com https://privacyportal-eu.onetrust.com/request/v1/consentreceipts https://privacyportal-de.onetrust.com/request/v1/consentreceipts https://c.contentsquare.net https://maps.googleapis.com https://region1.analytics.google.com https://cdn.linkedin.oribi.io https://stats.g.doubleclick.net https://zn83cl4nnfiqpbp4o-cnhidcx.siteintercept.qualtrics.com https://cpqr.iveco.com https://cpqr.ivecogroup.com https://player.vimeo.com https://siteintercept.qualtrics.com https://privacyportal-eu-cdn.onetrust.com https://vimeo.com https://region1.google-analytics.com https://charts3.equitystory.com https://cdn.cookielaw.org https://www.google-analytics.com https://geolocation.onetrust.com https://col.site24x7rum.eu https://www.youtube.com". The action has been blocked.
Failed to load resource: the server responded with a status of 429 ()
Fetch API cannot load https://ipinfo.io/json. Refused to connect because it violates the document's Content Security Policy.
ipinfo.is fallback also failed: TypeError: Failed to fetch at https://www.iveco.com/dist/ivgcorporate/static/js/main.e751f011.js:2:24658 at async ge (https://www.iveco.com/dist/ivgcorporate/static/js/main.e751f011.js:2:24313)
Loading the image 'https://www.ivecogroup.com/favicon.ico' violates the following Content Security Policy directive: "img-src 'self' 'unsafe-inline' https://jswpowersports.com.au/ https://ipapi.co https://carsales.com.au https://www.google.com.au https://*.akamaihd.net https://*.adsrvr.org https://fonts.gstatic.com https://*.adform.net https://www.cognitoforms.com/ https://widget.cdn.sprii.shop https://welcome-c.iveco.com https://welcome.iveco.com https://cpqr-cert.iveco.com https://cpqr.iveco.com blob: https://purecatamphetamine.github.io *.contentsquare.net https://cpqr-cert.ivecogroup.com *.clarity.ms https://www.clarity.ms https://www.google.pl https://ad.doubleclick.net *.contentsquare.net https://l.contentsquare.net https://c.contentsquare.net https://maps.gstatic.com https://siteintercept.qualtrics.com https://maps.googleapis.com https://www.google-analytics.com https://px.ads.linkedin.com https://www.google.it https://px4.ads.linkedin.com https://www.facebook.com https://www.google.com https://www.googletagmanager.com https://fra1.qualtrics.com https://optanon.blob.core.windows.net https://cdn.cookielaw.org https://tmpprod-eucompwaf010.azureedge.net data:". The action has been blocked.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
●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
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.logo-images > img.logo-image div > div.hero-slider-wrapper > div.logo-images > img.logo-image
div > div.hero-slider-wrapper > div.product-image-wrapper > img.product-image div > div.hero-slider-wrapper > div.product-image-wrapper > img.product-image

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 have descriptive text
●Links are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback