Skip to content
https://www.climeup.ai

Lighthouse Mobile

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

Detailed Report

Audit breakdown by category with detailed findings.

81

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.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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.

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
Chromewell div.MuiBox-root > div.MuiStack-root > div.MuiStack-root > img
/_next/image?url=%2F_next%2Fstatic%2Fmedia%2FChromewell.4...10.3 KiB7.1 KiB
ipack_logo div.MuiBox-root > div.MuiStack-root > div.MuiStack-root > img
/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fipack-logo-f...11.6 KiB5.9 KiB
MethaPressing div.MuiBox-root > div.MuiStack-root > div.MuiStack-root > img
/_next/image?url=%2F_next%2Fstatic%2Fmedia%2FMethaPressin...7.0 KiB4.1 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 914 ms
URLTime Spent
www.climeup.ai/914 ms
www.climeup.ai/en0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.9 s
Other547 ms
Style & Layout377 ms
Script Parsing & Compilation203 ms
Rendering104 ms
Garbage Collection63 ms
Parse HTML & CSS61 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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.

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

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,119 KiB
●Avoid long main-thread tasks 11 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 190 ms
●Server Backend Latencies 1,020 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 500 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
86

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > button.MuiButtonBase-root div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > button.MuiButtonBase-root
div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > button.MuiButtonBase-root div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > button.MuiButtonBase-root
form#cbam-calculator > div.MuiStack-root > div.MuiStack-root > button.MuiButtonBase-root form#cbam-calculator > div.MuiStack-root > div.MuiStack-root > button.MuiButtonBase-root
body > div > button.MuiButtonBase-root body > div > button.MuiButtonBase-root

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.

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
Calculate your CBAM cost exposure with the ClimeUp CBAM ® Calculator. section.MuiStack-root > div.MuiStack-root > div.MuiStack-root > p.MuiTypography-root
TALK TO CBAM EXPERTS div.MuiStack-root > a > div > button.MuiButtonBase-root
Calculate CBAM Cost div.MuiStack-root > form#cbam-calculator > div.MuiStack-root > button.MuiButtonBase-root
We guide your team with right strategies and tools to meet the ESG Reporting ma… div.MuiStack-root > section.MuiStack-root > div.MuiStack-root > p.MuiTypography-root
Learn More div > div.MuiPaper-root > div.MuiStack-root > button.MuiButtonBase-root
Learn More div > div.MuiPaper-root > div.MuiStack-root > button.MuiButtonBase-root
Learn More div > div.MuiPaper-root > div.MuiStack-root > button.MuiButtonBase-root
Learn More div > div.MuiPaper-root > div.MuiStack-root > button.MuiButtonBase-root
Accelerate your sustainability journey with expert-designed tools for ESG repor… div.MuiStack-root > section.MuiStack-root > div.MuiStack-root > p.MuiTypography-root
Assess ol.MuiStack-root > li > button.MuiButtonBase-root > span.MuiTypography-root
Learn More div.MuiGrid-root > div.MuiPaper-root > div.MuiStack-root > button.MuiButtonBase-root
Accelerate your sustainability journey with expert-designed tools for ESG repor… div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > p.MuiTypography-root
Corporate Carbon Footprint (CCF) div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Decarbonization & Net Zero Advisory div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
ESG Reporting div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Materiality Risk Assessments div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Product Carbon Footprint (PCF) div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Life Cycle Assessment (LCA) div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Environmental Product Declaration (EPD) div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Product Traceability div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Supplier Due Diligence div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Scope 3 Emissions div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Value Chain Mapping div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
EcoVadis / amfori Assessment div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
CDP Reporting div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
SBTi Commitment Validation div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
EU CBAM Reporting div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
BRSR Reporting div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
GRI Reporting div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
EUDR Reporting div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
CSRD Reporting div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
IFRS S1 & S2 Reporting div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
ClimeUp GHG div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
ClimeUp Water div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
ClimeUp ESG div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
ClimeUp IMPACT div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
ClimeUp PCF div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
ClimeUp SupplyChain360 div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
ClimeUp CBAM div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
ClimeUp EUDR div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Automotive div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Steel & Aluminium div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Packaging div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Real Estate & Construction div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Agriculture div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Transportation & Logistics div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Pharmaceuticals & Healthcare div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Machinery & Components div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
IT Companies & Data Centers div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Mining & Metals div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Cement & Building Materials div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
C-Suite Executives div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Company Secretary / General Counsel div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
HR Director / CHRO div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Operations / Plant Manager div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Sustainability Manager / ESG Lead div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
General Manager / BU Head div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
EHS / Compliance Officer div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Procurement & Supply Chain Manager div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Europe (CSRD, CBAM, EUDR) div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
North America (SEC, SB 253/261) div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Latin America div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Asia-Pacific div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Middle East & Africa div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
About Us div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Team div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
People & Culture div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Our Sustainability div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Office Locations div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Jobs div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Internships div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Contact IR div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
Email Alerts div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
FAQ div.MuiStack-root > ul.MuiStack-root > a > p.MuiTypography-root
© 2026 Climeup. All rights reserved. div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > p.MuiTypography-root

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
CBAM Cost Calculator div.MuiStack-root > div.MuiStack-root > form#cbam-calculator > h5.MuiTypography-root
ClimeUp div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > h6.MuiTypography-root

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Corporate Carbon Footprint (CCF) Decarbonization & Net Zero Advisory ESG Repo… div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > ul.MuiStack-root
ClimeUp GHG ClimeUp Water ClimeUp ESG ClimeUp IMPACT ClimeUp PCF ClimeUp S… div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > ul.MuiStack-root
Automotive Steel & Aluminium Packaging Real Estate & Construction Agricultu… div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > ul.MuiStack-root
About Us Team People & Culture Our Sustainability Office Locations Jobs I… div.MuiStack-root > div.MuiStack-root > div.MuiStack-root > ul.MuiStack-root

These are opportunities to improve the experience of reading tabular or list data using 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
●Image elements have `[alt]` attributes
●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.
●ARIA attributes are used as specified for the element's role
●`[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
●Links have a discernible name
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○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.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
58

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 are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
head > meta
https://www.climeup.ai/robots.txt

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 about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
4Sitemap: /sitemap.xmlInvalid sitemap URL

To appear in search results, crawlers need access to your app.

○Structured data is valid
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback