Mobile 375 × 812

Desktop 1440 × 900

Score: 77 / 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.
Content-Security-Policy header is missing
No Content-Security-Policy header found
4 button(s) with no accessible text
143 HTTP requests — consider bundling or reducing
Cross-Origin-Embedder-Policy header is missing
[](https://beavercheck.com/results/2098308a-5706-03cf-d1ee-07a830e48312)<a href="https://beavercheck.com/results/2098308a-5706-03cf-d1ee-07a830e48312"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.meilisearch.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.meilisearch.comThis 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.
1.48 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
13.10 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.75 s
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.
6.00 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.
18.15 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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
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 | |
|---|---|---|---|
Lightning fast illustration ul.pt-16 > li.transition-200 > div.relative > img.pointer-events-none | /_next/image?url=%2F_next%2Fstatic%2Fmedia%2Ffast.cf656ef... | 19.0 KiB | 14.2 KiB |
Ultra relevant illustration ul.pt-16 > li.transition-200 > div.relative > img.pointer-events-none | /_next/image?url=%2F_next%2Fstatic%2Fmedia%2Frelevant.f36... | 18.6 KiB | 13.4 KiB |
Sonic the Hedgehog 3 li.ais-Hits-item > article.grid > div > img.row-span-2 | /_next/image?url=https%3A%2F%2Fimage.tmdb.org%2Ft%2Fp%2Fw... | 8.4 KiB | 5.8 KiB |
Red One li.ais-Hits-item > article.grid > div > img.row-span-2 | /_next/image?url=https%3A%2F%2Fimage.tmdb.org%2Ft%2Fp%2Fw... | 7.7 KiB | 5.1 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
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.
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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.meilisearch.com/_next/static/css/94e4415bea04c623.css | 20.6 KiB | 17.5 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.meilisearch.com/_next/static/chunks/9941-012c57d720027966.js | 169.0 KiB | 158.0 KiB |
| www.meilisearch.com/_next/static/chunks/pages/_app-a6e90faa0c54cfc2.js | 115.4 KiB | 82.1 KiB |
| www.googletagmanager.com/gtag/js?id=G-S0LFS24LR2&cx=c>m=4e6460 | 171.5 KiB | 68.1 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-TNSCGVBH | 161.6 KiB | 66.5 KiB |
| www.googletagmanager.com/gtag/js?id=AW-16882124252&cx=c>m=4e6460 | 142.9 KiB | 65.3 KiB |
| www.meilisearch.com/_next/static/chunks/2559-d8584a39e4d20434.js | 110.6 KiB | 56.8 KiB |
| www.meilisearch.com/_next/static/chunks/4609-596fa1c444e16eb5.js | 59.5 KiB | 37.5 KiB |
| d-code.liadm.com/did-006l.min.js | 46.4 KiB | 33.2 KiB |
| www.meilisearch.com/_next/static/chunks/2257-3db4aa1904322e89.js | 36.6 KiB | 24.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 reduce Javascript execution time.
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 | 4.3 s |
| Other | 1.1 s |
| Style & Layout | 889 ms |
| Script Parsing & Compilation | 644 ms |
| Garbage Collection | 137 ms |
| Rendering | 93 ms |
| Parse HTML & CSS | 85 ms |
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.
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 |
|---|
header.sticky > div.mx-auto > div.ml-auto > button.ml-2 header.sticky > div.mx-auto > div.ml-auto > button.ml-2 |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
Accept All div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn |
These are opportunities to improve the legibility of your content.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
| Failing Elements |
|---|
Full-text search
Leverage reliable and performant search with features like ge… div.animation-showing-rest-of-the-page > section#38 > div.mx-auto > ul.grid |
Full-text search
Leverage reliable and performant search with features like ge… section#38 > div.mx-auto > ul.grid > ul.transition-200 |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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 about the viewport meta tag.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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 |
|---|
Apps div.lg:max-w-[385px] > div > div.mx-auto > button.flex |
ecomm div.lg:max-w-[385px] > div > div.mx-auto > button.flex |
Media div.lg:max-w-[385px] > div > div.mx-auto > button.flex |
Enterprise div.lg:max-w-[385px] > div > div.mx-auto > button.flex |
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.
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.
462 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.82 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
78 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.
1.21 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.97 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 long cache lifetime can speed up repeat visits to your page. Learn more about caching.
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.
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 | |
|---|---|---|---|
Lightning fast illustration ul.pt-16 > li.transition-200 > div.relative > img.pointer-events-none | /_next/image?url=%2F_next%2Fstatic%2Fmedia%2Ffast.cf656ef... | 19.0 KiB | 14.2 KiB |
Ultra relevant illustration ul.pt-16 > li.transition-200 > div.relative > img.pointer-events-none | /_next/image?url=%2F_next%2Fstatic%2Fmedia%2Frelevant.f36... | 18.6 KiB | 14.0 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.meilisearch.com/_next/static/css/94e4415bea04c623.css | 20.6 KiB | 15.6 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.meilisearch.com/_next/static/chunks/9941-012c57d720027966.js | 168.9 KiB | 157.9 KiB |
| www.meilisearch.com/_next/static/chunks/pages/_app-a6e90faa0c54cfc2.js | 115.4 KiB | 82.0 KiB |
| www.googletagmanager.com/gtag/js?id=G-S0LFS24LR2&cx=c>m=4e6460 | 171.5 KiB | 68.1 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-TNSCGVBH | 161.6 KiB | 66.5 KiB |
| www.googletagmanager.com/gtag/js?id=AW-16882124252&cx=c>m=4e6460 | 142.9 KiB | 64.7 KiB |
| www.meilisearch.com/_next/static/chunks/2559-d8584a39e4d20434.js | 110.7 KiB | 57.5 KiB |
| www.meilisearch.com/_next/static/chunks/4609-596fa1c444e16eb5.js | 59.5 KiB | 37.5 KiB |
| d-code.liadm.com/did-006l.min.js | 46.4 KiB | 33.2 KiB |
| www.meilisearch.com/_next/static/chunks/2257-3db4aa1904322e89.js | 36.6 KiB | 24.3 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.
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.left-0 > div.flex > div.animate > button.ml-2 div.left-0 > div.flex > div.animate > button.ml-2 |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
Accept All div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn |
These are opportunities to improve the legibility of your content.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
| Failing Elements |
|---|
Full-text search
Leverage reliable and performant search with features like ge… div.animation-showing-rest-of-the-page > section#38 > div.mx-auto > ul.grid |
Full-text search
Leverage reliable and performant search with features like ge… section#38 > div.mx-auto > ul.grid > ul.transition-200 |
Multi-modal search
Expand search capabilities to include images, videos, and a… section#38 > div.mx-auto > ul.grid > ul.transition-200 |
Filtering, faceting and sorting
Build complex search interfaces with a powerfu… section#38 > div.mx-auto > ul.grid > ul.transition-200 |
Federated search
Boost user experience and result relevancy by searching acros… section#38 > div.mx-auto > ul.grid > ul.transition-200 |
Search analytics
Gain actionable insights and make data-driven decisions with … section#38 > div.mx-auto > ul.grid > ul.transition-200 |
Geosearch
Deliver location-specific results by allowing users to filter and so… section#38 > div.mx-auto > ul.grid > ul.transition-200 |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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 about the viewport meta tag.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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 |
|---|
Apps div.lg:max-w-[385px] > div > div.mx-auto > button.flex |
ecomm div.lg:max-w-[385px] > div > div.mx-auto > button.flex |
Media div.lg:max-w-[385px] > div > div.mx-auto > button.flex |
Enterprise div.lg:max-w-[385px] > div > div.mx-auto > button.flex |
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.
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