Brazil · Sao Paulo Completed: Apr 8, 2026 14:03 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 86 / 100
Based on 8 categories, 0 sections
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
No favicon or icon links detected
Cross-Origin-Embedder-Policy header is missing
Cross-Origin-Opener-Policy header is missing
Unattributable: 481ms CPU time
https://matheo-olsen.fr/: 864ms CPU time
[](https://beavercheck.com/results/4e3abdb8-6700-44cb-9f5d-1fb500265342)<a href="https://beavercheck.com/results/4e3abdb8-6700-44cb-9f5d-1fb500265342"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmatheo-olsen.fr" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fmatheo-olsen.frThis badge auto-updates with your latest scan result.
Thanks for your feedback!
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
3.15 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.70 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
162 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.29 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
5.48 s
Audit breakdown by category with detailed findings.
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.
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.
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.
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 |
|---|---|---|
| matheo-olsen.fr/_next/static/chunks/7958e8787e722790.css | 17.7 KiB | 150 ms |
| matheo-olsen.fr/_next/static/chunks/e85767aaade4067a.css | 1.2 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
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 | 1.1 s |
| Other | 981 ms |
| Style & Layout | 351 ms |
| Script Parsing & Compilation | 166 ms |
| Rendering | 129 ms |
| Parse HTML & CSS | 78 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
| Failure reason | Failure type |
|---|---|
| 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| matheo-olsen.fr/_next/static/chunks/8f02d17ed0289fd9.js | 68.3 KiB | 24.2 KiB |
| matheo-olsen.fr/_next/static/chunks/5cf263598dde299a.js | 50.9 KiB | 22.0 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
| Failing Elements |
|---|
div.animate-fade-in-up > div.mt-8 > div.pt-2 > a.group div.animate-fade-in-up > div.mt-8 > div.pt-2 > a.group |
These items highlight common accessibility best practices.
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
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 404 () |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.74 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.74 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.05 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.
1.74 s
Audit breakdown by category with detailed findings.
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.
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.
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.
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 |
|---|---|
| matheo-olsen.fr/_next/static/chunks/7958e8787e722790.css | 17.7 KiB |
| matheo-olsen.fr/_next/static/chunks/e85767aaade4067a.css | 1.2 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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
| Failure reason | Failure type |
|---|---|
| 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| matheo-olsen.fr/_next/static/chunks/8f02d17ed0289fd9.js | 68.3 KiB | 25.1 KiB |
| matheo-olsen.fr/_next/static/chunks/5cf263598dde299a.js | 50.9 KiB | 22.7 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
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
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 404 () |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Send Feedback