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 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:1.079 source:map[column:4719 line:1843 type:source-location url:https://romeronperfumes.com.au/ 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:0.704 source:map[column:80 line:4161 type:source-location url:https://romeronperfumes.com.au/ urlProvider:network]] map[reflowTime:91.267 source:map[type:text value:[unattributed]]] map[reflowTime:1.079 source:map[column:144153 line:0 type:source-location url:https://romeronperfumes.com.au/cdn/wpm/b979a3e2fw137e9400p4daec9d4mf64d2306m.js urlProvider:network]]]

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
Candles `div.collection-card > div.collection-card__inner > div.resource-image > img.resource-image__image`	romeronperfumes.com.au/cdn/shop/collections/candles.png?v=1786802449&width=832	83.9 KiB	72.2 KiB
8ml Pen Perfumes `div.collection-card > div.collection-card__inner > div.resource-image > img.resource-image__image`	/cdn/shop/collections/pen_perfume_web_d276071c-8418-4fb2-...	77.6 KiB	66.0 KiB
AMALIA - Marc Antoine Barrois Tilia `slideshow-slides > slideshow-slide.product-media-container > div.product-media > img.product-media__image`	romeronperfumes.com.au/cdn/shop/files/AMALIA.png?v=1786241835&width=832	39.3 KiB	28.7 KiB
Platin - Men `div.collection-card > div.collection-card__inner > div.resource-image > img.resource-image__image`	/cdn/shop/collections/ROMERON_MENS.jpg?v=1786242361&width...	62.5 KiB	15.6 KiB
Platin - Women `div.collection-card > div.collection-card__inner > div.resource-image > img.resource-image__image`	/cdn/shop/collections/PLATIN_WOMAN_1_cbfe2df0-fd1f-4ea8-8...	61.8 KiB	15.3 KiB

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-5-IMG

nodeLabel: div.media-block > deferred-media.media-block__media > button.button > img.deferred-media__poster-image

path: 1,HTML,1,BODY,3,MAIN,0,DIV,1,DIV,0,DIV,0,DEFERRED-MEDIA,0,BUTTON,0,IMG

selector: div.media-block > deferred-media.media-block__media > button.button > img.deferred-media__poster-image

snippet: <img src="https://romeronperfumes.com.au/cdn/shop/files/preview_images/14003be221584…" alt="" srcset="//romeronperfumes.com.au/cdn/shop/files/preview_images/14003be221584d65834…" width="3840" height="6827" sizes="(min-width: 750px) 50vw, 100vw" class="deferred-media__poster-image">

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

value: No additional origins are good candidates for preconnecting

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/shopifycloud/portable-wallets/latest/accelerated-che...	300.0 s	2.2 KiB
/cdn/shopifycloud/shop-js/modules/v2/loader.init-shop-car...	1800.0 s	1.2 KiB
shop.app/checkouts/internal/preloads.js?locale=en-AU&shop_id=75774427291	60.0 s	505 B

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	Duration
/cdn/shop/t/13/assets/view-transitions.js?v=7106414069516...	1.4 KiB	151 ms

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

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: 150 ms 28.3 KiB

URL	Transfer Size	Est Savings
/cdn/shop/t/13/compiled_assets/styles.css?v=6325439337137...	18.9 KiB	15.5 KiB
/cdn/shop/t/13/assets/base.css?v=769603843573037003417868...	18.6 KiB	12.8 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 272.3 KiB

URL	Transfer Size	Est Savings
/extensions/01a0026b-8926-7e8d-a2f2-ce2c5593288f/forms-25...	251.6 KiB	238.9 KiB
romeronperfumes.com.au/cdn/wpm/b979a3e2fw137e9400p4daec9d4mf64d2306m.js	70.0 KiB	33.3 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
Unattributable	2.9 s	246 ms	0.0 ms
romeronperfumes.com.au/	2.7 s	141 ms	26 ms
romeronperfumes.com.au/cdn/wpm/b979a3e2fw137e9400p4daec9d4mf64d2306m.js	310 ms	258 ms	36 ms
romeronperfumes.com.au/cdn/shopifycloud/perf-kit/shopify-perf-kit-3.8.3.min.js	235 ms	205 ms	9.6 ms
/cdn/s/trekkie.storefront.7bcd7bb8195e24c65a61d69d69eb323...	214 ms	189 ms	15 ms
/cdn/shop/t/13/assets/section-renderer.js?v=1233111174855...	109 ms	66 ms	0.1 ms
/cdn/shop/t/13/assets/slideshow.js?v=16872658739827910200...	98 ms	79 ms	0.3 ms
/cdn/shopifycloud/shop-js/modules/v2/chunk.index_BZ-S_qkG...	75 ms	69 ms	0.5 ms
/cdn/shopifycloud/storefront/assets/shopify_pay/storefron...	73 ms	56 ms	16 ms
/cdn/shop/t/13/assets/utilities.js?v=28506172887375975941...	58 ms	28 ms	0.2 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
Other	3.8 s
Script Evaluation	1.8 s
Style & Layout	1.4 s
Parse HTML & CSS	282 ms
Rendering	233 ms
Script Parsing & Compilation	130 ms

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 4.5 KiB

URL	Transfer Size	Est Savings
/cdn/shop/t/13/assets/base.css?v=769603843573037003417868...	19.1 KiB	4.5 KiB

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
/cdn/shop/videos/c/vp/14003be221584d6583467024f38a1047/14...	14.5 MiB
/cdn/shop/videos/c/vp/4e85a8ccd91b4469aeddf16bc4fd5ef9/4e...	4.8 MiB
/extensions/01a0026b-8926-7e8d-a2f2-ce2c5593288f/forms-25...	252.4 KiB
/cdn/shopifycloud/checkout-web/assets/c1/hydrate.Hgrd3IkI.js	198.8 KiB
/cdn/shop/collections/car_fragrance_Thumbnail.png?v=17830...	153.4 KiB
/cdn/shop/collections/reed_difusser_web.png?v=1786802324&...	113.2 KiB
/cdn/shopifycloud/checkout-web/assets/c1/shipping-methods...	91.7 KiB
romeronperfumes.com.au/cdn/shop/files/af3.png?v=1785274896&width=832	90.6 KiB
romeronperfumes.com.au/cdn/shop/collections/candles.png?v=1786802449&width=832	84.6 KiB
/cdn/shop/files/0da55bbf-4315-4b67-b05e-7f7c48394ee9.png?...	84.6 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 11 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 160 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 460 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
IMPERIUM - Essential Parfums Bois Imperial `slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide`
MEGAMARINE - Orto Paris Megamare `slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide`
PARADIGME - Initio Paragon `slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide`
LOVE IN PARIS - Montale Rendez Vous Paris `slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide`
VERA - Lattafa Yara `slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide`
NEW YORK NIGHT - Bond 9 New York `slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide`
ILLUSION - Amouage Guidance `slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide`
AFFAIRE - Parfums de Marly Althaïr `slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide`
Room Sprays `slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide`
Hanging Car Fragrances `slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide`

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.

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
SHOP PERFUMES `div.group-block > div.group-block-content > div.spacing-style > h4`
Explore Travel & Pen Signature Sizes `div.border-style > div.spacing-style > div.spacing-style > h5`

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.media-block > deferred-media.media-block__media > video > img `div.media-block > deferred-media.media-block__media > video > img`
div.media-block > deferred-media.media-block__media > video > img `div.media-block > deferred-media.media-block__media > video > img`

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.section > div.border-style > div.spacing-style > a.image-block `div.section > div.border-style > div.spacing-style > a.image-block`
div.section > div.border-style > div.spacing-style > a.image-block `div.section > div.border-style > div.spacing-style > a.image-block`
div.section > div.border-style > div.spacing-style > a.image-block `div.section > div.border-style > div.spacing-style > a.image-block`
div.section > div.border-style > div.spacing-style > a.image-block `div.section > div.border-style > div.spacing-style > a.image-block`

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
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > a`
nav.details-content > ul.list-unstyled > li.menu__item > a `nav.details-content > ul.list-unstyled > li.menu__item > 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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]` values are valid

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

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

●Buttons have an accessible name

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

●ARIA attributes are used as specified for the element's role

●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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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

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

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

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

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

Best Practices

General

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
romeronperfumes.com.au/favicon.ico	`Failed to load resource: the server responded with a status of 404 ()`

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

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

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.media-block > deferred-media.media-block__media > video > img `div.media-block > deferred-media.media-block__media > video > img`
div.media-block > deferred-media.media-block__media > video > img `div.media-block > deferred-media.media-block__media > video > img`

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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`