Skip to content
https://lovaco.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

32

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.127246] map[node:map[boundingRect:map[bottom:631 height:258 left:0 right:412 top:373 width:412] lhId:page-1-SECTION nodeLabel:body.template-index > main#main > section#shopify-section-template--14344087666790__slideshow_a9TePV path:2,HTML,1,BODY,4,MAIN,1,SECTION selector:body.template-index > main#main > section#shopify-section-template--14344087666790__slideshow_a9TePV snippet:<section id="shopify-section-template--14344087666790__slideshow_a9TePV" class="shopify-section shopify-section--stackable shopify-section--contrast offse…"> type:node] score:0.065658 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:4089 height:48 left:28 right:228 top:4041 width:200] lhId:page-10-IMG nodeLabel:div.footer__groups > div.footer__group > div.footer__group-content > img.fs-body-base path:2,HTML,1,BODY,5,FOOTER,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG selector:div.footer__groups > div.footer__group > div.footer__group-content > img.fs-body-base snippet:<img src="//lovaco.com/cdn/shop/files/lova-canna-logo-white-sm.png?v=1648146754&amp;widt…" class="fs-body-base footer__logo"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1739 height:1068 left:0 right:412 top:671 width:412] lhId:page-3-SECTION nodeLabel:body.template-index > main#main > section#shopify-section-template--14344087666790__165185775605e60f8b path:2,HTML,1,BODY,4,MAIN,2,SECTION selector:body.template-index > main#main > section#shopify-section-template--14344087666790__165185775605e60f8b snippet:<section id="shopify-section-template--14344087666790__165185775605e60f8b" class="shopify-section shopify-section--stackable shopify-section--image-first"> type:node] score:0.061588 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:4089 height:48 left:28 right:228 top:4041 width:200] lhId:page-10-IMG nodeLabel:div.footer__groups > div.footer__group > div.footer__group-content > img.fs-body-base path:2,HTML,1,BODY,5,FOOTER,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG selector:div.footer__groups > div.footer__group > div.footer__group-content > img.fs-body-base snippet:<img src="//lovaco.com/cdn/shop/files/lova-canna-logo-white-sm.png?v=1648146754&amp;widt…" class="fs-body-base footer__logo"> type:node]]] type:subitems]]]

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:4.696 source:map[column:66017 line:13 type:source-location url:https://lovaco.com/cdn/shop/t/40/assets/swiper-bundle.min.js?v=32172172898449040931660142502 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:13.444 source:map[column:7507 line:12 type:source-location url:https://lovaco.com/cdn/shop/t/40/assets/swiper-bundle.min.js?v=32172172898449040931660142502 urlProvider:network]] map[reflowTime:25.155 source:map[column:53230 line:12 type:source-location url:https://lovaco.com/cdn/shop/t/40/assets/swiper-bundle.min.js?v=32172172898449040931660142502 urlProvider:network]] map[reflowTime:0.545 source:map[column:16832 line:12 type:source-location url:https://lovaco.com/cdn/shop/t/40/assets/swiper-bundle.min.js?v=32172172898449040931660142502 urlProvider:network]] map[reflowTime:3.565 source:map[type:text value:[unattributed]]] map[reflowTime:4.093 source:map[column:45378 line:12 type:source-location url:https://lovaco.com/cdn/shop/t/40/assets/swiper-bundle.min.js?v=32172172898449040931660142502 urlProvider:network]] map[reflowTime:0.795 source:map[column:7507 line:12 type:source-location url:https://lovaco.com/cdn/shop/t/40/assets/swiper-bundle.min.js?v=32172172898449040931660142502 urlProvider:network]] map[reflowTime:0.244 source:map[column:53230 line:12 type:source-location url:https://lovaco.com/cdn/shop/t/40/assets/swiper-bundle.min.js?v=32172172898449040931660142502 urlProvider:network]] map[reflowTime:0.452 source:map[column:16832 line:12 type:source-location url:https://lovaco.com/cdn/shop/t/40/assets/swiper-bundle.min.js?v=32172172898449040931660142502 urlProvider:network]] map[reflowTime:1074.957 source:map[column:15386 line:106 type:source-location url:https://lovaco.com/cdn/shop/t/40/assets/theme-b5916edf.js urlProvider:network]] map[reflowTime:5.873 source:map[column:25808 line:138 type:source-location url:https://lovaco.com/cdn/shop/t/40/assets/theme-b5916edf.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:18.06100048828125 label:Time to first byte subpart:timeToFirstByte] map[duration:2355.185999511719 label:Resource load delay subpart:resourceLoadDelay] map[duration:58.82200048828125 label:Resource load duration subpart:resourceLoadDuration] map[duration:649.3399995117187 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div.slideshow__cell > div.slideshow__asset > div.image > img.image__img
path: 2,HTML,1,BODY,4,MAIN,1,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.slideshow__cell > div.slideshow__asset > div.image > img.image__img
snippet: <img class="image__img lazyautosizes lazyloaded" src="https://lovaco.com/cdn/shop/files/Website_Desktop_Banner-1_900x.jpg?v=1777…" data-widths="[180, 360, 540, 720, 900, 1080, 1296, 1512, 1728, 2048]" data-aspectratio="1.6" data-sizes="auto" alt="" data-srcset="//lovaco.com/cdn/shop/files/Website_Desktop_Banner-1_180x.jpg?v=1777659161…" sizes="412.8px" srcset="//lovaco.com/cdn/shop/files/Website_Desktop_Banner-1_180x.jpg?v=1777659161…">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: div.slideshow__cell > div.slideshow__asset > div.image > img.image__img
path: 2,HTML,1,BODY,4,MAIN,1,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.slideshow__cell > div.slideshow__asset > div.image > img.image__img
snippet: <img class="image__img lazyautosizes lazyloaded" src="https://lovaco.com/cdn/shop/files/Website_Desktop_Banner-1_900x.jpg?v=1777…" data-widths="[180, 360, 540, 720, 900, 1080, 1296, 1512, 1728, 2048]" data-aspectratio="1.6" data-sizes="auto" alt="" data-srcset="//lovaco.com/cdn/shop/files/Website_Desktop_Banner-1_180x.jpg?v=1777659161…" sizes="412.8px" srcset="//lovaco.com/cdn/shop/files/Website_Desktop_Banner-1_180x.jpg?v=1777659161…">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

URLResource SizeEst Savings
a.mosaic-grid__item > div.mosaic-grid__item-inner > div.image > img.image__img a.mosaic-grid__item > div.mosaic-grid__item-inner > div.image > img.image__img
lovaco.com/cdn/shop/files/we-grow-c_720x.jpg?v=1651864312100.0 KiB36.8 KiB
div.slideshow__cell > div.slideshow__asset > div.image > img.image__img div.slideshow__cell > div.slideshow__asset > div.image > img.image__img
lovaco.com/cdn/shop/files/Website_Desktop_Banner-1_900x.jpg?v=177765916188.5 KiB35.5 KiB
a.mosaic-grid__item > div.mosaic-grid__item-inner > div.image > img.image__img a.mosaic-grid__item > div.mosaic-grid__item-inner > div.image > img.image__img
lovaco.com/cdn/shop/files/we-grow-c_300x300.jpg?v=165186431225.2 KiB10.5 KiB
div.slideshow__cell > div.slideshow__asset > div.image > img.image__img div.slideshow__cell > div.slideshow__asset > div.image > img.image__img
lovaco.com/cdn/shop/files/Website_Desktop_Banner-1_300x300.jpg?v=177765916118.7 KiB9.5 KiB
Ali S. ★★★★★ div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.author-image
lovaco.com/cdn/shop/files/colfax_180X.png?v=165004766711.7 KiB7.6 KiB
Kelci P. ★★★★★ div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.author-image
lovaco.com/cdn/shop/files/aurora_180X.png?v=165004770210.7 KiB6.7 KiB
Jordan T. ★★★★★ div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.author-image
lovaco.com/cdn/shop/files/durango_180X.png?v=165004826410.6 KiB6.6 KiB
James C. ★★★★★ div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.author-image
lovaco.com/cdn/shop/files/downtown_180X.png?v=16500474609.9 KiB5.9 KiB
Diane V. ★★★★★ div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.author-image
lovaco.com/cdn/shop/files/edgewater_180X.png?v=16500483989.6 KiB5.6 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
body.template-index > main#main > section#shopify-section-template--14344087666790__slideshow_a9TePV body.template-index > main#main > section#shopify-section-template--14344087666790__slideshow_a9TePV
0.066
body.template-index > main#main > section#shopify-section-template--14344087666790__165185775605e60f8b body.template-index > main#main > section#shopify-section-template--14344087666790__165185775605e60f8b
0.062

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

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: 300 ms 33.4 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.

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.

CategoryTime Spent
Script Evaluation6.7 s
Style & Layout4.9 s
Other2.6 s
Script Parsing & Compilation438 ms
Rendering143 ms
Parse HTML & CSS106 ms
Garbage Collection72 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.footer__groups > div.footer__group > div.footer__group-content > img.fs-body-base div.footer__groups > div.footer__group > div.footer__group-content > img.fs-body-base
lovaco.com/cdn/shop/files/lova-canna-logo-white-sm.png?v=1648146754&width=200
Quote icon div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.quote
lovaco.com/cdn/shop/files/quote-60_60X.png?v=1649490028
Quote icon div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.quote
lovaco.com/cdn/shop/files/quote-60_60X.png?v=1649490028
Quote icon div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.quote
lovaco.com/cdn/shop/files/quote-60_60X.png?v=1649490028
Quote icon div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.quote
lovaco.com/cdn/shop/files/quote-60_60X.png?v=1649490028
Quote icon div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.quote
lovaco.com/cdn/shop/files/quote-60_60X.png?v=1649490028
Quote icon div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > img.quote
lovaco.com/cdn/shop/files/quote-60_60X.png?v=1649490028

More information about the performance of your application. These numbers don't directly affect the Performance score.

Document request latency
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 17 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 3 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 190 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 10 ms
INP breakdown
86

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LOVA AURORA div.swiper > div#swiper-wrapper-452b931bcda10e61a > div.swiper-slide > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer__groups > div.footer__group > div.footer__group-content > img.fs-body-base div.footer__groups > div.footer__group > div.footer__group-content > img.fs-body-base

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mosaic-grid > div.mosaic-grid__inner > div.mosaic-grid__grid > a.mosaic-grid__item div.mosaic-grid > div.mosaic-grid__inner > div.mosaic-grid__grid > a.mosaic-grid__item
div.mosaic-grid > div.mosaic-grid__inner > div.mosaic-grid__grid > a.mosaic-grid__item div.mosaic-grid > div.mosaic-grid__inner > div.mosaic-grid__grid > a.mosaic-grid__item
div.mosaic-grid > div.mosaic-grid__inner > div.mosaic-grid__grid > a.mosaic-grid__item div.mosaic-grid > div.mosaic-grid__inner > div.mosaic-grid__grid > a.mosaic-grid__item

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.

Best practices

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Move carousel to slide 1 div.slideshow > div.navigation-dots > div.navigation-dots__inner > button.navigation-dot
Move carousel to slide 2 div.slideshow > div.navigation-dots > div.navigation-dots__inner > button.navigation-dot
Go to slide 1 section.testimonial-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 section.testimonial-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 section.testimonial-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 section.testimonial-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 section.testimonial-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 section.testimonial-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet

These items highlight common accessibility best practices.

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
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
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.
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
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` 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
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
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.
Elements with visible text labels have matching accessible names.
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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 403 ()
Uses HTTPS
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 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
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
85

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.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer__groups > div.footer__group > div.footer__group-content > img.fs-body-base div.footer__groups > div.footer__group > div.footer__group-content > img.fs-body-base

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

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 are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback