Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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.

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.

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.

Request	Cache TTL	Transfer Size
/SZylnW2i/Q1o/U0g/yfIMl6TXuv/buu5zhb6XQtVGzr9Y9/fSZnAQ/Wl...	21600.0 s	178.7 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js	86400.0 s	128.4 KiB
mailchimp.com/release/plums/cxp/js/index.8ec0f68b.1.js	3600.0 s	62.6 KiB
mailchimp.com/release/plums/cxp/css/critical.ccd7080a.1.css	3600.0 s	53.2 KiB
mailchimp.com/release/plums/f503b10a8b819ad9.woff2	3600.0 s	40.6 KiB
mailchimp.com/release/plums/chunks/js/617.d16728ceeab07901.1.js	3600.0 s	38.1 KiB
/analytics.js/v1/XW9BLqe2lnNnSxE3BHbGk42LMyT7wdIf/analyti...	120.0 s	30.0 KiB
mailchimp.com/release/plums/b4358c1049ee69f4.woff2	3600.0 s	36.3 KiB
mailchimp.com/release/plums/c477e5e371f1219d.woff2	3600.0 s	35.2 KiB
mailchimp.com/release/plums/ea9371020395bcec.woff2	3600.0 s	34.5 KiB
mailchimp.com/release/plums/659baf8b2573503b.woff2	3600.0 s	32.2 KiB
mailchimp.com/release/plums/cxp/js/experiment-loader.52c71e66.1.js	3600.0 s	28.5 KiB
ob.herbgreencolumn.com/i/52a636366034da11f1359c540cba8584.js	43200.0 s	44.6 KiB
mailchimp.com/release/plums/cxp/css/below-fold.59a5b7cd.1.css	3600.0 s	16.2 KiB
mailchimp.com/release/plums/chunks/js/6651.9f18b7c12b38e2b9.1.js	3600.0 s	11.0 KiB
schema-cf.bc0a.com/corejs/be-schema-v3.js	0.0 ms	7.8 KiB
mailchimp.com/release/plums/cxp/css/page_specific/p23-less.039977e3.1.css	3600.0 s	9.1 KiB
mailchimp.com/release/plums/cxp/css/common.baa76501.1.css	3600.0 s	8.0 KiB
bat.bing.com/p/insights/s/0.8.59	86400.0 s	15.6 KiB
mailchimp.com/release/plums/chunks/js/7100.d3a7005ffd99d1cb.1.js	3600.0 s	7.8 KiB
mailchimp.com/release/plums/chunks/js/7985.85145d681b2a9a58.1.js	3600.0 s	7.7 KiB
s2.go-mpulse.net/boomerang/QAT5G-9HZLF-7EDMX-YMVCJ-QZJDA	604800.0 s	58.1 KiB
mailchimp.com/release/plums/chunks/js/1422.5dbd381bbabb27ea.1.js	3600.0 s	6.3 KiB
mailchimp.com/release/plums/chunks/js/5385.5023dc854761a818.1.js	3600.0 s	5.8 KiB
mailchimp.com/release/plums/chunks/js/4798.44f484df06d74488.1.js	3600.0 s	5.6 KiB
mailchimp.com/release/plums/chunks/js/1590.44ae13401a6e6522.1.js	3600.0 s	4.8 KiB
mailchimp.com/release/plums/chunks/js/4073.af84b0e996c9801d.1.js	3600.0 s	4.7 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
mailchimp.com/release/plums/chunks/js/4275.76287b419f920044.1.js	3600.0 s	3.6 KiB
mailchimp.com/release/plums/chunks/js/7385.aebe03774601e461.1.js	3600.0 s	3.3 KiB
/release/plums/cxp/css/presenters/modules/single_plan-les...	3600.0 s	3.2 KiB
mailchimp.com/release/plums/chunks/js/3958.3ada252604f712b4.1.js	3600.0 s	3.2 KiB
mailchimp.com/release/plums/chunks/js/3424.9094cdac60158bf0.1.js	3600.0 s	2.8 KiB
mailchimp.com/release/plums/chunks/js/2362.497d7b0126126ba7.1.js	3600.0 s	2.8 KiB
/release/dist/js-src/ecs/cookie-preferences-manager.20fc3...	3600.0 s	2.6 KiB
/release/plums/cxp/css/presenters/modules/p23_flexible_hi...	3600.0 s	2.6 KiB
mailchimp.com/release/plums/chunks/js/8343.dda4b9696987b0e7.1.js	3600.0 s	2.4 KiB
mailchimp.com/release/plums/chunks/js/7469.d76f7dbf128d1a99.1.js	3600.0 s	2.2 KiB
mailchimp.com/release/plums/chunks/js/9692.6da4fe016889b4ba.1.js	3600.0 s	2.2 KiB
mailchimp.com/release/plums/chunks/js/4683.1bd336126971ff67.1.js	3600.0 s	2.2 KiB
mailchimp.com/release/plums/chunks/js/3156.d695fc9ff6590dfc.1.js	3600.0 s	2.1 KiB
/release/plums/cxp/css/presenters/modules/p23_horizontal_...	3600.0 s	2.1 KiB
mailchimp.com/release/plums/chunks/js/3490.bc326adaa2e5c259.1.js	3600.0 s	2.0 KiB
mailchimp.com/release/plums/chunks/js/1103.4b9bd80e6ee6da32.1.js	3600.0 s	2.0 KiB
mailchimp.com/release/plums/chunks/js/9867.d975c5221e4e7f03.1.js	3600.0 s	1.9 KiB
mailchimp.com/release/plums/chunks/js/6773.529814217176400f.1.js	3600.0 s	1.9 KiB
/logos/e386905c-240c-45e6-9cba-96e9d7c4775f/4412abc8-456f...	86400.0 s	3.4 KiB
mailchimp.com/release/plums/chunks/js/7941.1a419c2d0b281956.1.js	3600.0 s	1.7 KiB
mailchimp.com/release/plums/chunks/js/7746.1b458a9abdc97c6f.1.js	3600.0 s	1.7 KiB
mailchimp.com/release/plums/chunks/js/8175.49a75e36ab551751.1.js	3600.0 s	1.6 KiB
mailchimp.com/release/plums/chunks/js/2561.3c9b430f4d0f8202.1.js	3600.0 s	1.6 KiB
mailchimp.com/release/plums/chunks/js/102.282d345da7189423.1.js	3600.0 s	1.6 KiB
mailchimp.com/release/plums/chunks/js/7163.192d2384eafbdc57.1.js	3600.0 s	1.6 KiB
mailchimp.com/release/plums/chunks/js/6482.0dcf03ed828285d5.1.js	3600.0 s	1.5 KiB
mailchimp.com/release/plums/chunks/js/1263.af23bbfd07bb8b25.1.js	3600.0 s	1.5 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.7 KiB
mailchimp.com/release/plums/chunks/js/6195.00bb071b4bee9eec.1.js	3600.0 s	1.3 KiB
mailchimp.com/release/plums/chunks/js/2130.f73af14d1d72975c.1.js	3600.0 s	1.2 KiB
/release/plums/cxp/css/presenters/modules/logo_carousel-l...	3600.0 s	1.1 KiB
/release/plums/cxp/css/presenters/modules/p23_stacking_hi...	3600.0 s	1.1 KiB
mailchimp.com/release/plums/chunks/js/9542.2bc12e721e72cacf.1.js	3600.0 s	1016 B
/metrics/a?v=3&t=l&pid=1093151587&rv=64f0&tag_exp=0~11593...	0.0 ms	645 B
mailchimp.com/release/plums/8ee5e3b5d6d68b22.svg	3600.0 s	805 B
mailchimp.com/release/plums/3579da9be0d87b6f.svg	3600.0 s	771 B
/release/plums/cxp/css/presenters/modules/dual_plan_modul...	3600.0 s	756 B
mailchimp.com/release/plums/d587a00f04ec1dd3.svg	3600.0 s	756 B
mailchimp.com/release/plums/a1523f19694530bd.svg	3600.0 s	750 B
mailchimp.com/release/plums/8bd102bdbaf56447.svg	3600.0 s	739 B
/release/dist/js-src/ecs/cookie-preferences-manager.20fc3...	3600.0 s	0 B

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

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

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.

	URL	Resource Size	Est Savings
div.module--content > div.imageContainer > picture > img `div.module--content > div.imageContainer > picture > img`	/ctf/images/yzco4xsimv0y/704aBG4uuF1aALJjQzDjHr/3ef708887...	26.0 KiB	20.4 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.

URL	Transfer Size
mailchimp.com/ex.js	1021 B
mailchimp.com/release/plums/cxp/js/experiment-loader.52c71e66.1.js	28.5 KiB
/release/plums/cxp/css/presenters/modules/logo_carousel-l...	1.1 KiB
/release/plums/cxp/css/presenters/modules/p23_stacking_hi...	1.1 KiB
mailchimp.com/release/plums/cxp/css/page_specific/p23-less.039977e3.1.css	9.1 KiB
/release/plums/cxp/css/presenters/modules/p23_horizontal_...	2.1 KiB
/release/plums/cxp/css/presenters/modules/p23_flexible_hi...	2.6 KiB
/release/plums/cxp/css/presenters/modules/single_plan-les...	3.2 KiB
/release/plums/cxp/css/presenters/modules/dual_plan_modul...	756 B

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: 255 ms

URL	Time Spent
mailchimp.com/	255 ms
mailchimp.com/es/	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.

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 84.8 KiB

URL	Transfer Size	Est Savings
mailchimp.com/release/plums/cxp/css/critical.ccd7080a.1.css	52.6 KiB	49.0 KiB
	24.8 KiB	21.6 KiB
mailchimp.com/release/plums/cxp/css/below-fold.59a5b7cd.1.css	15.6 KiB	14.3 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 797.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-N5HD1RTH6E	175.0 KiB	115.6 KiB
accounts.google.com/gsi/client	95.4 KiB	79.6 KiB
mailchimp.com/metrics/gtd?id=G-N5HD1RTH6E&cx=c&gtm=4e64f0h1	182.4 KiB	73.5 KiB
mailchimp.com/metrics/?id=GTM-5XRCGV8&gtm=4e64f0h1	135.7 KiB	69.4 KiB
mailchimp.com/metrics/?id=GTM-59GS5R2&gtm=4e64f0h1	135.9 KiB	69.0 KiB
mailchimp.com/metrics/?id=AW-947197597&cx=c&gtm=4e64f0h1	152.6 KiB	67.1 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js	128.2 KiB	67.1 KiB
mailchimp.com/metrics/?id=	222.5 KiB	66.9 KiB
mailchimp.com/metrics/?id=DC-9894771&cx=c&gtm=4e64f0h1	140.7 KiB	64.0 KiB
/SZylnW2i/Q1o/U0g/yfIMl6TXuv/buu5zhb6XQtVGzr9Y9/fSZnAQ/Wl...	177.6 KiB	37.9 KiB
plugin.intuitcdn.net/web-shell/5.60.1/integration/3935.js	39.4 KiB	33.3 KiB
mailchimp.com/release/plums/cxp/js/index.8ec0f68b.1.js	62.0 KiB	30.8 KiB
s2.go-mpulse.net/boomerang/QAT5G-9HZLF-7EDMX-YMVCJ-QZJDA	58.0 KiB	23.2 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
mailchimp.com/es/	475 ms	12 ms	2.5 ms
Unattributable	282 ms	27 ms	0.0 ms
mailchimp.com/metrics/?id=	252 ms	230 ms	18 ms
/SZylnW2i/Q1o/U0g/yfIMl6TXuv/buu5zhb6XQtVGzr9Y9/fSZnAQ/Wl...	245 ms	224 ms	15 ms
ob.herbgreencolumn.com/i/52a636366034da11f1359c540cba8584.js	182 ms	138 ms	3.0 ms
s2.go-mpulse.net/boomerang/QAT5G-9HZLF-7EDMX-YMVCJ-QZJDA	150 ms	40 ms	4.7 ms
mailchimp.com/release/plums/cxp/js/index.8ec0f68b.1.js	148 ms	123 ms	4.7 ms
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js	129 ms	100 ms	15 ms
mailchimp.com/release/plums/chunks/js/7100.d3a7005ffd99d1cb.1.js	108 ms	103 ms	1.0 ms
/ct?id=40275&url=https%3A%2F%2Fmailchimp.com%2Fes%2F%3Fcu...	105 ms	101 ms	0.4 ms
mailchimp.com/metrics/?id=AW-947197597&cx=c&gtm=4e64f0h1	80 ms	67 ms	12 ms
mailchimp.com/metrics/gtd?id=G-N5HD1RTH6E&cx=c&gtm=4e64f0h1	74 ms	61 ms	13 ms
mailchimp.com/metrics/?id=DC-9894771&cx=c&gtm=4e64f0h1	69 ms	60 ms	8.0 ms
plugin.intuitcdn.net/web-shell/5.60.1/integration/2034.js	65 ms	59 ms	2.5 ms
mailchimp.com/release/plums/chunks/js/3156.d695fc9ff6590dfc.1.js	53 ms	41 ms	0.1 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.7 s
Other	505 ms
Style & Layout	233 ms
Script Parsing & Compilation	177 ms
Rendering	161 ms
Garbage Collection	37 ms
Parse HTML & CSS	36 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
mailchimp.com/metrics/?id=	222.8 KiB
mailchimp.com/metrics/gtd?id=G-N5HD1RTH6E&cx=c&gtm=4e64f0h1	183.0 KiB
/SZylnW2i/Q1o/U0g/yfIMl6TXuv/buu5zhb6XQtVGzr9Y9/fSZnAQ/Wl...	178.7 KiB
www.googletagmanager.com/gtag/js?id=G-N5HD1RTH6E	175.1 KiB
mailchimp.com/metrics/?id=AW-947197597&cx=c&gtm=4e64f0h1	152.9 KiB
mailchimp.com/metrics/?id=DC-9894771&cx=c&gtm=4e64f0h1	141.0 KiB
mailchimp.com/metrics/?id=GTM-59GS5R2&gtm=4e64f0h1	136.2 KiB
mailchimp.com/metrics/?id=GTM-5XRCGV8&gtm=4e64f0h1	136.0 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js	128.4 KiB
accounts.google.com/gsi/client	96.2 KiB

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

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 280 user timings

●Avoid long main-thread tasks 10 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 120 ms

●Server Backend Latencies 290 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

100

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Iniciar prueba gratis `div.singlePlanCard__column > div.ctaBuyNowWrapper > div.margin--bottom-c3 > a.ctaBuyNow`
Conozca más `div.stackingHighlight__block > div.stackingHighlight__block__media > div.flex > a.ctaArrow`
Cookie Statement. `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

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

●Select elements have associated label elements.

●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

●Elements with the `role=text` attribute do not have focusable descendents.

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

●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

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
mailchimp.com/es/help/about-sms-marketing/	aquí
cookiepedia.co.uk/giving-consent-to-cookies	More information

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
details#languagePicker-378616871 > ul.details__menu__container > li.menu__bumper > a.menu__bumper-first `details#languagePicker-378616871 > ul.details__menu__container > li.menu__bumper > a.menu__bumper-first`
details#languagePicker-378616871 > ul.details__menu__container > li.menu__bumper > a.menu__bumper-last `details#languagePicker-378616871 > ul.details__menu__container > li.menu__bumper > a.menu__bumper-last`
details#languagePicker-789808314 > ul.details__menu__container > li.menu__bumper > a.menu__bumper-first `details#languagePicker-789808314 > ul.details__menu__container > li.menu__bumper > a.menu__bumper-first`
details#languagePicker-789808314 > ul.details__menu__container > li.menu__bumper > a.menu__bumper-last `details#languagePicker-789808314 > ul.details__menu__container > li.menu__bumper > a.menu__bumper-last`

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

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`