Spain · Madrid Completed: Apr 12, 2026 14:06 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 72 / 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
1 control(s) without accessible label
No H1 heading found
Cookie '_d2id' is missing the HttpOnly flag
[](https://beavercheck.com/results/29c2a005-2a1a-43b0-87b5-bdb3c9d2892d)<a href="https://beavercheck.com/results/29c2a005-2a1a-43b0-87b5-bdb3c9d2892d"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mercadolibre.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mercadolibre.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.11 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.96 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
17 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.11 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.21 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.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.google-analytics.com/analytics.js | 7200.0 s | 20.9 KiB |
| static.mlstatic.com/org-img/homesnw/img/flags.png?v=3.0 | 0.0 ms | 9.7 KiB |
| http2.mlstatic.com/storage/melidata-js-sdk/js/3/last/melidata.min.js | 1800.0 s | 9.9 KiB |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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 | |
|---|---|---|---|
ul.ml-site-list > li.ml-site-mlv > a#VE > ::before ul.ml-site-list > li.ml-site-mlv > a#VE > ::before | static.mlstatic.com/org-img/homesnw/img/flags.png?v=3.0 | 8.9 KiB | 7.1 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /** * Homecom.css * Define los estilos para la home mercadolibre.com * @namespace ml */ … | 8.3 KiB | 3.8 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.googletagmanager.com/gtag/js?id=UA-80810547-1 | 123.2 KiB | 64.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.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
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 |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
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.10 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.33 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.
1.10 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.33 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.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.google-analytics.com/analytics.js | 7200.0 s | 20.9 KiB |
| static.mlstatic.com/org-img/homesnw/img/flags.png?v=3.0 | 0.0 ms | 9.7 KiB |
| http2.mlstatic.com/storage/melidata-js-sdk/js/3/last/melidata.min.js | 1800.0 s | 9.9 KiB |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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 | |
|---|---|---|---|
ul.ml-site-list > li.ml-site-mlv > a#VE > ::before ul.ml-site-list > li.ml-site-mlv > a#VE > ::before | static.mlstatic.com/org-img/homesnw/img/flags.png?v=3.0 | 8.9 KiB | 7.1 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /** * Homecom.css * Define los estilos para la home mercadolibre.com * @namespace ml */ … | 8.3 KiB | 3.8 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.googletagmanager.com/gtag/js?id=UA-80810547-1 | 123.0 KiB | 64.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.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
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 |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
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