https://immersion-facile.beta.gouv.fr/
37
Performance
96
Accessibility
83
Best Practices
91
SEO
PWA
37
Performance
96
Accessibility
83
Best Practices
91
SEO
PWA
37
Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
6.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Time to Interactive
8.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index
6.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time
660 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Largest Contentful Paint
7.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Cumulative Layout Shift
0.088
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Opportunities
Opportunity
Estimated Savings
Reduce unused JavaScript
2.13 s
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.LCP
URL
Transfer Size
Potential Savings
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
670.8 KiB
358.4 KiB
…../node_modules/.pnpm/leaflet@1.9.4/node_modules/leaflet/dist/leaflet-src.js
40.8 KiB
34.2 KiB
…../shared/src/email/emailTemplatesByName.ts
16.0 KiB
13.7 KiB
…../node_modules/.pnpm/@sentry+replay@7.119.1/node_modules/@sentry/replay/esm/index.js
33.5 KiB
12.2 KiB
…../node_modules/.pnpm/zod@3.22.3/node_modules/zod/lib/index.mjs
14.7 KiB
9.4 KiB
…../node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom.production.min.js
35.3 KiB
9.3 KiB
/js/container_gXlljpZ7.js
(matomo.inclusion.beta.gouv.fr)
72.2 KiB
33.1 KiB
Reduce unused CSS
1.52 s
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.FCPLCP
URL
Transfer Size
Potential Savings
/assets/main-DutxoaB7.css
(immersion-facile.beta.gouv.fr)
301.6 KiB
284.8 KiB
Eliminate render-blocking resources
1.29 s
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.FCPLCP
URL
Transfer Size
Potential Savings
/assets/main-DutxoaB7.css
(immersion-facile.beta.gouv.fr)
301.6 KiB
1,680 ms
Properly size images
0.15 s
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
URL
Resource Size
Potential Savings
Vignette vidéo Immersion en entreprise
<img src="https://immersion.cellar-c2.services.clever-cloud.com/video_immersion_en_e…" alt="Vignette vidéo Immersion en entreprise">
/video_immersion_en_entreprise_poster.webp
(immersion.cellar-c2.services.clever-cloud.com)
20.4 KiB
11.2 KiB
These suggestions can help your page load faster. They don't directly affect the Performance score.
Diagnostics
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn moreCLS
URL
Vignette vidéo Immersion en entreprise
<img src="https://immersion.cellar-c2.services.clever-cloud.com/video_immersion_en_e…" alt="Vignette vidéo Immersion en entreprise">
/video_immersion_en_entreprise_poster.webp
(immersion.cellar-c2.services.clever-cloud.com)
Plateforme de l'Inclusion
<img src="/assets/plateforme-inclusion-logo-BlXDzmuq.svg" alt="Plateforme de l'Inclusion" class="fr-footer__logo fr-m-2w fr-m-md-0 fr-mr-md-2w css-16iy0h2-partnerLogo im-f…">
/assets/plateforme-inclusion-logo-BlXDzmuq.svg
(immersion-facile.beta.gouv.fr)
Immersion Facilitée - Faciliter la réalisation des immersions professionnelles
<img class="fr-responsive-img css-xg6j4x-LayoutHeader-operator" src="/assets/img/logo-if.svg" alt="Immersion Facilitée - Faciliter la réalisation des immersions professionne…" style="max-width: 9.0625rem;" data-fr-js-ratio="true">
…img/logo-if.svg
(immersion-facile.beta.gouv.fr)
France Travail
<img src="/assets/logo-france-travail-stTXUoM9.svg" alt="France Travail" class="fr-footer__logo fr-mx-md-1w im-footer__logo css-17kr9f6-LayoutFooter-partn…">
/assets/logo-fran….svg
(immersion-facile.beta.gouv.fr)
Les entreprises s'engagent
<img src="/assets/les-entreprises-s-engagent-BjFnE2K3.svg" alt="Les entreprises s'engagent" class="fr-footer__logo im-footer__logo css-17kr9f6-LayoutFooter-partnerLogo">
/assets/les-entre….svg
(immersion-facile.beta.gouv.fr)
Serve static assets with an efficient cache policy 18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
URL
Cache TTL
Transfer Size
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
None
671 KiB
/assets/main-DutxoaB7.css
(immersion-facile.beta.gouv.fr)
None
302 KiB
/assets/illustration-default-hero-BPYThvtM.webp
(immersion-facile.beta.gouv.fr)
None
58 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
None
44 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
None
42 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
None
42 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
None
41 KiB
/assets/dsfr.module-CAs0d9sb.js
(immersion-facile.beta.gouv.fr)
None
28 KiB
/video_immersion_en_entreprise_poster.webp
(immersion.cellar-c2.services.clever-cloud.com)
None
21 KiB
/assets/plateforme-inclusion-logo-BlXDzmuq.svg
(immersion-facile.beta.gouv.fr)
None
5 KiB
/assets/les-entre….svg
(immersion-facile.beta.gouv.fr)
None
5 KiB
…img/logo-if.svg
(immersion-facile.beta.gouv.fr)
None
4 KiB
/assets/logo-fran….svg
(immersion-facile.beta.gouv.fr)
None
3 KiB
…css/custom.css
(immersion-facile.beta.gouv.fr)
None
1 KiB
/registerSW.js
(immersion-facile.beta.gouv.fr)
None
1 KiB
/env-config.js
(immersion-facile.beta.gouv.fr)
None
1 KiB
…HeatmapSe…/configs.php?idsite=…
(matomo.inclusion.beta.gouv.fr)
None
0 KiB
/js/container_gXlljpZ7.js
(matomo.inclusion.beta.gouv.fr)
1 h
72 KiB
Minimize main-thread work 2.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn moreTBT
Category
Time Spent
Script Evaluation
1,432 ms
Other
511 ms
Style & Layout
310 ms
Parse HTML & CSS
103 ms
Rendering
51 ms
Garbage Collection
22 ms
Script Parsing & Compilation
22 ms
Reduce JavaScript execution time 1.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
1,601 ms
1,206 ms
8 ms
Unattributable
342 ms
10 ms
0 ms
/js/container_gXlljpZ7.js
(matomo.inclusion.beta.gouv.fr)
220 ms
206 ms
12 ms
https://immersion-facile.beta.gouv.fr
148 ms
3 ms
0 ms
/assets/main-DutxoaB7.css
(immersion-facile.beta.gouv.fr)
125 ms
0 ms
0 ms
Avoid chaining critical requests 8 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.FCPLCP
Maximum critical path latency: 1,220 ms
Initial Navigation
https://immersion-facile.beta.gouv.fr
…css/custom.css
(immersion-facile.beta.gouv.fr)
- 90 ms, 0.86 KiB
/assets/main-DutxoaB7.css
(immersion-facile.beta.gouv.fr)
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
- 90 ms, 41.80 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
- 90 ms, 41.06 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
- 90 ms, 41.67 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
- 90 ms, 43.95 KiB
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
/assets/dsfr.module-CAs0d9sb.js
(immersion-facile.beta.gouv.fr)
- 90 ms, 27.99 KiB
/registerSW.js
(immersion-facile.beta.gouv.fr)
- 500 ms, 0.80 KiB
/env-config.js
(immersion-facile.beta.gouv.fr)
- 90 ms, 0.78 KiB
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Name
Type
Start Time
Duration
sentry-tracing-init
Mark
939.93 ms
Keep request counts low and transfer sizes small 27 requests • 1,360 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type
Requests
Transfer Size
Total
27
1,360.0 KiB
Script
6
772.9 KiB
Stylesheet
2
302.5 KiB
Font
4
168.5 KiB
Image
6
96.0 KiB
Other
8
18.5 KiB
Document
1
1.7 KiB
Media
0
0.0 KiB
Third-party
1
20.8 KiB
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element
Avec Immersion Facilitée, trouvez un métier à tester, entrez en relation immédi…
<h2 class="fr-text--xl im-hero-header__description">
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element
CLS Contribution
Avec Immersion Facilitée, trouvez un métier à tester, entrez en relation immédi…
<h2 class="fr-text--xl im-hero-header__description">
0.031
À propos des cookies sur immersion-facile.beta.gouv.fr Bienvenue ! Nous utilis…
<div id="fr-consent-banner" class="fr-consent-banner">
0.018
Bienvenue ! Nous utilisons des cookies pour améliorer votre expérience et les s…
<p class="fr-text--sm">
0.009
Bienvenue ! Nous utilisons des cookies pour améliorer votre expérience et les s…
<p class="fr-text--sm">
0.009
Faciliter la réalisation des immersions professionnelles
<h1 class="fr-display--xs im-hero-header__title">
0.008
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn moreTBT
URL
Start Time
Duration
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
6,550 ms
348 ms
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
7,025 ms
283 ms
/js/container_gXlljpZ7.js
(matomo.inclusion.beta.gouv.fr)
8,934 ms
139 ms
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
6,898 ms
127 ms
/assets/main-DutxoaB7.css
(immersion-facile.beta.gouv.fr)
2,588 ms
125 ms
Unattributable
858 ms
95 ms
Unattributable
759 ms
85 ms
/js/container_gXlljpZ7.js
(matomo.inclusion.beta.gouv.fr)
8,877 ms
57 ms
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
7,342 ms
56 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (26)
Show Hide
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.FCPLCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.FCPLCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.FCPLCP
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.FCPLCP
Initial server response time was short Root document took 80 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.FCPLCP
URL
Time Spent
https://immersion-facile.beta.gouv.fr
80 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.FCPLCP
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.FCPLCP
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn moreLCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn MoreTBT
URL
Potential Savings
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
0.1 KiB
../../../node_modules/.pnpm/@babel+runtime@7.26.0/node_modules/@babel/runtime/helpers/esm/classCallCheck.js:2:45
@babel/plugin-transform-classes
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more.LCP
Avoids enormous network payloads Total size was 1,360 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.LCP
URL
Transfer Size
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
670.8 KiB
/assets/main-DutxoaB7.css
(immersion-facile.beta.gouv.fr)
301.6 KiB
/js/container_gXlljpZ7.js
(matomo.inclusion.beta.gouv.fr)
72.2 KiB
/assets/illustration-default-hero-BPYThvtM.webp
(immersion-facile.beta.gouv.fr)
57.8 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
44.0 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
41.8 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
41.7 KiB
/assets/Marianne-….woff2
(immersion-facile.beta.gouv.fr)
41.1 KiB
/assets/dsfr.module-CAs0d9sb.js
(immersion-facile.beta.gouv.fr)
28.0 KiB
/video_immersion_en_entreprise_poster.webp
(immersion.cellar-c2.services.clever-cloud.com)
20.8 KiB
Avoids an excessive DOM size 444 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.TBT
Statistic
Element
Value
Total DOM Elements
444
Maximum DOM Depth
div.fr-radio-group > div.fr-radio-rich__img > svg > use.fr-artwork-decorative
<use class="fr-artwork-decorative" xlink:href="/assets/light-BcMY7tSa.svg#artwork-decorative">
16
Maximum Child Elements
Accessibilité : partiellement conformeMentions légalesPolitique de confidential…
<ul class="fr-footer__bottom-list">
12
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.FCPLCP
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.TBT
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more.
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Avoids unload event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
96
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Failing Elements
Vous êtes candidat pour une immersion
<h3 class="im-nav-card__title im-hero-header__nav-card-title">
Vous êtes candidat pour une immersion Vous êtes candidat pour une immersion
<div class="im-nav-card im-nav-card--candidate im-hero-header__nav-card im-hero-header…">
Vous représentez une entreprise
<h3 class="im-nav-card__title im-hero-header__nav-card-title">
Vous représentez une entreprise Vous représentez une entreprise
<div class="im-nav-card im-nav-card--establishment im-hero-header__nav-card im-hero-he…">
These are opportunities to improve the legibility of your content.
Navigation
[id] attributes on active, focusable elements are not unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
Failing Elements
Personnaliser
<button id="fr-consent-modal-control-button" class="fr-btn fr-btn--secondary" aria-controls="fr-consent-modal" data-fr-opened="false" data-fr-js-modal-button="true">
Gestion des cookies
<a class="fr-footer__bottom-link" label="Gestion des cookies" id="fr-consent-modal-control-button" href="#fr-consent-modal">
These are opportunities to improve keyboard navigation in your application.
Additional items to manually check (10)
Show Hide
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (20)
Show Hide
[aria-*] attributes match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Buttons have an accessible name
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 more.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
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.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Links have a discernible name
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 more.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
List items (<li>) are contained within <ul> or <ol> parent elements
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
Heading elements appear in a sequentially-descending order
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.
Not applicable (22)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA meter elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA progressbar elements have accessible names
When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA tooltip elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA treeitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items are wrapped in <dl> elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
<input type="image"> elements have [alt] text
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
83
Best Practices
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Source
Description
../../../node_modules/.pnpm/@sentry+browser@7.119.1/node_modules/@sentry/browser/esm/transports/fetch.js:41:13
Fetch API cannot load https://o4508405260615680.ingest.de.sentry.io/api/4508999055507536/envelope/?sentry_key=8bbb3df20b0910b08f2f435e46f6390f&sentry_version=7&sentry_client=sentry.javascript.browser%2F7.119.1. Refused to connect because it violates the document's Content Security Policy.
../../../node_modules/.pnpm/@sentry+browser@7.119.1/node_modules/@sentry/browser/esm/transports/fetch.js:41:13
Refused to connect to 'https://o4508405260615680.ingest.de.sentry.io/api/4508999055507536/envelope/?sentry_key=8bbb3df20b0910b08f2f435e46f6390f&sentry_version=7&sentry_client=sentry.javascript.browser%2F7.119.1' because it violates the following Content Security Policy directive: "default-src 'self' https://user-images.githubusercontent.com https://tally.so https://px.ads.linkedin.com https://snap.licdn.com https://metabase.immersion-facile.beta.gouv.fr https://matomo.inclusion.beta.gouv.fr https://sentry.gip-inclusion.cloud-ed.fr wss://client.relay.crisp.chat/w/9d/  https://client.crisp.chat data: blob: https://immersion.cellar-c2.services.clever-cloud.com https://immersion-dev.cellar-c2.services.clever-cloud.com https://immersion-staging.cellar-c2.services.clever-cloud.com *.openstreetmap.org 'unsafe-inline' 'unsafe-eval'". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback.
Issues were logged in the Issues panel in Chrome Devtools
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.
Issue type
Content security policy
…450…/envelope?sentry_key=…
(o4508405260615680.ingest.de.sentry.io)
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name
Version
Leaflet
1.9.4
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Description
Directive
Severity
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
default-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
default-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
High
Passed audits (11)
Show Hide
Uses HTTPS
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.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
Avoids front-end JavaScript libraries with known security vulnerabilities
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
URL
Map URL
/assets/main-evRgUNgv.js
(immersion-facile.beta.gouv.fr)
/assets/main-evRgUNgv.js.map
(immersion-facile.beta.gouv.fr)
/assets/dsfr.module-CAs0d9sb.js
(immersion-facile.beta.gouv.fr)
/assets/dsfr.module-CAs0d9sb.js.map
(immersion-facile.beta.gouv.fr)
Not applicable (1)
Show Hide
Fonts with font-display: optional are preloaded
Preload `optional` fonts so first-time visitors may use them. Learn more
91
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.
Crawling and Indexing
robots.txt is not valid 70 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.
Line #
Content
Error
1
<!DOCTYPE html>
Syntax not understood
2
<html lang="fr">
Syntax not understood
3
<head>
Syntax not understood
4
  <meta charset="UTF-8"/>
Syntax not understood
5
  <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
Syntax not understood
6
  <meta
Syntax not understood
7
      name="google-site-verification"
Syntax not understood
8
      content="LsGoJ0vVY7hOl4PgphuQ7UqvurMtEngLqjmjnBevsi0"
Syntax not understood
9
  />
Syntax not understood
11
  <title>PMSMP: Immersion Facile</title>
Unknown directive
13
  <meta name="theme-color" content="#0091FF"/>
Syntax not understood
14
  <link rel="stylesheet" href="/assets/css/custom.css"/>
Syntax not understood
15
  <link rel="apple-touch-icon" href="/assets/apple-touch-icon-DrfPSIlu.png" />
Syntax not understood
16
  <link rel="icon" href="/assets/favicon-CduWKyBp.svg" type="image/svg+xml" />
Syntax not understood
17
  <link rel="shortcut icon" href="/assets/favicon-BMkCb9zi.ico" type="image/x-icon" />
Syntax not understood
18
  <link rel="manifest" href="/assets/manifest-Ysg1ohlc.webmanifest" crossorigin="use-credentials" />
Syntax not understood
21
  <script type="module" crossorigin src="/assets/main-evRgUNgv.js"></script>
Syntax not understood
22
  <link rel="stylesheet" crossorigin href="/assets/main-DutxoaB7.css">
Syntax not understood
23
<link rel="manifest" href="/manifest.webmanifest"><script id="vite-plugin-pwa:register-sw" src="/registerSW.js"></script></head>
Unknown directive
25
<body>
Syntax not understood
26
<div id="root"></div>
Syntax not understood
27
<noscript>
Syntax not understood
28
  <h1>
Syntax not understood
29
    Immersion Facilitée: Faciliter la réalisation des immersions
Unknown directive
30
    professionnelles
Syntax not understood
31
  </h1>
Syntax not understood
32
  <h2>La meilleure façon de faire émerger de nouveaux talents</h2>
Syntax not understood
33
  <p>
Syntax not understood
34
    Avec Immersion Facilitée, trouvez un métier à tester, entrez en relation
Syntax not understood
35
    immédiatement avec une entreprise accueillante, remplissez une demande
Syntax not understood
36
    de convention et obtenez une réponse en temps record !
Syntax not understood
37
  </p>
Syntax not understood
38
  <p>
Syntax not understood
39
    Ce site a besoin de JavaScript pour fonctionner correctement, nous vous
Syntax not understood
40
    conseillons
Syntax not understood
41
    <a href="https://enablejavascript.co/fr/" target="_blank">
Unknown directive
42
      d'activer JavaScript
Syntax not understood
43
    </a>
Syntax not understood
44
  </p>
Syntax not understood
45
  <h3>Liens utiles:</h3>
Unknown directive
47
  <ul>
Syntax not understood
48
    <li>
Syntax not understood
49
      <a
Syntax not understood
50
          href="https://immersion-facile.beta.gouv.fr/aide/"
Unknown directive
51
          target="_blank"
Syntax not understood
52
      >
Syntax not understood
53
        Contactez l'équipe
Syntax not understood
54
      </a>
Syntax not understood
55
    </li>
Syntax not understood
56
    <li>
Syntax not understood
57
      <a
Syntax not understood
58
          href="https://www.linkedin.com/company/l-immersion-facilitee/"
Unknown directive
59
          target="_blank"
Syntax not understood
60
      >
Syntax not understood
61
        Rejoignez-nous sur Linkedin
Syntax not understood
62
      </a>
Syntax not understood
63
    </li>
Syntax not understood
64
    <li>
Syntax not understood
65
      <a
Syntax not understood
66
          href="https://immersion-facile.beta.gouv.fr/aide/"
Unknown directive
67
          target="_blank"
Syntax not understood
68
      >
Syntax not understood
69
        Accédez à notre FAQ
Syntax not understood
70
      </a>
Syntax not understood
71
    </li>
Syntax not understood
72
  </ul>
Syntax not understood
73
</noscript>
Syntax not understood
74
<script src="/env-config.js"></script>
Syntax not understood
75
</body>
Syntax not understood
76
</html>
Syntax not understood
To appear in search results, crawlers need access to your app.
Mobile Friendly
Tap targets are not sized appropriately 97% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Tap Target
Size
Overlapping Target
Statistiques
<a class="fr-footer__bottom-link" label="Statistiques" href="/stats" target="_blank" id="im-footer-nav__stats">
67x18
Plan du site
<a class="fr-footer__bottom-link" label="Plan du site" href="/pages/plan-du-site" id="im-footer-nav__sitemap">
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (11)
Show Hide
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn more.
Links are crawlable
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 More
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.
Source
Selector
% of Page Text
Font Size
Legible text
100.00%
≥ 12px
 
 
  
   Document avoids plugins   
     
 
  
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
 
 
 
 
  
  
 
 Not applicable (1)   
 
 Show Hide 
 
  
 
  
   Document has a valid rel=canonical   
     
 
  
Canonical links suggest which URL to show in search results. Learn more.
 
 
 
 
 
                                  
PWA
 
 
These checks validate the aspects of a Progressive Web App. Learn more.
 
Installable
 
  
   Web app manifest or service worker do not meet the installability requirements 4 reasons  
     
 
  
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
 
 
Failure reason
Manifest start URL is not valid
Manifest does not contain a 'name' or 'short_name' field
Manifest 'display' property must be one of 'standalone', 'fullscreen', or 'minimal-ui'
No supplied icon is at least 144 px square in PNG, SVG or WebP format, with the purpose attribute unset or set to "any"
 
PWA Optimized
 
  
   Does not register a service worker that controls page and start_url   
     
 
  
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
 
 
 
 
  
   Is not configured for a custom splash screen
Failures: Manifest does not have `background_color`,
Manifest does not have `theme_color`,
Manifest does not have `name`.
   
     
 
  
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more.
 
 
 
 
  
   Does not set a theme color for the address bar.
Failures: Manifest does not have `theme_color`.
   
     
 
  
The browser address bar can be themed to match your site. Learn more.
 
 
 
 
  
   Content is sized correctly for the viewport   
     
 
  
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.
 
 
 
 
  
   Has a <meta name="viewport"> tag with width or initial-scale   
     
 
  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
 
 
 
 
  
   Provides a valid apple-touch-icon   
     
 
  
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
 
 
 
 
  
   Manifest doesn't have a maskable icon   
     
 
  
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.
 
 
 
  
  
 
 Additional items to manually check (3)   
 
 Show Hide 
 
  
 
  
   Site works cross-browser   
     
 
  
To reach the most number of users, sites should work across every major browser. Learn more.
 
 
 
 
  
   Page transitions don't feel like they block on the network   
     
 
  
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more.
 
 
 
 
  
   Each page has a URL   
     
 
  
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more.
 
 
 
 These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.