Lighthouse Desktop
· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.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.
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
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Essential Open Earbuds and Everyday Earbuds Classic div.needsclick > div.needsclick > div.needsclick > img.needsclick | /company/LuhenE/images/75f4c4fd-fee1-46f2-948f-44ed26751f... | 320.3 KiB | 226.6 KiB |
User generated content video div.slick-track > div.ugc-card > div.ugc-card__media-wrap > video | /cdn/shop/files/preview_images/c1fd04da4621438c80d90c04c5... | 98.9 KiB | 88.2 KiB |
User generated content video div.slick-track > div.ugc-card > div.ugc-card__media-wrap > video | /cdn/shop/files/preview_images/e1eec2def32846e8bef7ca4ed1... | 44.3 KiB | 39.5 KiB |
For The One Who Never Stops. div.sb__banner-wrap > div.sb__slide > picture > img.sb__bg | /cdn/shop/files/MD_HOMEPAGE_DESKTOP_V1.jpg?v=1774007616&w... | 87.8 KiB | 4.5 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| /cdn/shop/t/562/compiled_assets/styles.css?v=539382814132... | 3.2 KiB |
| /cdn/shopifycloud/portable-wallets/latest/accelerated-che... | 2.1 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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Diagnostics
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /extensions/019d622f-4dd5-79c7-b5be-31579e6d5d38/bitespee... | 45.1 KiB | 10.5 KiB |
| crossborder-integration.global-e.com/resources/js/app?shop=raycon.myshopify.com | 23.0 KiB | 10.0 KiB |
| inline: if (!window.customerHub) { windo… | 5.1 KiB | 3.1 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /cdn/shop/t/562/assets/theme.css?v=1166855633815564921117... | 46.5 KiB | 43.1 KiB |
| .alchemy-reset{} … | 19.5 KiB | 19.5 KiB |
| cdn1.stamped.io/files/widget.min.css | 17.8 KiB | 17.8 KiB |
| /onsite/js/build-preview/commit-98747c9b1816a2f78e748cdc0... | 15.1 KiB | 14.1 KiB |
| /extensions/019d68e3-79e6-7f04-acc7-fc5b3ebc1f89/judgeme-... | 10.7 KiB | 10.7 KiB |
| .accessibly-app-hidden{visibility:hidden !important;display:none !important} … | 10.6 KiB | 10.6 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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 4.6 s |
| Other | 1.4 s |
| Style & Layout | 380 ms |
| Script Parsing & Compilation | 226 ms |
| Garbage Collection | 140 ms |
| Rendering | 83 ms |
| Parse HTML & CSS | 57 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages that use WebXR are not currently eligible for back/forward cache. | Actionable |
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| .alchemy-reset{} … | 19.8 KiB | 16.7 KiB |
| /onsite/js/build-preview/commit-98747c9b1816a2f78e748cdc0... | 15.3 KiB | 3.0 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
logo div.needsclick > div.needsclick > div.needsclick > img.needsclick | /company/LuhenE/images/43864d96-7406-4224-9055-6ff8110967... |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
RENDONS VOTRE BOÎTE DE RÉCEPTION PLUS AGRÉABLE div.footer__top > div.wrapper > div.footer__newsletter-form > p.small--text-center |
These are opportunities to improve the legibility of your content.
Best Practices
General
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md. | |
| AttributionReporting | |
| Fledge |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Access to fetch at 'https://raycon.myshopify.com/cart.js' from origin 'https://rayconglobal.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
rayconglobal.com/ line 9614, col 14 | Error updating cart product ID attributes: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
TypeError: Failed to fetch dynamically imported module: https://rayconglobal.com/a/elevar/static/configs/eaf3284a91c577096e0e52bbfe2a36e0b2d2c0a0/config.js | |
Uncaught (in promise) Error: Failed to fetch settings: | |
/w/fb26f090-0ab1-4b11-bb96-9f0ab37adae9/cd4093cd-9f39-486... line 306, col 4966 | Warning: Prop `%s` did not match. Server: %s Client: %s%s src "https://replocdn.com/w/fb26f090-0ab1-4b11-bb96-9f0ab37adae9/cd4093cd-9f39-486d-90e0-6afb23f6cff2.min.js?v=bdd807e0-1d8a-11f1-bf0b-a9b4be72aad1" "http://localhost:3001/w/fb26f090-0ab1-4b11-bb96-9f0ab37adae9/cd4093cd-9f39-486d-90e0-6afb23f6cff2.min.js?v=bdd807e0-1d8a-11f1-bf0b-a9b4be72aad1"
at script
at Xhe (https://replocdn.com/w/fb26f090-0ab1-4b11-bb96-9f0ab37adae9/cd4093cd-9f39-486d-90e0-6afb23f6cff2.min.js?v=bdd807e0-1d8a-11f1-bf0b-a9b4be72aad1:307:919) |
/w/fb26f090-0ab1-4b11-bb96-9f0ab37adae9/cd4093cd-9f39-486... line 306, col 4966 | Warning: ReactDOM.hydrate is no longer supported in React 18. Use hydrateRoot instead. Until you switch to the new API, your app will behave as if it's running React 17. Learn more: https://reactjs.org/link/switch-to-createroot |
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.