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.

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.406787] map[node:map[boundingRect:map[bottom:329 height:91 left:15 right:276 top:238 width:261] lhId:page-1-SPAN nodeLabel:Digitize path:1,HTML,1,BODY,0,DIV,2,MAIN,0,DIV,0,SECTION,2,DIV,1,H3,0,SPAN selector:section.s_cover > div.s_allow_columns > h3 > span snippet:<span style="font-size: 65px;"> type:node] score:0.406107 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/poppins/v24/pxiByp8kv8JHgFVrLCz7Z1xlFd2JQEk.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/poppins/v24/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:237 height:77 left:15 right:1335 top:160 width:1320] lhId:page-6-H1 nodeLabel: path:1,HTML,1,BODY,0,DIV,2,MAIN,0,DIV,0,SECTION,2,DIV,0,H1 selector:div#wrap > section.s_cover > div.s_allow_columns > h1.display-3 snippet:<h1 class="display-3" style="text-align: center;"> type:node] score:0.00068 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/poppins/v24/pxiByp8kv8JHgFVrLDz8Z1xlFd2JQEk.woff2]]] type:subitems]]]

items: [map[node:map[type:text value:Total] score:0.01544] map[node:map[boundingRect:map[bottom:1067 height:1136 left:-65 right:1415 top:-69 width:1481] lhId:page-7-SPAN nodeLabel:div#wrap > section.s_cover > span.s_parallax_bg_wrap > span.s_parallax_bg path:1,HTML,1,BODY,0,DIV,2,MAIN,0,DIV,0,SECTION,0,SPAN,0,SPAN selector:div#wrap > section.s_cover > span.s_parallax_bg_wrap > span.s_parallax_bg snippet:<span class="s_parallax_bg oe_img_bg o_bg_img_center o_bg_img_origin_border_box" data-original-id="839" data-original-src="/web/image/839-71704307/12.webp" data-mimetype-before-conversion="image/webp" data-resize-width="1920" data-mimetype="image/webp" style="background-image: url("/web/image/842-71704307/12.webp");" data-attachment-id="839"> type:node] score:0.01544]]

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

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
www.vacriganum.com/web/assets/1/47f191a/web.assets_frontend.min.css	166.8 KiB	830 ms
www.vacriganum.com/website/static/src/js/content/cookie_watcher.js	1.3 KiB
fonts.googleapis.com/css?family=Inter:300,300i,400,400i,700,700i&display=swap	1005 B	226 ms
fonts.googleapis.com/css?family=Poppins:300,300i,400,400i,700,700i&display=swap	1.1 KiB

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
www.vacriganum.com/website/static/src/js/content/cookie_watcher.js	3600.0 s	1.3 KiB
download.odoo.com/js/plausi_saas.js	0.0 ms	964 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
Digitize `section.s_cover > div.s_allow_columns > h3 > span`	0.406
div#wrap > section.s_cover > span.s_parallax_bg_wrap > span.s_parallax_bg `div#wrap > section.s_cover > span.s_parallax_bg_wrap > span.s_parallax_bg`	0.015
`div#wrap > section.s_cover > div.s_allow_columns > h1.display-3`	0.001

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.

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

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: 280 ms 149.8 KiB

URL	Transfer Size	Est Savings
www.vacriganum.com/web/assets/1/47f191a/web.assets_frontend.min.css	166.6 KiB	149.8 KiB

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

URL	Transfer Size	Est Savings
www.vacriganum.com/web/assets/1/47f191a/web.assets_frontend.min.css	166.8 KiB	12.3 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: 0.0 ms 643.8 KiB

URL	Transfer Size	Est Savings
www.vacriganum.com/web/assets/1/fc4f2f5/web.assets_frontend_lazy.min.js	1.1 MiB	643.8 KiB

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

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

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

●JavaScript execution time 0.4 s

●Minimizes main-thread work 0.8 s

●Avoid long main-thread tasks 3 long tasks found

●Avoid non-composited animations 3 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 240 ms

●Server Backend Latencies 20 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 470 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contact Us `div.container-fluid > a.oe_unremovable > font.text-white > strong`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
free website `div.row > div.col-md > div.o_brand_promotion > a`

These are opportunities to improve the legibility of your content.

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
Digitize >> `div#wrap > section.s_cover > div.s_allow_columns > h3`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link `div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link`
div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link `div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link`
div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link `div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link`

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
div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link `div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link`
div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link `div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link`
div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link `div.row > div.s_table_of_content_navbar_wrap > div.s_table_of_content_navbar > a.table_of_content_link`

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]`s are contained by their required parent element

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

●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.

●Elements use only permitted ARIA attributes

●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

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○Form elements have associated labels

○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

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

○Tables have different content in the summary attribute and `<caption>`.

○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
www.vacriganum.com/web/assets/1/fc4f2f5/web.assets_frontend_lazy.min.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.

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
www.vacriganum.com/website-design	Read More
www.vacriganum.com/crm-systems-data-analytics	Read More
www.vacriganum.com/ai-business-automation	Read More
www.vacriganum.com/digital-marketing	Read 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`