Skip to content
https://disney.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.

50

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.

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:33.813 source:map[column:10072 line:2 type:source-location url:https://static-mh.content.disney.io/matterhorn/assets/jquery-dc8b911876ec.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:9.238 source:map[column:21471 line:2 type:source-location url:https://static-mh.content.disney.io/matterhorn/assets/jquery-dc8b911876ec.js urlProvider:network]] map[reflowTime:12.288 source:map[column:13245 line:1 type:source-location url:https://static-mh.content.disney.io/matterhorn/assets/modules/slider-f6eec86a9714.js urlProvider:network]] map[reflowTime:3.992 source:map[column:10780 line:2 type:source-location url:https://static-mh.content.disney.io/matterhorn/assets/modules/flex_content_hero-3c591439291d.js urlProvider:network]] map[reflowTime:5.951 source:map[column:6735 line:0 type:source-location url:https://static-mh.content.disney.io/matterhorn/assets/jquery-dc8b911876ec.js urlProvider:network]] map[reflowTime:1.613 source:map[column:29460 line:1 type:source-location url:https://static-mh.content.disney.io/matterhorn/assets/jquery-dc8b911876ec.js urlProvider:network]] map[reflowTime:0.731 source:map[column:6757 line:0 type:source-location url:https://static-mh.content.disney.io/matterhorn/assets/jquery-dc8b911876ec.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
Winnie l’Ourson : À la recherche du ballon perdu div.aspect-container > div.aspect > div.background-image > img
/v1/images/fr_wtp_popup_mob_142b40a7.jpeg?region=0,0,800,...160.0 KiB108.8 KiB
Logo du film Le Diable s'habille en Prada 2 div.content-details > a > div.content-title > img.logo-title
/v1/images/devil_wears_prada_2_fre-logo_r_9bece1b9.png?re...140.9 KiB99.5 KiB
Deux personnes marchent sur un passage piéton devant un hôtel coloré de style r… div.aspect-container > div.aspect > div.background-image > img
/v1/images/wdw_q3_updates_fy26_mob_m_d00f6354.jpeg?region...120.1 KiB69.0 KiB
Disney Adventure World div.aspect-container > div.aspect > div.background-image > img
/v1/images/fr_dlp-adventure-world_mob_m_fb76b41a.jpeg?reg...100.4 KiB49.3 KiB
Une image du film Le Diable s'habille en Prada 2 div.image-wrapper > div.aspect > a.ada-el-focus > img#ref-1-0--img--idx-0
/v1/images/eu_thedevilwearsprada2_mobile_hero_1b53fa6d.jp...104.7 KiB41.1 KiB
Scrubs div.aspect-container > div.aspect > div.background-image > img
/v1/images/eu_scrubs-2026_hulu_mob_m_ac8360a2.jpeg?region...92.1 KiB41.0 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:1007.858 label:Time to first byte subpart:timeToFirstByte] map[duration:1484.854 label:Resource load delay subpart:resourceLoadDelay] map[duration:63.963 label:Resource load duration subpart:resourceLoadDuration] map[duration:19.102 label:Element render delay subpart:elementRenderDelay]]
lhId: page-4-IMG
nodeLabel: Une image du film Le Diable s'habille en Prada 2
path: 2,HTML,1,BODY,4,DIV,10,DIV,1,DIV,0,DIV,0,ARTICLE,1,SECTION,0,DIV,0,DIV,0,UL,0,LI,0,DIV,0,DIV,0,A,0,IMG
selector: div.image-wrapper > div.aspect > a.ada-el-focus > img#ref-1-0--img--idx-0
snippet: <img tabindex="0" src="https://lumiere-a.akamaihd.net/v1/images/eu_thedevilwearsprada2_mobile_her…" id="ref-1-0--img--idx-0" width="750" height="564" alt="Une image du film Le Diable s'habille en Prada 2" data-width="750" data-height="564" data-aspect_ratio="0.752" data-orientation="landscape" data-legacy="true">

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-4-IMG
nodeLabel: Une image du film Le Diable s'habille en Prada 2
path: 2,HTML,1,BODY,4,DIV,10,DIV,1,DIV,0,DIV,0,ARTICLE,1,SECTION,0,DIV,0,DIV,0,UL,0,LI,0,DIV,0,DIV,0,A,0,IMG
selector: div.image-wrapper > div.aspect > a.ada-el-focus > img#ref-1-0--img--idx-0
snippet: <img tabindex="0" src="https://lumiere-a.akamaihd.net/v1/images/eu_thedevilwearsprada2_mobile_her…" id="ref-1-0--img--idx-0" width="750" height="564" alt="Une image du film Le Diable s'habille en Prada 2" data-width="750" data-height="564" data-aspect_ratio="0.752" data-orientation="landscape" data-legacy="true">

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.

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.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Lists the toplevel main thread tasks that executed during page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Collection of useful page vitals.

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

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: 11.6 s
URLTime Spent
disney.com/1.1 s
www.disney.com/10.2 s
www.disney.fr/330 ms
www.disney.fr/0.0 ms

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: 846 ms
URLTime Spent
www.disney.fr/946 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

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.

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.

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.

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.

Estimated savings: 400 ms 530.6 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
Facebook div.media-image > a > figure > img
/v1/images/icon_social_facebook_dark_9d7616bf.svg?region=...
Instagram div.media-image > a > figure > img
/v1/images/icon_social_instagram_dark_b5f8e532.svg?region...
X.com div.media-image > a > figure > img
lumiere-a.akamaihd.net/v1/images/twitter_x_logo_ff25ea4d.svg?region=0,0,32,32
Pinterest div.media-image > a > figure > img
/v1/images/icon_social_pinterest_dark_aa86ec65.svg?region...
Youtube div.media-image > a > figure > img
/v1/images/icon_social_youtube_dark_6136d901.svg?region=0...

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

Layout shift culprits
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 120 ms
Server Backend Latencies 300 ms
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
INP breakdown
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
91

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Le Mois de la Terre Collection Star Wars : Maul - Seigneur de l’Ombre section#ref-1-3 > div.bound > div.slides > ol.slider-list
Jumpers Le Diable s'habille en Prada 2 Star Wars: The Mandalorian and Grogu Toy… section#ref-1-12 > div.bound > div.slides > ol.slider-list

These are opportunities to improve the usage of ARIA in your application which 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
Le Mois de la Terre Collection div.entity-details > a.entity-link > h3.title > span
Star Wars : Maul - Seigneur de l’Ombre div.entity-details > a.entity-link > h3.title > span

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
RÉSERVER VOS BILLETS p.cta-links-container > span.cta-item > span.btn-container > a.button

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Suivez Disney sur: div.rich-text-container > div.rich_text_body > div.rich-text-output > table
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 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
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.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Heading elements appear in a sequentially-descending order
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.
Skip links are focusable.
`<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.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
`<td>` elements in a large `<table>` have one or more table headers.
77

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 URLRequest Resolution
www.disney.fr/Allowed

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
Failed to load resource: the server responded with a status of 404 ()
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 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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Connexion ul#goc-user-mobile > li.goc-login > span.trigger-menu > a.goc-icn-login
Gérer le compte MyDisney ul#goc-user-mobile > ul#My-Account-region > li.trigger-menu > a
Déconnexion ul#goc-user-mobile > ul#My-Account-region > li.trigger-menu > a
Plus div.goc-bound > ul#goc-desktop-global > li#goc-bar-more-dropdown > a.more-dropdown-link
Connexion ul#goc-user > li.goc-login > span.login-title-link > a.login-link
Gérer le compte MyDisney ul > li > span.trigger-base > a.login-dropdown-link
Déconnexion ul > li > span.trigger-base > a.login-dropdown-link

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

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Send Feedback