Skip to content
https://greenly.earth

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

88

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:30.41 source:map[type:text value:[unattributed]]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Vidéo YouTube Greenly div.container-x > div.h-[386px] > div.style_video_box__0Y3aW > img.style_bg-img__HnWPr
/greenly/aPrtZrpReVYa3oZr_media_bg_FR.png?auto=format%2Cc...50.1 KiB44.5 KiB
Suite climatique pour vos sujets ESG div.container-x > div.flex > a.flex > img.absolute
/greenly/aKYn0qTt2nPbajCC_ghg-bg.jpg?auto=format%2Ccompre...41.3 KiB36.3 KiB
Découvrez Greenly Pro, le global Network de Greenly div.mx-auto > div.flex > div.style_video_box__0Y3aW > img.style_bg-img__HnWPr
/greenly/aMrRxmGNHVfTPVNT_greenlypro.jpg?auto=format%2Cco...38.5 KiB30.2 KiB
Graphique leaders G2 div.[&>section:nth-child(6)]:mt-0! > section.m-2 > div.container-x > img.h-auto
/greenly/aQBXrLpReVYa3u_i_Frame1171277565.png?auto=format...19.2 KiB17.1 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: Vidéo YouTube Greenly
path: 1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,7,DIV,0,SECTION,0,DIV,1,DIV,1,DIV,0,IMG
selector: div.container-x > div.h-[386px] > div.style_video_box__0Y3aW > img.style_bg-img__HnWPr
snippet: <img alt="Vidéo YouTube Greenly" rel="preload" width="1863" height="1158" decoding="async" data-nimg="1" class="style_bg-img__HnWPr" style="color:transparent" sizes="(max-width: 768px) 100vw, (max-width: 1280px) 60vw, 720px" srcset="https://images.prismic.io/greenly/aPrtZrpReVYa3oZr_media_bg_FR.png?auto=fo…" src="https://images.prismic.io/greenly/aPrtZrpReVYa3oZr_media_bg_FR.png?auto=fo…">

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
pasdepub.greenly.earth/fgfj9n67boj69zu.js?aw=WTRQBCN600.0 s169.5 KiB
/53025viwqlcsgk9.js?id=G-19W6F3XDEC&rndma&cx=c&6&gtm=4e66t1600.0 s166.2 KiB
/41808be0-452a-4aa5-b8ef-0df6d600420c/loader.js?target_ty...7200.0 s51.4 KiB
static.cdn.prismic.io/prismic.js?repo=greenly&new=true0.0 ms9.8 KiB
sc.lfeeder.com/lftracker_v1_DzLR5a5NVlW8BoQ2.js3600.0 s11.5 KiB
bzrcdn.openai.com/sdk/oaiq.min.js14400.0 s7.6 KiB
/beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e178179150...86400.0 s11.3 KiB
try.abtasty.com/c4620fc761cf0a1226bd1dd511723a81.js21600.0 s2.4 KiB
/?sid=DzLR5a5NVlW8BoQ2&data=eyJnYVRyYWNraW5nSWRzIjpbXSwiZ...0.0 ms317 B
/tr/?ev=PageView&id=7587478201373143&eid=1782888229600.17...0.0 ms19 B

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 753 ms
URLTime Spent
greenly.earth/853 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.3 s
Other580 ms
Style & Layout219 ms
Script Parsing & Compilation194 ms
Rendering96 ms
Parse HTML & CSS63 ms
Garbage Collection36 ms

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 14.4 KiB
URLTransfer SizeEst Savings
16.6 KiB14.4 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 364.1 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/destination?id=AW-629219137&cx=c&gtm=4e66t1150.5 KiB65.1 KiB
/53025viwqlcsgk9.js?id=G-19W6F3XDEC&rndma&cx=c&6&gtm=4e66t1166.1 KiB64.7 KiB
pasdepub.greenly.earth/fgfj9n67boj69zu.js?aw=WTRQBCN169.2 KiB62.8 KiB
/sdk/8ed674730f57266b61f6474a633fe5cab3728cb9/modern/sdk....105.8 KiB58.0 KiB
greenly.earth/_next/static/chunks/45623-f36fb5122bd0e50b.js91.6 KiB54.3 KiB
greenly.earth/_next/static/chunks/27506-b85be1fa542da46a.js37.1 KiB31.8 KiB
greenly.earth/_next/static/chunks/58340-8e6a9e249cb15f5d.js83.8 KiB27.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
section.m-2 > div.container-x > div > img.max-w-full section.m-2 > div.container-x > div > img.max-w-full
greenly.cdn.prismic.io/greenly/aQjkOLpReVYa39rc_ecolipot-about.svg
Logo div.didomi-popup-container > div.didomi-popup-view > div.didomi-popup-notice-logo-container > img.didomi-popup-notice-logo
/greenly/0b1b1cf4-95f3-46de-82c9-7a2fa2f14584_Logo.svg?au...

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

●Max Potential First Input Delay 110 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,918 KiB
●User Timing marks and measures 10 user timings
●JavaScript execution time 1.1 s
●Avoid long main-thread tasks 9 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 250 ms
●Server Backend Latencies 380 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Avoid large layout shifts 5 layout shifts found
○INP breakdown
○Avoid non-composited animations
87

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
our 17 partners div.didomi-popup-notice-text-container > div.didomi-popup-notice-text > p > a.didomi-notice-view-partners-link-in-text
EcoPilot div.flex > ul.flex > li.w-full > a.group

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.style_video_box__0Y3aW > div.style_video_info__D4z7i > div.style_video_info_right__Pfi7n > h5 div.style_video_box__0Y3aW > div.style_video_info__D4z7i > div.style_video_info_right__Pfi7n > h5
div.style_video_box__0Y3aW > div.style_video_info__D4z7i > div.style_video_info_right__Pfi7n > h5 div.style_video_box__0Y3aW > div.style_video_info__D4z7i > div.style_video_info_right__Pfi7n > h5

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.m-2 > div.container-x > div > img.max-w-full section.m-2 > div.container-x > div > img.max-w-full

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.style_no_script_menu___XlnN > ul > li > a div.style_no_script_menu___XlnN > ul > li > a
div.style_no_script_menu___XlnN > ul > li > a div.style_no_script_menu___XlnN > ul > li > a
div.style_no_script_menu___XlnN > ul > li > a div.style_no_script_menu___XlnN > ul > li > a
div.style_no_script_menu___XlnN > ul > li > a div.style_no_script_menu___XlnN > ul > li > 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.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
92

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
play-icon div.flex > div.style_video_box__0Y3aW > a.style_container_bottom__x1PQG > img
/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fplay.cd5976b...541 x 48 (11.27)48 x 49 (0.98)

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
/sdk/8ed674730f57266b61f6474a633fe5cab3728cb9/modern/sdk.... line 1, col 194791
Didomi - Google Consent Mode: gtm.load event is already present in the data layer when setting default values. Ensure GTM and other Google tags are loaded after Didomi is ready for the Google Consent Mode integration to work correctly.
aplo-evnt.com/api/v1/intent_pixel/track_request?app_id=664df0f5d149d10348b6df6c
Failed to load resource: the server responded with a status of 400 ()

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 about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
pasdepub.greenly.earth/fgfj9n67boj69zu.js?aw=WTRQBCN
/53025viwqlcsgk9.js?id=G-19W6F3XDEC&rndma&cx=c&6&gtm=4e66t1
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
85

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Solutions div.flex > ul.flex > li.relative > a.group
Secteurs div.flex > ul.flex > li.relative > a.group
Ressources div.flex > ul.flex > li.relative > a.group
À propos div.flex > ul.flex > li.relative > a.group
div.container-x > div.h-[386px] > div.style_video_box__0Y3aW > a.style_container_bottom__x1PQG div.container-x > div.h-[386px] > div.style_video_box__0Y3aW > a.style_container_bottom__x1PQG
div.h-[386px] > div.style_video_box__0Y3aW > div.style_video_info__D4z7i > a.style_container_bottom__x1PQG div.h-[386px] > div.style_video_box__0Y3aW > div.style_video_info__D4z7i > a.style_container_bottom__x1PQG
play-icon div.mx-auto > div.flex > div.style_video_box__0Y3aW > a.style_container_bottom__x1PQG
div.flex > div.style_video_box__0Y3aW > div.style_video_info__D4z7i > a.style_container_bottom__x1PQG div.flex > div.style_video_box__0Y3aW > div.style_video_info__D4z7i > a.style_container_bottom__x1PQG

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.m-2 > div.container-x > div > img.max-w-full section.m-2 > div.container-x > div > img.max-w-full

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback