Lighthouse Mobile

· 0 checks — Mobile 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
/cdn-cgi/challenge-platform/h/g/scripts/jsd/825e783f7fae/...	14400.0 s	11.0 KiB
/beacon.min.js/v833ccba57c9e4d2798f2e76cebdd09a1177817227...	86400.0 s	11.4 KiB
/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader...	172793.0 s	4.5 KiB

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.

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:7783.52 label:Time to first byte subpart:timeToFirstByte] map[duration:47.9 label:Resource load delay subpart:resourceLoadDelay] map[duration:147.917 label:Resource load duration subpart:resourceLoadDuration] map[duration:50.531 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-DIV

nodeLabel: article#post-62 > div.elementor > section.elementor-section > div.elementor-background-overlay

path: 1,HTML,1,BODY,3,DIV,1,DIV,0,DIV,0,ARTICLE,0,DIV,0,SECTION,0,DIV

selector: article#post-62 > div.elementor > section.elementor-section > div.elementor-background-overlay

snippet: <div class="elementor-background-overlay">

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: article#post-62 > div.elementor > section.elementor-section > div.elementor-background-overlay

path: 1,HTML,1,BODY,3,DIV,1,DIV,0,DIV,0,ARTICLE,0,DIV,0,SECTION,0,DIV

selector: article#post-62 > div.elementor > section.elementor-section > div.elementor-background-overlay

snippet: <div class="elementor-background-overlay">

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

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: 7.6 s

URL	Time Spent
www.muscatbeautysalon.com/	7.7 s

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: 0.0 ms 755.0 KiB

URL	Transfer Size	Est Savings
blob:https://www.muscatbeautysalon.com/c84c43dc-ae7b-4697-9ce4-ec25cdee5ea0	776.5 KiB	741.0 KiB
:root{--wcboost-swatches-item-width:30px;--wcboost-swatches-item-width:30px;--wcboost-swatches-item…	19.4 KiB	14.1 KiB

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

●Time to Interactive 3.1 s

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 1,027 KiB

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.6 s

●Avoid long main-thread tasks 7 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 90 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

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.

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
header#site-header > div.header-mobile > div.mobile-menu > button.mobile-menu-toggle `header#site-header > div.header-mobile > div.mobile-menu > button.mobile-menu-toggle`

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
header#site-header > div.header-mobile > div.site-branding > a.logo `header#site-header > div.header-mobile > div.site-branding > a.logo`
div.header-mobile > div.mobile-header-icons > div.mobile-search > a.search-icon `div.header-mobile > div.mobile-header-icons > div.mobile-search > a.search-icon`
div.header-mobile > div.mobile-header-icons > div.header-wishlist > a.wishlist-icon `div.header-mobile > div.mobile-header-icons > div.header-wishlist > a.wishlist-icon`
div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button `div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button`
div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button `div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button`
div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button `div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button`
div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button `div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button`
div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button `div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button`
div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button `div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button`
div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button `div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button`
div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button `div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button`
div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button `div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button`
div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button `div.product-inner > div.product-thumbnail > div.product-loop__buttons > a.quick-view-button`
div.footer-container > div.footer-items > div.footer-branding > a.logo `div.footer-container > div.footer-items > div.footer-branding > a.logo`
body.home > div#page > a#gotop `body.home > div#page > a#gotop`

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.

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
BAIN CREME ANTI PELLICULAIRE `div.product-inner > div.product-thumbnail > a.woocommerce-LoopProduct-link > img.lazy`	/wp-content/uploads/2025/02/KER_00226-3474637135690-250ml...	174 x 1500 (0.12)	600 x 600 (1.00)
BAIN DE MASSE EPAISSISSANT `div.product-inner > div.product-thumbnail > a.woocommerce-LoopProduct-link > img.lazy`	/wp-content/uploads/2025/02/3474637077518_Bain-De-Masse-E...	174 x 1500 (0.12)	600 x 600 (1.00)

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 / Warning	Source
SharedStorage	www.muscatbeautysalon.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.muscatbeautysalon.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.muscatbeautysalon.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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.

Source	Description
/home/u251455955/domains/muscatbeautysalon.com/public_htm...	`Failed to load resource: the server responded with a status of 404 ()`

●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

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

100

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.

○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 have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`