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.

100

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.

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
luxsite.eu/wp-content/uploads/trustindex-google-widget-gdpr.css?1793570382	0 B	173 ms
/wp-content/litespeed/css/e7ab1793a44c008f2271c473400544a...	0 B	93 ms
/wp-content/uploads/elementor/google-fonts/css/robotoslab...	0 B	230 ms
/wp-content/uploads/elementor/google-fonts/css/poppins.cs...	0 B	230 ms
/wp-content/uploads/elementor/google-fonts/css/ibmplexsan...	0 B	230 ms
/wp-content/uploads/elementor/google-fonts/css/roboto.css...	0 B	230 ms

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

Diagnostics

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.


milori-wedding `div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image`
shop-maxartprint `div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image`
privatstav `div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image`
gorbach `div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image`
tessastav `div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image`
berreicapital `div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image`
my-jobs `div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image`
idealuklid `div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image`
orean-beauty-salon `div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image`

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 0.6 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 114 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.2 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 50 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 80 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

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

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
--Choose-- Web Design Website Development Online Shop Website Redesign Promo Vi… `div.elementor-form-fields-wrapper > div.elementor-field-type-select > div.elementor-field > select#form-field-field_c5af16b`

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.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon `div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon`
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon `div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon`
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon `div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon`
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a `div.e-con-inner > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon `div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon`
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon `div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon`

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
HOME `nav.elementor-nav-menu--main > ul#menu-1-aab2942 > li.menu-item > a.elementor-item`
Design `li.menu-item > ul.sub-menu > li.menu-item > a.elementor-sub-item`
Website development `li.menu-item > ul.sub-menu > li.menu-item > a.elementor-sub-item`
Web application `li.menu-item > ul.sub-menu > li.menu-item > a.elementor-sub-item`
Online Shop `li.menu-item > ul.sub-menu > li.menu-item > a.elementor-sub-item`
Advertising video clips `li.menu-item > ul.sub-menu > li.menu-item > a.elementor-sub-item`
PORTFOLIO `nav.elementor-nav-menu--main > ul#menu-1-aab2942 > li.menu-item > a.elementor-item`
REVIEWS `nav.elementor-nav-menu--main > ul#menu-1-aab2942 > li.menu-item > a.elementor-item`
CONTACT `nav.elementor-nav-menu--main > ul#menu-1-aab2942 > li.menu-item > a.elementor-item`
BLOG `nav.elementor-nav-menu--main > ul#menu-1-aab2942 > li.menu-item > a.elementor-item`
FAQ `nav.elementor-nav-menu--main > ul#menu-1-aab2942 > li.menu-item > a.elementor-item`
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-name `form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-name`
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-email > input#form-field-field_9b6cd50 `form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-email > input#form-field-field_9b6cd50`
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-tel > input#form-field-field_046f3cd `form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-tel > input#form-field-field_046f3cd`
Web Design `nav.elementor-nav-menu--main > ul#menu-1-4607ae4 > li.menu-item > a.elementor-item`
Website Development `nav.elementor-nav-menu--main > ul#menu-1-4607ae4 > li.menu-item > a.elementor-item`
Web Application `nav.elementor-nav-menu--main > ul#menu-1-4607ae4 > li.menu-item > a.elementor-item`
Online Shop `nav.elementor-nav-menu--main > ul#menu-1-4607ae4 > li.menu-item > a.elementor-item`
Website Redesign `nav.elementor-nav-menu--main > ul#menu-1-4607ae4 > li.menu-item > a.elementor-item`
Promo Videos `nav.elementor-nav-menu--main > ul#menu-1-4607ae4 > li.menu-item > a.elementor-item`
Home `nav.elementor-nav-menu--main > ul#menu-1-3bd9bdf > li.menu-item > a.elementor-item`
Porttfolio `nav.elementor-nav-menu--main > ul#menu-1-3bd9bdf > li.menu-item > a.elementor-item`
Blog `nav.elementor-nav-menu--main > ul#menu-1-3bd9bdf > li.menu-item > a.elementor-item`
Contact `nav.elementor-nav-menu--main > ul#menu-1-3bd9bdf > li.menu-item > a.elementor-item`
FAQ `nav.elementor-nav-menu--main > ul#menu-1-3bd9bdf > li.menu-item > a.elementor-item`
Home `nav.elementor-nav-menu--main > ul#menu-1-77317f3 > li.menu-item > a.elementor-item`
Porttfolio `nav.elementor-nav-menu--main > ul#menu-1-77317f3 > li.menu-item > a.elementor-item`
Blog `nav.elementor-nav-menu--main > ul#menu-1-77317f3 > li.menu-item > a.elementor-item`
Contact `nav.elementor-nav-menu--main > ul#menu-1-77317f3 > li.menu-item > a.elementor-item`
FAQ `nav.elementor-nav-menu--main > ul#menu-1-77317f3 > li.menu-item > a.elementor-item`
Web Design `nav.elementor-nav-menu--main > ul#menu-1-53fbf48 > li.menu-item > a.elementor-item`
Website Development `nav.elementor-nav-menu--main > ul#menu-1-53fbf48 > li.menu-item > a.elementor-item`
Web Application `nav.elementor-nav-menu--main > ul#menu-1-53fbf48 > li.menu-item > a.elementor-item`
Online Shop `nav.elementor-nav-menu--main > ul#menu-1-53fbf48 > li.menu-item > a.elementor-item`
Website Redesign `nav.elementor-nav-menu--main > ul#menu-1-53fbf48 > li.menu-item > a.elementor-item`
Promo Videos `nav.elementor-nav-menu--main > ul#menu-1-53fbf48 > li.menu-item > a.elementor-item`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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]` 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.

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

●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 are distinguishable without relying on color.

●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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

○`<object>` elements have alternate text

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

Best Practices

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
FencedFrame	luxsite.eu/cdn-cgi/challenge-platform/scripts/jsd/main.js?ray=a5441919ec14347e
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	luxsite.eu/cdn-cgi/challenge-platform/scripts/jsd/main.js?ray=a5441919ec14347e
Fledge	luxsite.eu/cdn-cgi/challenge-platform/scripts/jsd/main.js?ray=a5441919ec14347e

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
/wp-content/uploads/elementor/google-fonts/css/roboto.css...	`Failed to load resource: net::ERR_NAME_NOT_RESOLVED`
/wp-content/uploads/elementor/google-fonts/css/robotoslab...	`Failed to load resource: net::ERR_NAME_NOT_RESOLVED`
/wp-content/uploads/elementor/google-fonts/css/ibmplexsan...	`Failed to load resource: net::ERR_NAME_NOT_RESOLVED`
/wp-content/uploads/elementor/google-fonts/css/poppins.cs...	`Failed to load resource: net::ERR_NAME_NOT_RESOLVED`
/wp-content/litespeed/css/e7ab1793a44c008f2271c473400544a...	`Failed to load resource: the server responded with a status of 429 ()`
luxsite.eu/wp-content/uploads/trustindex-google-widget-gdpr.css?1793570382	`Failed to load resource: the server responded with a status of 429 ()`
luxsite.eu/wp-content/uploads/trustindex-google-widget-gdpr.css	`Failed to load resource: the server responded with a status of 429 ()`
luxsite.eu/wp-content/plugins/litespeed-cache/guest.vary.php	`Failed to load resource: the server responded with a status of 429 ()`
luxsite.eu/wp-content/uploads/2025/12/cropped-logo-seo2.webp	`Failed to load resource: the server responded with a status of 429 ()`
luxsite.eu/	`Uncaught (in promise) SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON`

●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

●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

●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

○Use a strong HSTS policy

○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

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 destination	Link Text
luxsite.eu/web-design/	Learn more
luxsite.eu/website-development/	Learn more
luxsite.eu/web-application/	Learn more
luxsite.eu/online-shop/	Learn more
luxsite.eu/web-design/	Learn more
luxsite.eu/advertising-video-clips/	Learn more
www.trustindex.io/?a=sys&c=wp-verified-badge&url=/review-platform-verification/	Learn more

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

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`