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.

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:649.0640004882813 label:Time to first byte subpart:timeToFirstByte] map[duration:942.5969995117188 label:Resource load delay subpart:resourceLoadDelay] map[duration:980.656 label:Resource load duration subpart:resourceLoadDuration] map[duration:1099.511 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Hero

path: 1,HTML,1,BODY,0,DIV,5,DIV,0,DIV,0,DIV,2,DIV,2,DIV,1,MAIN,2,SECTION,0,DIV,1,FIGURE,1,DIV,2,PICTURE,3,IMG

selector: figure.banner > div.banner__media > picture > img

snippet: <img width="1920" height="800" alt="Hero" loading="eager" onerror="this.setAttribute('data-error', 1)" data-nuxt-pic="" src="https://api.norriq.shop/images/proxy/_/rs:fill:640:267:1/g:fp:0.7933309837…" sizes="(max-width: 640px) 320px, (max-width: 768px) 640px, (max-width: 1024px) 76…" srcset="https://api.norriq.shop/images/proxy/_/rs:fill:320:133:1/g:fp:0.7933309837…">

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: Hero

path: 1,HTML,1,BODY,0,DIV,5,DIV,0,DIV,0,DIV,2,DIV,2,DIV,1,MAIN,2,SECTION,0,DIV,1,FIGURE,1,DIV,2,PICTURE,3,IMG

selector: figure.banner > div.banner__media > picture > img

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

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
norriq.shop/_nuxt/AddToCart.BLwbK-4d.css	684 B	1.7 s
norriq.shop/_nuxt/default.BXdTFt2a.css	926 B	1.7 s
norriq.shop/_nuxt/PageRenderer.c8dOUXwc.css	1.1 KiB	1.1 s
norriq.shop/_nuxt/UniqueSellingPoints.DSPfnU3e.css	934 B	1.7 s
norriq.shop/_nuxt/ResponsivePicture.B1W42TPM.css	688 B	1.7 s

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
norriq.shop/fonts/Lato-normal-400-latin-ext.woff2	14400.0 s	5.9 KiB
norriq.shop/images/logo.svg	14400.0 s	1.5 KiB

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
Kids `article.flex > div.relative > picture > img`	/images/proxy/_/rs:fill:1280:916:1/g:fp:0.5:0.5/plain/htt...	75.0 KiB	54.8 KiB
Kogeplader `article.flex > div.relative > picture > img`	/images/proxy/_/rs:fill:1280:916:1/g:fp:0.957894736842105...	34.3 KiB	25.0 KiB
Drinks `article.flex > div.relative > picture > img`	/images/proxy/_/rs:fill:1280:916:1/g:fp:0.5:0.5/plain/htt...	25.4 KiB	18.5 KiB
Hero `figure.banner > div.banner__media > picture > img`	/images/proxy/_/rs:fill:640:267:1/g:fp:0.7933309837092731...	29.7 KiB	18.1 KiB
Lisbeth baking play set `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/a6ab8348...	20.1 KiB	5.4 KiB
Carson knitted bell teddy `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/a5ab8348...	18.8 KiB	4.2 KiB

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 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: 2.8 s 1.1 MiB

URL	Transfer Size	Est Savings
norriq.shop/_nuxt/FST49PYT.js	585.7 KiB	436.1 KiB
norriq.shop/_nuxt/JT9aLxij.js	738.3 KiB	388.1 KiB
norriq.shop/_nuxt/D0NXVq8K.js	223.7 KiB	92.3 KiB
www.googletagmanager.com/gtag/js?id=G-NT7Z8E40FY&cx=c&gtm=4e65d0	153.1 KiB	76.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-WNRC7R9	122.8 KiB	63.2 KiB
norriq.shop/_nuxt/C2nbNEA3.js	68.9 KiB	37.0 KiB
norriq.shop/_nuxt/BRMHjgGy.js	27.9 KiB	21.8 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
norriq.shop/	1.5 s	167 ms	2.0 ms
Unattributable	1.2 s	485 ms	0.0 ms
norriq.shop/_nuxt/CB7oOE8Z.js	1.1 s	1.0 s	0.3 ms
www.googletagmanager.com/gtag/js?id=G-NT7Z8E40FY&cx=c&gtm=4e65d0	288 ms	219 ms	65 ms
norriq.shop/_nuxt/D0NXVq8K.js	275 ms	189 ms	4.2 ms
norriq.shop/_nuxt/JT9aLxij.js	267 ms	153 ms	4.4 ms
www.googletagmanager.com/gtm.js?id=GTM-WNRC7R9	205 ms	154 ms	49 ms
norriq.shop/_nuxt/B7x18WR1.js	175 ms	92 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
Script Evaluation	2.5 s
Other	1.3 s
Style & Layout	959 ms
Parse HTML & CSS	151 ms
Script Parsing & Compilation	140 ms
Rendering	128 ms
Garbage Collection	49 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
Adiana knitted teddy `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/67ab8348...
Adiana knitted teddy `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/68ab8348...
Amanda play house furniture `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/a3ab8348...
Amanda play house furniture `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/a4ab8348...
Astrid abacus `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/90ab8348...
Astrid abacus `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/91ab8348...
Carson knitted bell teddy `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/a5ab8348...
Elena Wood Toy `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/5fab8348...
Gitte giraffe `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/88ab8348...
Kate cupcakes toy 4-pack `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/8eab8348...
Kate cupcakes toy 4-pack `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/8fab8348...
Kevin car & airplane - 2-pack `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/6dab8348...
Kirk hammer toy `div.flex > a.aspect-4/5 > picture > img`	/images/proxy/_/rs:fit:400:300:1/g:ce/plain//erp/9bab8348...

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

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●User Timing marks and measures 26 user timings

●Avoid long main-thread tasks 18 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 840 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 500 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●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 have a discernible name

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

○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

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

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

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

100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
norriq.shop/_nuxt/JT9aLxij.js
norriq.shop/_nuxt/FST49PYT.js
norriq.shop/_nuxt/D0NXVq8K.js

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

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.

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`head > meta`
`https://norriq.shop/robots.txt`

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

○Structured data is valid

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