C — https://www.mistral.ai | BeaverCheck Audit

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 button(s) with no accessible text

Accessibility › Link & Button Quality

4 image-only link(s) without alt text

Accessibility › Link & Button Quality

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mistral.ai)](https://beavercheck.com/results/42ebf1f8-09de-e955-4677-3cfb1634e9c9)

HTML

<a href="https://beavercheck.com/results/42ebf1f8-09de-e955-4677-3cfb1634e9c9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mistral.ai" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mistral.ai

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

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.

2.21 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.08 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2.02 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.64 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.

12.94 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

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

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

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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:72.226 source:map[type:text value:[unattributed]]]]

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.

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

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

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.

URL	Transfer Size	Duration
/_next/static/chunks/0tyr.u-akm8m0.css?dpl=b2bf46033d11da...	34.8 KiB	300 ms
/_next/static/chunks/0ojimrc6cqe8n.css?dpl=b2bf46033d11da...	3.9 KiB
/_next/static/chunks/0hepg41p_n0wp.css?dpl=b2bf46033d11da...	2.1 KiB

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

Request	Cache TTL	Transfer Size
static.axept.io/sdk.js	0.0 ms	181.5 KiB
mistral.ai/.netlify/scripts/rum	14400.0 s	4.3 KiB
/fonts.googleapis.com/css?family=Source%20Sans%203:regula...	86400.0 s	1.4 KiB

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

	URL	Resource Size	Est Savings
Stellantis `div.flex > div.min-w-0 > div.absolute > img.opacity-80`	/_next/image?url=https%3A%2F%2Fcms.mistral.ai%2Fassets%2F...	43.0 KiB	25.2 KiB
ASML `div.flex > div.min-w-0 > div.absolute > img.opacity-80`	/_next/image?url=https%3A%2F%2Fcms.mistral.ai%2Fassets%2F...	39.1 KiB	21.8 KiB
CMA CGM `div.flex > div.min-w-0 > div.absolute > img.opacity-80`	/_next/image?url=https%3A%2F%2Fcms.mistral.ai%2Fassets%2F...	36.4 KiB	18.5 KiB
div.logoloop__track > ul.logoloop__list > li.logoloop__item > img `div.logoloop__track > ul.logoloop__list > li.logoloop__item > img`	/_next/image?url=https%3A%2F%2Fcms.mistral.ai%2Fassets%2F...	17.1 KiB	15.1 KiB
div.logoloop__track > ul.logoloop__list > li.logoloop__item > img `div.logoloop__track > ul.logoloop__list > li.logoloop__item > img`	/_next/image?url=https%3A%2F%2Fcms.mistral.ai%2Fassets%2F...	15.0 KiB	14.7 KiB
Hero background `main.dark:bg-background > div.relative > div.absolute > img.size-full`	/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fmistral-fron...	23.5 KiB	11.0 KiB
div.sc-gVgoRu > button#axeptio_main_button > img `div.sc-gVgoRu > button#axeptio_main_button > img`	/2025/03/1bada10b-87b2-4bb0-a129-e04373e3d7bc.png?auto=fo...	4.3 KiB	4.0 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.

Estimated savings: 803 ms

URL	Time Spent
www.mistral.ai/	803 ms
mistral.ai/	0.0 ms

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.

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.

TTI

Diagnostics

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

Estimated savings: 150 ms 1021.0 KiB

URL	Transfer Size	Est Savings
/_next/static/chunks/0fqrfvj8lo92e.js?dpl=b2bf46033d11dac...	264.5 KiB	263.9 KiB
/_next/static/chunks/0ixzxbrlwvkb_.js?dpl=b2bf46033d11dac...	183.0 KiB	179.4 KiB
/_next/static/chunks/0498v922jg.9a.js?dpl=b2bf46033d11dac...	130.6 KiB	130.4 KiB
/_next/static/chunks/0nafd8md.jk3n.js?dpl=b2bf46033d11dac...	96.1 KiB	91.0 KiB
static.axept.io/sdk.js	181.1 KiB	72.6 KiB
www.googletagmanager.com/gtag/js?id=G-V0SRTQLQ82&cx=c&gtm=4e6460h1	175.2 KiB	70.2 KiB
/_next/static/chunks/0jlp7q_dh8pdr.js?dpl=b2bf46033d11dac...	117.7 KiB	66.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-T8R6SXZ4	125.6 KiB	62.8 KiB
/_next/static/chunks/14ar.s0-uvwx5.js?dpl=b2bf46033d11dac...	63.4 KiB	37.1 KiB
/_next/static/chunks/0jv_pm0_h6kja.js?dpl=b2bf46033d11dac...	26.0 KiB	25.8 KiB
/_next/static/chunks/0~itrr-_l-xgq.js?dpl=b2bf46033d11dac...	39.2 KiB	21.1 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.

URL	Total CPU Time	Script Evaluation	Script Parse
mistral.ai/	1.2 s	147 ms	72 ms
/_next/static/chunks/0jlp7q_dh8pdr.js?dpl=b2bf46033d11dac...	1.1 s	843 ms	75 ms
/_next/static/chunks/0ixzxbrlwvkb_.js?dpl=b2bf46033d11dac...	941 ms	177 ms	115 ms
Unattributable	918 ms	28 ms	0.0 ms
static.axept.io/sdk.js	741 ms	615 ms	105 ms
www.googletagmanager.com/gtag/js?id=G-V0SRTQLQ82&cx=c&gtm=4e6460h1	509 ms	377 ms	128 ms
/_next/static/chunks/00cw3d0rb0yl3.js?dpl=b2bf46033d11dac...	384 ms	364 ms	20 ms
www.googletagmanager.com/gtm.js?id=GTM-T8R6SXZ4	255 ms	191 ms	29 ms
/_next/static/chunks/08ury25dtt1uc.js?dpl=b2bf46033d11dac...	227 ms	128 ms	19 ms
/_next/static/chunks/0~itrr-_l-xgq.js?dpl=b2bf46033d11dac...	202 ms	71 ms	15 ms
/_next/static/chunks/0fqrfvj8lo92e.js?dpl=b2bf46033d11dac...	110 ms	1.6 ms	108 ms
/_next/static/chunks/0498v922jg.9a.js?dpl=b2bf46033d11dac...	72 ms	2.5 ms	68 ms
/_next/static/chunks/14ar.s0-uvwx5.js?dpl=b2bf46033d11dac...	53 ms	1.3 ms	51 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

Category	Time Spent
Script Evaluation	3.0 s
Other	1.9 s
Script Parsing & Compilation	880 ms
Style & Layout	717 ms
Parse HTML & CSS	207 ms
Rendering	175 ms
Garbage Collection	30 ms

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

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 2,037 KiB

●User Timing marks and measures 6 user timings

●Avoid long main-thread tasks 18 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 360 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

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.

Failing Elements
Why Mistral `div.flex > nav.grid > div.flex > h3.pointer-events-none`
Explore `div.flex > nav.grid > div.flex > h3.pointer-events-none`
Build `div.flex > nav.grid > div.flex > h3.pointer-events-none`
Legal `div.flex > nav.grid > div.flex > h3.pointer-events-none`

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.

Failing Elements
Your AI future belongs in your hands. `div.relative > div.container > div.h-[360px] > h3.heading-3`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
Discover more `div.z-10 > div.container > a.mx-auto > button.inline-flex`
View open roles `div.relative > div.relative > a > button.inline-flex`
Start building with Mistral AI `div.relative > div.flex > a > button.inline-flex`
Talk to an expert `div.relative > div.flex > a > button.inline-flex`
No, thanks `div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_dismiss`
Manage preferences `div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_configure`
Cookies `div.sc-gVgoRu > button#axeptio_main_button`

○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

●Image elements have `[alt]` attributes

●`[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

●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

●Links have a discernible name

●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.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○Form elements have associated labels

○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.

○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.

100

Best Practices

General

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.

URL	Map URL
/_next/static/chunks/0ixzxbrlwvkb_.js?dpl=b2bf46033d11dac...
/_next/static/chunks/0fqrfvj8lo92e.js?dpl=b2bf46033d11dac...
static.axept.io/sdk.js	static.axept.io/sdk.js.map

●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

●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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

100

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.

○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

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

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.

893 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.64 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

163 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.008

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.24 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.

3.49 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

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

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:60.661 source:map[type:text value:[unattributed]]]]

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.

title: Preconnected origins

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

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.

URL	Transfer Size	Duration
/_next/static/chunks/0ojimrc6cqe8n.css?dpl=b2bf46033d11da...	5.3 KiB	246 ms
/_next/static/chunks/0hepg41p_n0wp.css?dpl=b2bf46033d11da...	3.6 KiB	246 ms
/_next/static/chunks/0tyr.u-akm8m0.css?dpl=b2bf46033d11da...	36.0 KiB	180 ms

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

Request	Cache TTL	Transfer Size
static.axept.io/sdk.js	0.0 ms	181.5 KiB
mistral.ai/.netlify/scripts/rum	14400.0 s	4.3 KiB
/fonts.googleapis.com/css?family=Source%20Sans%203:regula...	86400.0 s	1.4 KiB

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

	URL	Resource Size	Est Savings
Stellantis `div.flex > div.min-w-0 > div.absolute > img.opacity-80`	/_next/image?url=https%3A%2F%2Fcms.mistral.ai%2Fassets%2F...	333.7 KiB	141.3 KiB
ASML `div.flex > div.min-w-0 > div.absolute > img.opacity-80`	/_next/image?url=https%3A%2F%2Fcms.mistral.ai%2Fassets%2F...	136.5 KiB	49.8 KiB
CMA CGM `div.flex > div.min-w-0 > div.absolute > img.opacity-80`	/_next/image?url=https%3A%2F%2Fcms.mistral.ai%2Fassets%2F...	115.7 KiB	41.0 KiB
Hero background `main.dark:bg-background > div.relative > div.absolute > img.size-full`	/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fmistral-fron...	46.9 KiB	12.4 KiB
div.logoloop__track > ul.logoloop__list > li.logoloop__item > img `div.logoloop__track > ul.logoloop__list > li.logoloop__item > img`	/_next/image?url=https%3A%2F%2Fcms.mistral.ai%2Fassets%2F...	10.0 KiB	6.2 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.

Estimated savings: 257 ms

URL	Time Spent
www.mistral.ai/	257 ms
mistral.ai/	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.

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.

Diagnostics

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

Estimated savings: 200 ms 1020.9 KiB

URL	Transfer Size	Est Savings
/_next/static/chunks/0fqrfvj8lo92e.js?dpl=b2bf46033d11dac...	264.5 KiB	263.9 KiB
/_next/static/chunks/0ixzxbrlwvkb_.js?dpl=b2bf46033d11dac...	183.2 KiB	179.6 KiB
/_next/static/chunks/0498v922jg.9a.js?dpl=b2bf46033d11dac...	130.7 KiB	130.5 KiB
/_next/static/chunks/0nafd8md.jk3n.js?dpl=b2bf46033d11dac...	95.8 KiB	90.7 KiB
static.axept.io/sdk.js	181.1 KiB	72.5 KiB
www.googletagmanager.com/gtag/js?id=G-V0SRTQLQ82&cx=c&gtm=4e6460	175.2 KiB	70.2 KiB
/_next/static/chunks/0jlp7q_dh8pdr.js?dpl=b2bf46033d11dac...	117.8 KiB	66.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-T8R6SXZ4	125.6 KiB	62.8 KiB
/_next/static/chunks/14ar.s0-uvwx5.js?dpl=b2bf46033d11dac...	63.4 KiB	37.1 KiB
/_next/static/chunks/0jv_pm0_h6kja.js?dpl=b2bf46033d11dac...	26.0 KiB	25.8 KiB
/_next/static/chunks/0~itrr-_l-xgq.js?dpl=b2bf46033d11dac...	39.3 KiB	21.3 KiB

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

Category	Time Spent
Script Evaluation	883 ms
Other	638 ms
Script Parsing & Compilation	235 ms
Style & Layout	170 ms
Rendering	57 ms
Parse HTML & CSS	44 ms

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

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 2,589 KiB

●User Timing marks and measures 6 user timings

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 5 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 50 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 40 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Failing Elements
Products `div.px-4 > div.flex > nav.hidden > button.group`
Solutions `div.px-4 > div.flex > nav.hidden > a.group`
Research `div.px-4 > div.flex > nav.hidden > a.group`
Blog `div.px-4 > div.flex > nav.hidden > a.group`
Customers `div.px-4 > div.flex > nav.hidden > a.group`
Company `div.px-4 > div.flex > nav.hidden > button.group`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.

Failing Elements
div.flex > div.relative > div.group > button.size-9 `div.flex > div.relative > div.group > button.size-9`

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.

Failing Elements
Why Mistral `div.flex > nav.grid > div.flex > h3.pointer-events-none`
Explore `div.flex > nav.grid > div.flex > h3.pointer-events-none`
Build `div.flex > nav.grid > div.flex > h3.pointer-events-none`
Legal `div.flex > nav.grid > div.flex > h3.pointer-events-none`

These are opportunities to improve the legibility of your content.

Navigation

Failing Elements
Your AI future belongs in your hands. `div.relative > div.container > div.h-[360px] > h3.heading-3`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
Discover more `div.z-10 > div.container > a.mx-auto > button.inline-flex`
View open roles `div.relative > div.relative > a > button.inline-flex`
Start building with Mistral AI `div.relative > div.flex > a > button.inline-flex`
Talk to an expert `div.relative > div.flex > a > button.inline-flex`
No, thanks `div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_dismiss`
Manage preferences `div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_configure`
Cookies `div.sc-gVgoRu > button#axeptio_main_button`

○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

●`[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

●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

●Links have a discernible name

●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.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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.

○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

○Form elements have associated labels

○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.

○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.

100

Best Practices

General

URL	Map URL
/_next/static/chunks/0ixzxbrlwvkb_.js?dpl=b2bf46033d11dac...
/_next/static/chunks/0fqrfvj8lo92e.js?dpl=b2bf46033d11dac...
static.axept.io/sdk.js	static.axept.io/sdk.js.map

●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

●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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

100

SEO

○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

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.mistral.ai

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Navigation

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Names and labels

Contrast

Navigation

Best Practices

General

SEO

Keyboard Shortcuts