Lighthouse Desktop

· 0 checks — Desktop 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
danbritdirect.dk/images/logo.svg	0.0 ms	122.5 KiB

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.702784] map[node:map[boundingRect:map[bottom:3872 height:3664 left:0 right:1350 top:208 width:1350] lhId:page-1-DIV nodeLabel:Danbrit Akkumulator Velkommen til vores B-2-B Shop! GÅ TIL KUNDECENTER Brug … path:1,HTML,1,BODY,17,DIV,5,DIV,0,DIV,0,DIV,2,DIV selector:div.flex > div.app > div.flex > div.wrapper snippet:<div class="wrapper" data-v-4b186de2=""> type:node] score:0.702784 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:93 height:37 left:35 right:235 top:55 width:200] lhId:page-6-IMG nodeLabel:General.Title path:1,HTML,1,BODY,17,DIV,5,DIV,0,DIV,0,DIV,0,HEADER,2,DIV,0,DIV,0,DIV,0,DIV,5,A,0,IMG selector:div.grid > div.col-span-2 > a.router-link-active > img snippet:<img src="/images/logo.svg" alt="General.Title"> 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:24.918 source:map[column:709 line:24 type:source-location url:https://danbritdirect.dk/_nuxt/BwRYw4dp.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:240.948 source:map[type:text value:[unattributed]]] map[reflowTime:1.472 source:map[column:205927 line:3 type:source-location url:https://danbritdirect.dk/_nuxt/Dhhuls5Z.js urlProvider:network]] map[reflowTime:42.747 source:map[column:5457 line:0 type:source-location url:https://danbritdirect.dk/_nuxt/D8mJtIdJ.js urlProvider:network]] map[reflowTime:55.267 source:map[column:5410 line:0 type:source-location url:https://danbritdirect.dk/_nuxt/DmldgzNN.js urlProvider:network]] map[reflowTime:0.127 source:map[column:185903 line:3 type:source-location url:https://danbritdirect.dk/_nuxt/Dhhuls5Z.js urlProvider:network]] map[reflowTime:4.508 source:map[column:45227 line:0 type:source-location url:https://danbritdirect.dk/_nuxt/DmldgzNN.js urlProvider:network]]]

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,17,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.live.danbrit.norriq.dev/images/proxy/_/rs:fit:1280:533:1/g:fp:…" sizes="(max-width: 640px) 320px, (max-width: 768px) 640px, (max-width: 1024px) 76…" srcset="https://api.live.danbrit.norriq.dev/images/proxy/_/rs:fit:320:133:1/g:fp:0…">

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
danbritdirect.dk/_nuxt/entry.IKWlNHYf.css	41.1 KiB	51 ms
danbritdirect.dk/_nuxt/AddToCart.BEp9GU08.css	405 B
danbritdirect.dk/_nuxt/UniqueSellingPoints.CLCN3dS8.css	701 B
danbritdirect.dk/_nuxt/ResponsivePicture.DnvtxWAo.css	420 B
danbritdirect.dk/_nuxt/PageRenderer.BmDrvP2q.css	891 B

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

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.

Element	Layout shift score
Danbrit Akkumulator Velkommen til vores B-2-B Shop! GÅ TIL KUNDECENTER Brug … `div.flex > div.app > div.flex > div.wrapper`	0.703

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: 100 ms 346.6 KiB

URL	Transfer Size	Est Savings
danbritdirect.dk/_nuxt/CawlrmtO.js	182.6 KiB	135.9 KiB
danbritdirect.dk/_nuxt/oOnxIdNT.js	188.9 KiB	99.1 KiB
danbritdirect.dk/_nuxt/Dhhuls5Z.js	216.0 KiB	90.7 KiB
danbritdirect.dk/_nuxt/Cvx4-kRg.js	28.8 KiB	21.0 KiB

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	1.0 s
Other	584 ms
Style & Layout	566 ms
Rendering	52 ms
Garbage Collection	50 ms
Parse HTML & CSS	40 ms
Script Parsing & Compilation	15 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 reason	Failure type
Internal error.	Not actionable

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
General.Title `div.grid > div.col-span-2 > a.router-link-active > img`	danbritdirect.dk/images/logo.svg
HANKOOK AGM BATTERI 35AH (B32 MODEL) `div.flex > a.relative > picture > img`	/images/proxy/_/rs:fit:400:400:1/g:ce/plain//erp/16756113...
HANKOOK AGM BATTERI 35AH (A14 MODEL) `div.flex > a.relative > picture > img`	/images/proxy/_/rs:fit:400:400:1/g:ce/plain//erp/10042179...
HANKOOK AGM BATTERI 12V 75 AH (E23 MODEL) `div.flex > a.relative > picture > img`	/images/proxy/_/rs:fit:400:400:1/g:ce/plain//erp/91110649...

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

●Time to Interactive 2.3 s

●Document request latency

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●User Timing marks and measures 28 user timings

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 12 long tasks found

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 90 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 130 ms

○INP breakdown

○Avoid non-composited animations

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

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

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

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
danbritdirect.dk/_nuxt/oOnxIdNT.js
danbritdirect.dk/_nuxt/Dhhuls5Z.js
danbritdirect.dk/_nuxt/CawlrmtO.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

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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`