Skip to content
https://allocine.fr

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.

44

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.

RequestCache TTLTransfer Size
cdn.lib.getjad.io/library/120157152/ALLOCINE_FR_WEB7200.0 s202.8 KiB
assets.allocine.fr/js/website/website-common.d3da14fd91803900262f.js3600.0 s172.5 KiB
client.aps.amazon-adsystem.com/publisher.js3600.0 s82.3 KiB
cdn.id5-sync.com/api/1.0/id5-api.js3600.0 s34.5 KiB
/e23a01f6-a508-4e71-8f50-c1a9cae7c0d0/loader.js?target_ty...7200.0 s33.9 KiB
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js900.0 s21.7 KiB
assets.allocine.fr/js/website/home.07ffba97132d723e791c.js3600.0 s23.9 KiB
cdn.lib.getjan.io/library/allocine.js14400.0 s22.3 KiB
assets.allocine.fr/skin/font/icon/font-icon.488231ae.woff23600.0 s17.8 KiB
assets.allocine.fr/js/website/5038.611da82d3fb224bd2785.js3600.0 s14.1 KiB
/js/website/translations-3e5f9a1ee288763011eec279f4f2a02d...3600.0 s13.3 KiB
tags.crwdcntrl.net/lt/c/16576/sync.min.js86400.0 s13.5 KiB
assets.allocine.fr/js/website/2326.c70bb3085d1439348f66.js3600.0 s6.4 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
assets.allocine.fr/js/website/script-03.8a1fc93fdc6a41f47900.js3600.0 s4.7 KiB
assets.allocine.fr/skin/img/logo-boxoffice-company.686f7e8e.svg3600.0 s4.2 KiB
www.allocine.fr/_/js/routing?callback=AC.setRouting600.0 s3.4 KiB
assets.allocine.fr/skin/img/allocine/logo-main-white.536669e5.svg3600.0 s1.9 KiB
assets.allocine.fr/skin/img/logo-webedia-white.1476b15c.svg3600.0 s1.8 KiB
assets.allocine.fr/skin/img/allocine/logo-main-grey.5de8867c.svg3600.0 s1.7 KiB
config.aps.amazon-adsystem.com/configs/33093600.0 s1.6 KiB
assets.allocine.fr/skin/img/allocine/logo-main.ab1b33da.svg3600.0 s1.6 KiB
assets.allocine.fr/skin/img/logo-allocine.7e88ee87.svg3600.0 s1.2 KiB
boot.pbstck.com/v1/tag/f0b7ab5f-140d-42a6-9fbb-821a457e78341200.0 s930 B
assets.allocine.fr/skin/font/icon/font-icon.488231ae.woff23600.0 s0 B

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:85.805 source:map[type:text value:[unattributed]]]]

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

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.

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.carousel-row > figure.carousel-item > a.xXx > img.carousel-main-image div.carousel-row > figure.carousel-item > a.xXx > img.carousel-main-image
fr.web.img6.acsta.net/img/dc/4b/dc4b39b9f1590e39a8dab7672030047b.jpg39.9 KiB20.1 KiB
div.roller-item > div.roller-news-item > a.xXx > img.roller-main-hp-roller-image div.roller-item > div.roller-news-item > a.xXx > img.roller-main-hp-roller-image
fr.web.img2.acsta.net/c_350_135/img/cf/0b/cf0bf8fb1aa0e665132c009cbde34129.jpg15.3 KiB7.6 KiB
poster de L'Arnaqueuse div.card > figure.thumbnail > a.xXx > img.thumbnail-img
fr.web.img2.acsta.net/c_150_200/img/0b/f9/0bf95ca0474a1781b921862fb273a9cb.jpg11.8 KiB6.9 KiB
poster de Pour le meilleur div.card > figure.thumbnail > a.xXx > img.thumbnail-img
fr.web.img2.acsta.net/c_150_200/img/70/d6/70d6f7006ed9b8dbaf991e6922ba60f7.jpg9.9 KiB5.0 KiB
div.roller-item > div.roller-news-item > a.xXx > img.roller-main-hp-roller-image div.roller-item > div.roller-news-item > a.xXx > img.roller-main-hp-roller-image
fr.web.img4.acsta.net/c_350_135/img/bc/16/bc161b70f72dc61a6b4ae4d640862c45.jpg12.5 KiB4.8 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: 756 ms
URLTime Spent
allocine.fr/756 ms
www.allocine.fr/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

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

Estimated savings: 450 ms 88.7 KiB
URLTransfer SizeEst Savings
cdn.lib.getjad.io/library/120157152/ALLOCINE_FR_WEB202.0 KiB88.7 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.

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 Evaluation3.2 s
Other752 ms
Script Parsing & Compilation714 ms
Style & Layout536 ms
Rendering307 ms
Parse HTML & CSS104 ms
Garbage Collection102 ms

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 30.4 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
Logo div.didomi-popup-container > div.didomi-popup-view > div.didomi-popup-notice-logo-container > img.didomi-popup-notice-logo
fr.web.img6.acsta.net/commons/v9/allocine/logos/brand/logo-new-fb.png
Découvrez en plus avec AlloCiné div.banner-hp-wrapper > div.banner-hp-mobile > a.xXx > img.banner-hp-img

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
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Avoids enormous network payloads Total size was 1,510 KiB
User Timing marks and measures 9 user timings
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 160 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 20 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
Avoid non-composited animations
79

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Bouton Menu mobile header#header-main > div.header-main-center > div.header-main-top > div#header-main-mobile-btn-menu
Bouton Rechercher header#header-main > div.header-main-center > div.header-main-top > div#header-main-mobile-btn-search
Bouton Mon compte div.header-main-center > div.header-main-top > div#header-main-mobile-btn-userspace > span.icon

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.

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
div.didomi-popup-notice-text > p > div#cmp-main > button.jad_cmp_paywall_button div.didomi-popup-notice-text > p > div#cmp-main > button.jad_cmp_paywall_button
div.didomi-popup-notice-text > p > div#cmp-main > button.jad_cmp_paywall_button div.didomi-popup-notice-text > p > div#cmp-main > button.jad_cmp_paywall_button

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.video-card-player > div.player-info > div.item > a.xXx div.video-card-player > div.player-info > div.item > a.xXx

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.

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
au site pour TTC pendant 1 mois sans cookie publicitaire p > div#cmp-main > div.jad_cmp_paywall_section > h4.jad_cmp_paywall_title

These are opportunities to improve keyboard navigation in your application.

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

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
Le Petit lieutenant Bande-annonce VF div.video-card-player > div.player-info > div.item > a.item-link
Un air de famille Bande-annonce VF div.video-card-player > div.player-info > div.item > a.xXx
Bandi div.gd > div.card > div.meta > a.meta-title
Alter Ego div.gd > div.card > div.meta > a.meta-title
Malcolm : Rien n’a changé div.gd > div.card > div.meta > a.meta-title
Euphoria div.gd > div.card > div.meta > a.meta-title
Paris Police 1910 div.gd > div.card > div.meta > a.meta-title
Recalé div.gd > div.card > div.meta > a.meta-title
Enchaînés div.gd > div.card > div.meta > a.meta-title
La Petite maison dans la prairie div.gd > div.card > div.meta > a.meta-title

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
Image elements have `[alt]` attributes
Form elements have associated labels
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
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
Links are distinguishable without relying on color.
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
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-hidden="true"]` elements do not contain focusable descendents
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
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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
Image elements do not have `[alt]` attributes that are redundant text.
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.
73

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
fr.web.img6.acsta.net/commons/v9/allocine/logos/brand/logo-new-fb.pngAutomatically upgraded to HTTPS

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.

URLDisplayed sizeActual sizeExpected size
div.roller-item > div.roller-news-item > a.xXx > img.roller-main-hp-roller-image div.roller-item > div.roller-news-item > a.xXx > img.roller-main-hp-roller-image
fr.web.img4.acsta.net/c_350_135/img/bc/16/bc161b70f72dc61a6b4ae4d640862c45.jpg350 x 135350 x 135525 x 203
div.roller-item > div.roller-news-item > a.xXx > img.roller-main-hp-roller-image div.roller-item > div.roller-news-item > a.xXx > img.roller-main-hp-roller-image
fr.web.img4.acsta.net/c_350_135/img/f4/04/f404df65e713d76389e53402366f2e0c.jpg350 x 135350 x 135525 x 203

General

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
Mixed content
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
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
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
div#cmp-main > div.jad_cmp_paywall_intro > div.jad_cmp_paywall_intro-readmore > a.jad_cmp_paywall_intro-readmore-link div#cmp-main > div.jad_cmp_paywall_intro > div.jad_cmp_paywall_intro-readmore > a.jad_cmp_paywall_intro-readmore-link
cliquant ici div.jad_cmp_paywall_section > div.jad_cmp_paywall_text > p > a
div#cmp-main > div.jad_cmp_paywall_section > div.jad_cmp_paywall_readmore > a.jad_cmp_paywall_readmore-link div#cmp-main > div.jad_cmp_paywall_section > div.jad_cmp_paywall_readmore > a.jad_cmp_paywall_readmore-link
liste complète div.jad_cmp_paywall_section > div.jad_cmp_paywall_text > p > a
div#cmp-main > div.jad_cmp_paywall_section > div.jad_cmp_paywall_readmore > a.jad_cmp_paywall_readmore-link div#cmp-main > div.jad_cmp_paywall_section > div.jad_cmp_paywall_readmore > a.jad_cmp_paywall_readmore-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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback