Lighthouse Mobile
· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.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.
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
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.
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.
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.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Good Luck, Have Fun, Don’t Die est assurément le plus gros bordel cinématograph… div.wrap > article.card > a.thumb > img.thumb | sm.ign.com/t/ign_fr/slotter/4/48535/48535_2qkd.800.png | 144.1 KiB | 68.6 KiB |
div.tbl > article.embed_video_broll > figure.icmsvideocontainer > img.videoposter div.tbl > article.embed_video_broll > figure.icmsvideocontainer > img.videoposter | /t/ign_fr/video/a/alkahest-o/alkahest-official-gameplay-r... | 47.0 KiB | 33.7 KiB |
Test Last Flag : un hero shooter à l’ancienne, centré sur l’objectif div.wrap > article.card > a.thumb > img.thumb | sm.ign.com/t/ign_fr/slotter/4/48450/48450_v82d.800.png | 82.3 KiB | 19.2 KiB |
IGN Logo header.fixed-header > div.sidebar-page-header > a.logo-link > img.ign-icon | assets1.ignimgs.com/kraken/ign30-logo-alt.png?width=192&auto=webp | 14.6 KiB | 13.2 KiB |
Test Diablo IV Lord of Hatred : lumière et ténèbres pour sauver Sanctuaire div.wrap > article.card > a.thumb > img.thumb | /t/ign_fr/screenshot/default/diablo-4-lord-of-hatred-ca-v... | 30.5 KiB | 10.9 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| /assets/inter-latin-variable-wghtOnly-normal-a05a0d687a08... | 5.0 ms |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| fr.ign.com/s/css/videoplayer.css?680 | 3.4 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| ign.com/ | 751 ms |
| www.ign.com/ | 768 ms |
| fr.ign.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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Diagnostics
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.jsdelivr.net/npm/hls.js | 159.5 KiB | 145.2 KiB |
| /pagead/managed/js/gpt/m202604160201/pubads_impl.js | 187.7 KiB | 123.7 KiB |
| imasdk.googleapis.com/js/sdkloader/ima3.js | 150.0 KiB | 93.3 KiB |
| www.googletagmanager.com/gtag/js?id=G-CHH2BMFQ0J | 157.7 KiB | 62.3 KiB |
| cmp.inmobi.com/tcfv2/cmp2.js?referer=fr.ign.com | 115.8 KiB | 57.8 KiB |
| cmp.inmobi.com/tcfv2/61/cmp2ui-fr.js | 111.8 KiB | 51.9 KiB |
| pg.ignimgs.com/pogoadkit.js | 45.9 KiB | 45.2 KiB |
| fundingchoicesmessages.google.com/i/7047?ers=3 | 68.7 KiB | 36.8 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| fr.ign.com/ | 1.0 s | 147 ms | 7.5 ms |
| cmp.inmobi.com/tcfv2/cmp2.js?referer=fr.ign.com | 647 ms | 465 ms | 46 ms |
| Unattributable | 563 ms | 9.8 ms | 0.0 ms |
| /pagead/managed/js/gpt/m202604160201/pubads_impl.js | 528 ms | 428 ms | 92 ms |
| cmp.inmobi.com/tcfv2/61/cmp2ui-fr.js | 489 ms | 316 ms | 47 ms |
| www.googletagmanager.com/gtag/js?id=G-CHH2BMFQ0J | 402 ms | 339 ms | 61 ms |
| imasdk.googleapis.com/js/sdkloader/ima3.js | 307 ms | 254 ms | 48 ms |
| fundingchoicesmessages.google.com/i/7047?ers=3 | 293 ms | 244 ms | 25 ms |
| www.googletagmanager.com/gtag/js?id=G-G0Z2FQREVE&cx=c>m=4e64k0h2 | 218 ms | 184 ms | 32 ms |
| /f/AGSKWxVXMVcHHiHe3morEoN3zvmCkrdNQwAuQEcfy34o4rtQMzN-C9... | 121 ms | 35 ms | 72 ms |
| cdn.jsdelivr.net/npm/hls.js | 83 ms | 41 ms | 42 ms |
| sm.ign.com/themes_10.js?680 | 82 ms | 4.7 ms | 1.1 ms |
| pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js | 72 ms | 62 ms | 8.4 ms |
| securepubads.g.doubleclick.net/tag/js/gpt.js | 65 ms | 56 ms | 8.1 ms |
| fr.ign.com/s/bundle_ign.js?680 | 53 ms | 43 ms | 3.9 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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 2.7 s |
| Other | 1.1 s |
| Script Parsing & Compilation | 533 ms |
| Style & Layout | 494 ms |
| Rendering | 225 ms |
| Parse HTML & CSS | 89 ms |
| Garbage Collection | 34 ms |
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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with WebSocket cannot enter back/forward cache. | Pending browser support |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| fr.ign.com/s/js/videoplayer/setupPreroll.js?680 | 4.4 KiB | 2.7 KiB |
| fr.ign.com/s/js/videoplayer/setupVideoPlayer.js?680 | 6.2 KiB | 2.3 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
IGN Logo div.sidebar-header > div.logo-edition > a#headerlogo > img.ign-icon | assets1.ignimgs.com/kraken/ign30-logo-alt.png?width=192&auto=webp |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#video-controls > div.bottom-controls > div.left-controls > button#play div#video-controls > div.bottom-controls > div.left-controls > button#play |
div.bottom-controls > div.left-controls > div.volume-controls > button#volume-button div.bottom-controls > div.left-controls > div.volume-controls > button#volume-button |
div.bottom-controls > div.right-controls > div.quality-controls > button#quality-button div.bottom-controls > div.right-controls > div.quality-controls > button#quality-button |
div#video-controls > div.bottom-controls > div.right-controls > button#fullscreen-button div#video-controls > div.bottom-controls > div.right-controls > button#fullscreen-button |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.tbl > article.embed_video_broll > figure.icmsvideocontainer > img.videoposter div.tbl > article.embed_video_broll > figure.icmsvideocontainer > img.videoposter |
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Change Region
United States
United Kingdom
Australia
Africa
Adria Serbian/Croat… div#ignheader > div.region > div.region-selector > select#region-dropdown |
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
section.hero > article.hero > div.vplayer > iframe#video53243 section.hero > article.hero > div.vplayer > iframe#video53243 |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.sidebar-main > ul.sidebar-section > li.legal > a div.sidebar-main > ul.sidebar-section > li.legal > a |
div#mainblock > header.fixed-header > div.sidebar-page-header > a#current-user div#mainblock > header.fixed-header > div.sidebar-page-header > a#current-user |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
div.m-mobile > div.info-bottom > div.container > a.comments div.m-mobile > div.info-bottom > div.container > a.comments |
footer#footer > div#footerMain > div.legal > a footer#footer > div#footerMain > div.legal > 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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Google Photos Touch-Up : quoi de neuf avec les nouveaux outils d’édition subtil… div.tbl > article#content87682 > div.m > h3 |
These are opportunities to improve keyboard navigation in your application.
Tables and lists
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Accueil
Ciné, Séries, Anime
Comics & mangas
Tech & Gadgets
Le Cri du Mochi
Test… div.side-container > div.side > div.sidebar-main > ul.sidebar-section |
Contact
Presse
Politique de Cookies
Conditions Générales d’Utilisation
Politiqu… div.side-container > div.side > div.sidebar-main > ul.sidebar-section |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 404 () |
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
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
div.sidebar-main > ul.sidebar-section > li.search > a div.sidebar-main > ul.sidebar-section > li.search > a |
To appear in search results, crawlers need access to your app.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.tbl > article.embed_video_broll > figure.icmsvideocontainer > img.videoposter div.tbl > article.embed_video_broll > figure.icmsvideocontainer > img.videoposter |
Format your HTML in a way that enables crawlers to better understand your app’s content.