Skip to content
https://magicmotorsport.shop

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.

52

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.

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.

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.

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:46.614 source:map[column:36 line:1729 type:source-location url:https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/requirejs/require.js 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:3.405 source:map[column:15960 line:16 type:source-location url:https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/owl.carousel/owl.carousel.min.js urlProvider:network]] map[reflowTime:36.511 source:map[column:24 line:9791 type:source-location url:https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/jquery.js urlProvider:network]] map[reflowTime:4.814 source:map[column:27 line:6442 type:source-location url:https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/jquery.js urlProvider:network]] map[reflowTime:0.587 source:map[column:40 line:6295 type:source-location url:https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/jquery.js urlProvider:network]] map[reflowTime:0.362 source:map[column:61 line:6303 type:source-location url:https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/jquery.js urlProvider:network]] map[reflowTime:0.332 source:map[column:55 line:6314 type:source-location url:https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/jquery.js urlProvider:network]] map[reflowTime:0.187 source:map[column:63 line:6442 type:source-location url:https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/jquery.js urlProvider:network]] map[reflowTime:0.416 source:map[column:66 line:6404 type:source-location url:https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/jquery.js urlProvider:network]] map[reflowTime:0.27 source:map[type:text value:[unattributed]]]]

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-DIV
nodeLabel: MECHATRONIC SOLUTIONS FOR AUTOMOTIVE WORKSHOPS And more... Offers 430€ OFF Th…
path: 1,HTML,1,BODY,6,DIV,1,MAIN,2,DIV,0,DIV,3,DIV,1,DIV
selector: div.columns > div.column > div > div.homepage-banner
snippet: <div class="homepage-banner">

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
value: no origins were preconnected
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
value: No additional origins are good candidates for preconnecting

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
div.owl-item > div.item > div.slider-bg > img div.owl-item > div.item > div.slider-bg > img
magicmotorsport.shop/media/trootech/slider/d/y/dynomag-hub-homeshop.pg_7_1_2.jpg38.3 KiB31.0 KiB
div.slider-content > div.row > div.col-6 > img.slider-logo div.slider-content > div.row > div.col-6 > img.slider-logo
magicmotorsport.shop/media/trootech/slider/l/o/logomark-dyno_3.png25.5 KiB25.5 KiB
div.owl-item > div.item > div.slider-bg > img div.owl-item > div.item > div.slider-bg > img
magicmotorsport.shop/media/trootech/slider/s/t/stagex-super-promo-shop.jpg22.6 KiB18.3 KiB
div.owl-item > div.item > div.slider-bg > img div.owl-item > div.item > div.slider-bg > img
magicmotorsport.shop/media/trootech/slider/f/r/fryon-home-shop.jpg22.5 KiB18.3 KiB
div.owl-item > div.item > div.slider-bg > img div.owl-item > div.item > div.slider-bg > img
/media/trootech/slider/i/x/ixi-personal-flasher-micro-sla...21.1 KiB17.1 KiB
CAT_KC div.owl-stage > div.owl-item > div.item > img
/media/wysiwyg/smartwave/porto/homepage/brands/carlab-imm...16.0 KiB15.5 KiB
div.owl-item > div.item > div.slider-bg > img div.owl-item > div.item > div.slider-bg > img
magicmotorsport.shop/media/trootech/slider/h/o/home-slider-flex_5.jpg17.7 KiB14.4 KiB
CAT_KC div.owl-stage > div.owl-item > div.item > img
magicmotorsport.shop/media/wysiwyg/smartwave/porto/homepage/brands/mbe.png8.2 KiB7.8 KiB
CAT_KC div.owl-stage > div.owl-item > div.item > img
magicmotorsport.shop/media/wysiwyg/smartwave/porto/homepage/brands/xhorse.png7.4 KiB7.0 KiB
div.slider-content > div.row > div.col-6 > img.slider-logo div.slider-content > div.row > div.col-6 > img.slider-logo
magicmotorsport.shop/media/trootech/slider/3/0/30-yeaes_2.png6.8 KiB6.5 KiB
div.slider-content > div.row > div.col-6 > img.slider-logo div.slider-content > div.row > div.col-6 > img.slider-logo
magicmotorsport.shop/media/trootech/slider/s/t/stagex_1.png6.9 KiB6.4 KiB
IXI Bike Personal Flasher: only 99 euros to tune your bike via OBD div.product-item-info > div.product-item-photo > a > img.product-image-photo
/media/catalog/product/cache/21ea9f3fcf5697b9ea811248899a...13.8 KiB6.2 KiB
div.slider-content > div.row > div.col-6 > img.slider-logo div.slider-content > div.row > div.col-6 > img.slider-logo
magicmotorsport.shop/media/trootech/slider/i/x/ixi-logo-white.png4.1 KiB4.1 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 654 ms
URLTime Spent
magicmotorsport.shop/754 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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 11.7 KiB
URLTransfer SizeEst Savings
/static/version1786090959/_cache/merged/9e125d34b3c3d1a6d...152.9 KiB11.7 KiB

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.

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 Evaluation4.1 s
Other1.9 s
Script Parsing & Compilation631 ms
Style & Layout620 ms
Parse HTML & CSS206 ms
Garbage Collection136 ms
Rendering132 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 205.7 KiB
URLTransfer SizeEst Savings
/static/version1786090959/frontend/Smartwave/porto_child/...88.9 KiB57.6 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...75.4 KiB43.7 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...20.9 KiB14.6 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...19.3 KiB10.9 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...17.9 KiB8.9 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...14.4 KiB7.9 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...13.4 KiB6.0 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...9.9 KiB5.0 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...9.0 KiB4.9 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...7.7 KiB4.6 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...7.1 KiB3.8 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...7.8 KiB3.7 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...6.8 KiB3.6 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...6.2 KiB3.3 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...5.4 KiB3.1 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...7.3 KiB3.1 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...3.9 KiB2.6 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...4.7 KiB2.6 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...4.6 KiB2.5 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...3.2 KiB2.4 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...5.5 KiB2.2 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...4.1 KiB2.2 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...3.1 KiB2.2 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...3.7 KiB2.1 KiB
/static/version1786090959/frontend/Smartwave/porto_child/...3.0 KiB2.1 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.

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
logo div.block-content > p.footer-logo > a > img
/static/version1786090959/frontend/Smartwave/porto_child/...
send div.control > button.subscribe > span > img
/static/version1786090959/frontend/Smartwave/porto_child/...
Shop ul > li.ui-menu-item > a.level-top > img.menu-thumb-icon
/static/version1786090959/frontend/Smartwave/porto_child/...

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

●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Avoid long main-thread tasks 20 long tasks found
●Network Requests
●Network Round Trip Times 150 ms
●Server Backend Latencies 640 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
80

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menu Categories Account Settings ul.bottom-menu > li.nav-item > div.sections > div.section-items

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
› div.banner-slider > div#home-slider > div.owl-nav > button.owl-next
div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot
div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot
div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot
div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot
div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot
‹ div.row > div#product-slider > div.owl-nav > button.owl-prev
› div.row > div#product-slider > div.owl-nav > button.owl-next
‹ div.row > div#latest-slider > div.owl-nav > button.owl-prev
› div.row > div#latest-slider > div.owl-nav > button.owl-next

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form#search_mini_form > div.field > div.control > input#search form#search_mini_form > div.field > div.control > input#search
Shop div.product-item-info > div.product-item-details > div.product-item-subtext > p
Last arrived div.product-item-info > div.product-item-details > div.product-item-subtext > p
div.newsletter > div.control > span.input-text > input#newsletter div.newsletter > div.control > span.input-text > input#newsletter
Support div.row > div.col-lg > div.block-content > h6
Disclaimers and rules div.row > div.col-lg-6 > div.block-content > h6
Contact div.row > div.col-lg > div.block-content > h6
Cookie Policy div.policy-links > div > a.iubenda-nostyle > span
Privacy Policy div.policy-links > div > a.iubenda-nostyle > span

These are opportunities to improve the legibility of your content.

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
Support div.row > div.col-lg > div.block-content > h6

These are opportunities to improve keyboard navigation in your application.

Best practices

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
+39 (0)91 74877 22 ul.site-links > li > p > a
+39 (0)91 74877 23 ul.site-links > li > p > a

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]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[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 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
○`<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
○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
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
69

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
div.actions > div#switcher-language-trigger > strong.view-en > img.switcher-id div.actions > div#switcher-language-trigger > strong.view-en > img.switcher-id
magicmotorsport.shop/media/wysiwyg/smartwave/porto/flags/en.png16 x 1116 x 1124 x 17

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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

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 404 ()
Refused to execute script from 'https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB///widget.trustpilot.com/bootstrap/v5/tp.widget.bootstrap.min.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
Sending form data to 'https://www.facebook.com/tr/' violates the following report-only Content Security Policy directive: "form-action 'self' geostag.cardinalcommerce.com geo.cardinalcommerce.com 1eafstag.cardinalcommerce.com 1eaf.cardinalcommerce.com centinelapistag.cardinalcommerce.com centinelapi.cardinalcommerce.com pilot-payflowlink.paypal.com www.paypal.com www.sandbox.paypal.com *.paypal.com www.apptrian.com tiktok.com www.tiktok.com connect.tiktok.net graph.tiktok.com *.cardinalcommerce.com 3ds-secure.cardcomplete.com www.clicksafe.lloydstsb.com pay.activa-card.com *.wirecard.com acs.sia.eu *.touchtechpayments.com www.securesuite.co.uk rsa3dsauth.com *.monzo.com *.arcot.com *.wlp-acs.com www.searchanise.com *.searchserverapi.com *.searchserverapi1.com *.twitter.com". The violation has been logged, but no further action has been taken.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
●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
●Page has the HTML doctype
●Properly defines charset
●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
83

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 destinationLink Text
magicmotorsport.shop/en/dynomag-awd-roller.htmlMORE 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
div.header > div.header-center > div.search-area > a.search-toggle-icon div.header > div.header-center > div.search-area > a.search-toggle-icon

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`

Send Feedback