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
choices.consentframework.com/js/pa/46244/c/1O0Ql/cmp	3600.0 s	165.7 KiB
www.ipsos.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?	14400.0 s	12.4 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
cache.consentframework.com/js/pa/46244/c/1O0Ql/stub	3600.0 s	2.5 KiB
munchkin.marketo.net/munchkin.js	0.0 ms	1.2 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.

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
How to build trust in the AI era `div#slick-slide00 > div.paragraph > picture > img.highlights__pic`	/sites/default/files/styles/hp_slider/public/2026-02/Scre...	2.2 MiB	1.5 MiB
Insights to Activate Impact Stories `div#slick-slide10 > div.paragraph > picture > img.highlights__pic`	/sites/default/files/styles/hp_slider/public/2026-01/web-...	1.7 MiB	985.0 KiB
A GLOBAL PRESENCE WITH 90 markets ALL OFFICES `div.global-block__bg > div.global-block__bg1 > div.global-block__bg2 > div.global-block__bg3`	/sites/ipsos/themes/custom/ipsos/html2025/build/images/mi...	115.0 KiB	98.7 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:321.378 label:Time to first byte subpart:timeToFirstByte] map[duration:2195.85 label:Element render delay subpart:elementRenderDelay]]

lhId: page-3-DIV

nodeLabel: We and our 4 partners wish to store and access information on your devices (suc…

path: 1,HTML,1,BODY,20,DIV,0,DIV,1,DIV,0,DIV,0,DIV,4,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV

selector: div.sd-cmp-gpI1s > div.sd-cmp-xbcna > div.sd-cmp-VhJqD > div

snippet: <div>

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

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
/css2?family=Barlow+Semi+Condensed:ital,wght@0,400;0,500;...	346.6 KiB	2.5 s
/sites/default/files/css/css_uhIUcN13-OV8OUrpkqQqpdF2fOXE...	36.3 KiB	453 ms
/sites/default/files/css/css_lQoUQWrgX-UNfH7xY5mq6_kxbdp7...	4.5 KiB

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.

Estimated savings: 1.6 s

URL	Time Spent
ipsos.com/	802 ms
www.ipsos.com/	812 ms
www.ipsos.com/en-us	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.

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.

Estimated savings: 170 ms 36.3 KiB

URL	Transfer Size	Est Savings
/css2?family=Barlow+Semi+Condensed:ital,wght@0,400;0,500;...	346.6 KiB	36.3 KiB

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: 1.7 s 377.8 KiB

URL	Transfer Size	Est Savings
/css2?family=Barlow+Semi+Condensed:ital,wght@0,400;0,500;...	346.2 KiB	346.2 KiB
/sites/default/files/css/css_uhIUcN13-OV8OUrpkqQqpdF2fOXE...	36.2 KiB	31.6 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.2 s 450.9 KiB

URL	Transfer Size	Est Savings
/sites/default/files/js/js_npFedVWVNmQAFPeamnYjmV9AInxl8Q...	117.2 KiB	76.1 KiB
www.googletagmanager.com/gtag/js?id=G-SQVZ1SDGC0&cx=c&gtm=4e64h1	173.1 KiB	70.1 KiB
www.googletagmanager.com/gtag/js?id=G-X263VWZR69&cx=c&gtm=4e64h1	168.7 KiB	68.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-NZ2K4ZR	162.0 KiB	66.6 KiB
www.googletagmanager.com/gtag/js?id=AW-1070074081&cx=c&gtm=4e64h1	144.8 KiB	64.6 KiB
www.googletagmanager.com/gtag/js?id=AW-17811859262&cx=c&gtm=4e64h1	143.5 KiB	64.0 KiB
choices.consentframework.com/js/pa/46244/c/1O0Ql/cmp	164.6 KiB	40.7 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.ipsos.com/en-us	811 ms	45 ms	3.1 ms
choices.consentframework.com/js/pa/46244/c/1O0Ql/cmp	573 ms	435 ms	63 ms
Unattributable	566 ms	27 ms	0.0 ms
/sites/default/files/js/js_npFedVWVNmQAFPeamnYjmV9AInxl8Q...	366 ms	210 ms	37 ms
www.ipsos.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	340 ms	326 ms	2.7 ms
www.googletagmanager.com/gtag/js?id=G-SQVZ1SDGC0&cx=c&gtm=4e64h1	266 ms	202 ms	62 ms
www.googletagmanager.com/gtm.js?id=GTM-NZ2K4ZR	232 ms	174 ms	48 ms
www.googletagmanager.com/gtag/js?id=G-X263VWZR69&cx=c&gtm=4e64h1	213 ms	159 ms	52 ms
www.googletagmanager.com/gtag/js?id=AW-1070074081&cx=c&gtm=4e64h1	183 ms	136 ms	46 ms
www.googletagmanager.com/gtag/js?id=AW-17811859262&cx=c&gtm=4e64h1	168 ms	125 ms	43 ms
/css2?family=Barlow+Semi+Condensed:ital,wght@0,400;0,500;...	78 ms	0.0 ms	0.0 ms
cache.consentframework.com/js/pa/46244/c/1O0Ql/stub	78 ms	74 ms	0.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	1.9 s
Style & Layout	765 ms
Other	601 ms
Script Parsing & Compilation	364 ms
Parse HTML & CSS	116 ms
Garbage Collection	103 ms
Rendering	38 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
/sites/default/files/styles/hp_slider/public/2026-02/Scre...	2.2 MiB
/sites/default/files/styles/hp_slider/public/2026-01/web-...	1.7 MiB
/css2?family=Barlow+Semi+Condensed:ital,wght@0,400;0,500;...	346.6 KiB
www.googletagmanager.com/gtag/js?id=G-SQVZ1SDGC0&cx=c&gtm=4e64h1	173.1 KiB
www.googletagmanager.com/gtag/js?id=G-X263VWZR69&cx=c&gtm=4e64h1	168.8 KiB
choices.consentframework.com/js/pa/46244/c/1O0Ql/cmp	165.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-NZ2K4ZR	162.4 KiB
www.googletagmanager.com/gtag/js?id=AW-1070074081&cx=c&gtm=4e64h1	144.9 KiB
www.googletagmanager.com/gtag/js?id=AW-17811859262&cx=c&gtm=4e64h1	143.6 KiB
/sites/default/files/js/js_npFedVWVNmQAFPeamnYjmV9AInxl8Q...	117.3 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
Ipsos `div.header__inner > div.header__logo > a > img`	/sites/ipsos/themes/custom/ipsos/html2025/build/images/mi...
Ipsos `div.footer__inner > div.footer__col > a.footer__logo > img`	/sites/ipsos/themes/custom/ipsos/html2025/build/images/mi...

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

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 15 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 210 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

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

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
We and our 4 partners wish to store and access information on your devices (suc… `div.sd-cmp-gpI1s > div.sd-cmp-xbcna > div.sd-cmp-VhJqD > div`
partners `div.sd-cmp-xbcna > div.sd-cmp-VhJqD > div > strong.vendors`
This is used to develop and provide you with services, content, and advertiseme… `div.sd-cmp-gpI1s > div.sd-cmp-xbcna > div.sd-cmp-VhJqD > div`
You can "accept all" and withdraw your consent at any time via the "cookies" fo… `div.sd-cmp-vfoED > div.sd-cmp-gpI1s > div.sd-cmp-xbcna > div.sd-cmp-VhJqD`
powered by `div.sd-cmp-Wfd7X > div.sd-cmp-KebVX > a > span`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.latest-insights__publications > div.latest-insights__left > div.insights-block > a `div.latest-insights__publications > div.latest-insights__left > div.insights-block > a`
div.footer__social > ul.links > li > a `div.footer__social > ul.links > li > a`
div.footer__social > ul.links > li > a `div.footer__social > ul.links > li > a`
div.footer__social > ul.links > li > a `div.footer__social > ul.links > li > a`
div.footer__social > ul.links > li > a `div.footer__social > ul.links > li > a`
div.footer__social > ul.links > li > a `div.footer__social > ul.links > li > a`

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Open `header#header > div.header__inner > ul.header__buttons > li`
Select `header#header > div.header__inner > ul.header__buttons > li`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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

●Document has a `<title>` element

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

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

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

○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

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	www.ipsos.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.ipsos.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.ipsos.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

●Uses HTTPS

●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

●Page has valid source maps

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