Spain · Madrid Completed: Apr 21, 2026 19:25 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 68 / 100
Based on 8 categories, 0 sections
Room to improve — your 11.0s load time is above Google's 2.5s 'Good' threshold.
Several missing protections leave your users and data exposed.
Major barriers for users with disabilities — up to 15% of your audience.
Solid SEO basics — a few optimizations could boost rankings.
Solid infrastructure — fast server responses across the board.
Strong compliance posture across regulations.
Good content signals with minor gaps.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 20.7 MB (7.1 MB transferred)
Performance issues directly impact user engagement and conversion rates.
1 image-only link(s) without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/5d73dc60-dd52-41af-af3a-6cc61fc0e646)<a href="https://beavercheck.com/results/5d73dc60-dd52-41af-af3a-6cc61fc0e646"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fign.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fign.comThis badge auto-updates with your latest scan result.
Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 11.0s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
9 barrier(s) likely increasing bounce by ~36%.
Page takes 11.0s to load
+12% bounceUsers abandon at ~3s — you're 8.5s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 1.4s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
Mixed content on HTTPS page
+8% bounceBrowsers block insecure subresources — broken images, missing scripts, warning badge
Fix: Change http:// URLs inside the page to https:// (or protocol-relative)
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
2 form field(s) without a label
+4% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
65 link(s) with generic text ("click here", "read more")
+1% bounceScreen-reader users navigating by link list see no context — and search engines can't infer relevance
Fix: Rewrite with descriptive phrases that identify the destination
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
18 broken link(s) on the page
+5% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€425 investment → €3,550/month returns + EUR 20,500,000 risk avoided
€425
5h · 5 findings
€3,550 /mo
~€42,599 / year
EUR 20,500,000
if kept compliant
€128 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
5.0 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€1,708,335 / month at risk
~€20,500,020 / year if left unfixed
€20,500,000
+5 more
€1.65 /mo
22243.4 MB/mo × 0.074 EUR/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
4.67 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
11.04 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.37 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.034
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
7.68 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
21.64 s
Audit breakdown by category with detailed findings.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
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.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| 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.
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.
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.
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.
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.
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 () |
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.
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.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.03 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.60 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
74 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.174
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.79 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
5.64 s
Audit breakdown by category with detailed findings.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
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.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
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.
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 | 119.4 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 | 58.3 KiB |
Critique Michael : un spectacle d’exception oui, un biopic qui se rate (volonta… div.wrap > article.card > a.thumb > img.thumb | sm.ign.com/t/ign_fr/slotter/4/48655/48655_cz3w.800.png | 37.3 KiB | 23.0 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 | 13.6 KiB |
IGN Logo div.sidebar-header > div.logo-edition > a#headerlogo > img.ign-icon | assets1.ignimgs.com/kraken/ign30-logo-alt.png?width=96&auto=webp | 4.6 KiB | 4.3 KiB |
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.
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/ | 238 ms |
| www.ign.com/ | 208 ms |
| fr.ign.com/ | 0.0 ms |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
Test Last Flag : un hero shooter à l’ancienne, centré sur l’objectif div.page-content > section.vspotlight > div.wrap > article.card | 0.174 |
Le respect de votre vie privée est notre priorité
Nous et nos partenaires stock… div#qc-cmp2-container > div#qc-cmp2-main > div.qc-cmp-cleanslate > div#qc-cmp2-ui | 0.001 |
| 0.000 | |
1 heure, 30 minutes - Les pliants arrivent bientôt (avec une mauvaise nouvelle). div.tbl > article#content87685 > div.m > div.info | 0.000 |
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.
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 |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /pagead/managed/js/gpt/m202604160201/pubads_impl.js | 187.7 KiB | 121.7 KiB |
| cdn.jsdelivr.net/npm/hls.js | 127.5 KiB | 116.0 KiB |
| imasdk.googleapis.com/js/sdkloader/ima3.js | 150.0 KiB | 93.5 KiB |
| www.googletagmanager.com/gtag/js?id=G-CHH2BMFQ0J | 157.7 KiB | 62.8 KiB |
| www.googletagmanager.com/gtag/js?id=G-G0Z2FQREVE&cx=c>m=4e64k0h2 | 146.1 KiB | 62.4 KiB |
| cmp.inmobi.com/tcfv2/61/cmp2ui-fr.js | 111.8 KiB | 51.5 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 |
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 |
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=96&auto=webp |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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 |
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.bottom-controls > div.left-controls > div.volume-controls > input#volume div.bottom-controls > div.left-controls > div.volume-controls > input#volume |
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.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > div.info-bottom > div.container > a.comments |
div.m > div.info-bottom > div.container > a.comments div.m > 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.
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.
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.
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.
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.
Send Feedback