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
www.comprooroalatina.com/images/001.jpg	0.0 ms	524.0 KiB
www.comprooroalatina.com/images/000.jpg	0.0 ms	480.8 KiB
www.comprooroalatina.com/images/comproorolatina/topbanner.jpg	0.0 ms	435.1 KiB
www.comprooroalatina.com/images/005.jpg	0.0 ms	426.9 KiB
www.comprooroalatina.com/images/002.jpg	0.0 ms	365.5 KiB
www.comprooroalatina.com/include/javascript/scripts.js	0.0 ms	169.8 KiB
www.comprooroalatina.com/js/jquery-1.6.js	0.0 ms	89.5 KiB
www.comprooroalatina.com/js/Swis721_Cn_BT_400.font.js	0.0 ms	37.1 KiB
www.comprooroalatina.com/js/Swis721_Cn_BT_700.font.js	0.0 ms	36.0 KiB
www.comprooroalatina.com/images/seguicisufacebook.png	0.0 ms	28.2 KiB
www.comprooroalatina.com/style/verticalmenu.css	0.0 ms	21.3 KiB
www.comprooroalatina.com/style/stili.css	0.0 ms	20.8 KiB
www.comprooroalatina.com/js/tms_presets.js	0.0 ms	18.5 KiB
www.comprooroalatina.com/js/cufon-yui.js	0.0 ms	18.1 KiB
www.comprooroalatina.com/js/css3-mediaqueries.js	0.0 ms	15.9 KiB
www.comprooroalatina.com/javascript/javascript.js	0.0 ms	10.8 KiB
www.comprooroalatina.com/css/style.css	0.0 ms	9.4 KiB
www.comprooroalatina.com/js/responsiveslides.js	0.0 ms	9.3 KiB
www.comprooroalatina.com/js/tms-0.3.js	0.0 ms	8.4 KiB
www.comprooroalatina.com/js/jquery.easing.1.3.js	0.0 ms	8.2 KiB
www.comprooroalatina.com/javascript/cookie.js	0.0 ms	8.1 KiB
www.comprooroalatina.com/images/calcola.png	0.0 ms	7.0 KiB
www.comprooroalatina.com/js/jcarousellite.js	0.0 ms	5.5 KiB
www.comprooroalatina.com/style/blu.css	0.0 ms	3.1 KiB
www.comprooroalatina.com/css/responsiveslides.css	0.0 ms	2.9 KiB
www.comprooroalatina.com/css/zerogrid.css	0.0 ms	2.7 KiB
www.comprooroalatina.com/images/personalizzacookie.png	0.0 ms	1.6 KiB
www.comprooroalatina.com/images/accettasolocookienecessari.png	0.0 ms	1.6 KiB
www.comprooroalatina.com/images/rosso.gif	0.0 ms	1.5 KiB
www.comprooroalatina.com/images/salvaechiudi.png	0.0 ms	1.5 KiB
www.comprooroalatina.com/images/accettatuttiicookie.png	0.0 ms	1.4 KiB
www.comprooroalatina.com/css/reset.css	0.0 ms	815 B
www.comprooroalatina.com/images/arrow_right.png	0.0 ms	740 B
www.comprooroalatina.com/css/responsive.css	0.0 ms	679 B
www.comprooroalatina.com/css/layout.css	0.0 ms	632 B
www.comprooroalatina.com/js/script.js	0.0 ms	575 B
www.comprooroalatina.com/js/cufon-replace.js	0.0 ms	452 B

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:1] map[node:map[boundingRect:map[bottom:940 height:940 left:0 right:1350 top:0 width:1350] lhId:page-4-HTML nodeLabel:html.cufon-active path:1,HTML selector:html.cufon-active snippet:<html lang="it" itemscope="" itemtype="http://schema.org/LocalBusiness" class="cufon-active cufon-ready" style=""> type:node] score:1 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:143 height:143 left:0 right:1350 top:0 width:1350] lhId:page-1-IMG nodeLabel:body#page1 > div.body1 > img path:1,HTML,1,BODY,2,DIV,0,IMG selector:body#page1 > div.body1 > img snippet:<img src="./images/comproorolatina/topbanner.jpg"> type:node]]] type:subitems]]]

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div.rslides_container > ul#slider > li#centered-btns1_s0 > img `div.rslides_container > ul#slider > li#centered-btns1_s0 > img`	www.comprooroalatina.com/images/000.jpg	480.5 KiB	407.3 KiB
body#page1 > div.body1 > img `body#page1 > div.body1 > img`	www.comprooroalatina.com/images/comproorolatina/topbanner.jpg	434.8 KiB	403.3 KiB
center > p > a > img `center > p > a > img`	www.comprooroalatina.com/images/seguicisufacebook.png	27.9 KiB	23.0 KiB
form > center > a > img `form > center > a > img`	www.comprooroalatina.com/images/calcola.png	6.8 KiB	5.7 KiB

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: div.rslides_container > ul#slider > li#centered-btns1_s0 > img

path: 1,HTML,1,BODY,4,DIV,0,DIV,0,DIV,0,DIV,0,UL,0,LI,0,IMG

selector: div.rslides_container > ul#slider > li#centered-btns1_s0 > img

snippet: <img src="images/000.jpg" alt="">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
www.comprooroalatina.com/	http/1.1
www.comprooroalatina.com/css/reset.css	http/1.1
www.comprooroalatina.com/css/layout.css	http/1.1
www.comprooroalatina.com/css/style.css	http/1.1
www.comprooroalatina.com/css/zerogrid.css	http/1.1
www.comprooroalatina.com/css/responsive.css	http/1.1
www.comprooroalatina.com/css/responsiveslides.css	http/1.1
www.comprooroalatina.com/js/jquery-1.6.js	http/1.1
www.comprooroalatina.com/js/cufon-yui.js	http/1.1
www.comprooroalatina.com/js/cufon-replace.js	http/1.1
www.comprooroalatina.com/js/Swis721_Cn_BT_400.font.js	http/1.1
www.comprooroalatina.com/js/Swis721_Cn_BT_700.font.js	http/1.1
www.comprooroalatina.com/js/jquery.easing.1.3.js	http/1.1
www.comprooroalatina.com/js/tms-0.3.js	http/1.1
www.comprooroalatina.com/js/tms_presets.js	http/1.1
www.comprooroalatina.com/js/jcarousellite.js	http/1.1
www.comprooroalatina.com/js/script.js	http/1.1
www.comprooroalatina.com/js/css3-mediaqueries.js	http/1.1
www.comprooroalatina.com/js/responsiveslides.js	http/1.1
www.comprooroalatina.com/javascript/javascript.js	http/1.1
www.comprooroalatina.com/javascript/cookie.js	http/1.1
www.comprooroalatina.com/style/stili.css	http/1.1
www.comprooroalatina.com/style/verticalmenu.css	http/1.1
www.comprooroalatina.com/style/blu.css	http/1.1
www.comprooroalatina.com/include/javascript/scripts.js	http/1.1
www.comprooroalatina.com/images/accettatuttiicookie.png	http/1.1
www.comprooroalatina.com/images/accettasolocookienecessari.png	http/1.1
www.comprooroalatina.com/images/personalizzacookie.png	http/1.1
www.comprooroalatina.com/images/rosso.gif	http/1.1
www.comprooroalatina.com/images/salvaechiudi.png	http/1.1
www.comprooroalatina.com/images/comproorolatina/topbanner.jpg	http/1.1
www.comprooroalatina.com/images/000.jpg	http/1.1
www.comprooroalatina.com/images/001.jpg	http/1.1
www.comprooroalatina.com/images/002.jpg	http/1.1
www.comprooroalatina.com/images/005.jpg	http/1.1
www.comprooroalatina.com/images/arrow_right.png	http/1.1
www.comprooroalatina.com/images/calcola.png	http/1.1
www.comprooroalatina.com/images/seguicisufacebook.png	http/1.1
www.comprooroalatina.com/images/themes.gif	http/1.1
www.comprooroalatina.com/favicon.ico	http/1.1

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
www.comprooroalatina.com/include/javascript/scripts.js	169.8 KiB	285 ms
www.comprooroalatina.com/js/jquery-1.6.js	89.5 KiB	445 ms
www.comprooroalatina.com/javascript/javascript.js	10.8 KiB	85 ms
www.comprooroalatina.com/javascript/cookie.js	8.1 KiB	85 ms
www.comprooroalatina.com/js/css3-mediaqueries.js	15.9 KiB	125 ms
www.comprooroalatina.com/js/responsiveslides.js	9.3 KiB	85 ms
www.comprooroalatina.com/js/tms_presets.js	18.5 KiB	125 ms
www.comprooroalatina.com/js/jcarousellite.js	5.5 KiB
www.comprooroalatina.com/js/script.js	575 B
www.comprooroalatina.com/js/Swis721_Cn_BT_700.font.js	36.0 KiB	245 ms
www.comprooroalatina.com/js/Swis721_Cn_BT_400.font.js	37.1 KiB	245 ms
www.comprooroalatina.com/js/tms-0.3.js	8.4 KiB	85 ms
www.comprooroalatina.com/js/jquery.easing.1.3.js	8.2 KiB	85 ms
www.comprooroalatina.com/js/cufon-yui.js	18.1 KiB	125 ms
www.comprooroalatina.com/js/cufon-replace.js	452 B
www.comprooroalatina.com/style/verticalmenu.css	21.3 KiB	125 ms
www.comprooroalatina.com/style/blu.css	3.1 KiB
www.comprooroalatina.com/style/stili.css	20.8 KiB	125 ms
www.comprooroalatina.com/css/style.css	9.4 KiB	165 ms
www.comprooroalatina.com/css/responsive.css	679 B	125 ms
www.comprooroalatina.com/css/zerogrid.css	2.7 KiB	125 ms
www.comprooroalatina.com/css/responsiveslides.css	2.9 KiB	125 ms
www.comprooroalatina.com/css/layout.css	632 B	125 ms
www.comprooroalatina.com/css/reset.css	815 B

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

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 90 ms 120.6 KiB

URL	Transfer Size	Est Savings
www.comprooroalatina.com/include/javascript/scripts.js	169.6 KiB	89.6 KiB
www.comprooroalatina.com/js/tms_presets.js	18.2 KiB	9.6 KiB
www.comprooroalatina.com/js/responsiveslides.js	9.0 KiB	5.2 KiB
www.comprooroalatina.com/javascript/javascript.js	10.5 KiB	4.6 KiB
www.comprooroalatina.com/js/jquery.easing.1.3.js	7.9 KiB	4.5 KiB
www.comprooroalatina.com/javascript/cookie.js	7.9 KiB	4.3 KiB
www.comprooroalatina.com/js/jcarousellite.js	5.2 KiB	2.8 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 40.8 KiB

URL	Transfer Size	Est Savings
www.comprooroalatina.com/style/verticalmenu.css	21.1 KiB	20.6 KiB
www.comprooroalatina.com/style/stili.css	20.5 KiB	20.2 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: 170 ms 217.0 KiB

URL	Transfer Size	Est Savings
www.comprooroalatina.com/include/javascript/scripts.js	169.6 KiB	165.0 KiB
www.comprooroalatina.com/js/jquery-1.6.js	89.2 KiB	52.0 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 5.4 KiB

URL	Transfer Size	Est Savings
www.comprooroalatina.com/style/verticalmenu.css	21.3 KiB	2.9 KiB
www.comprooroalatina.com/style/stili.css	20.8 KiB	2.5 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.comprooroalatina.com/images/001.jpg	524.0 KiB
www.comprooroalatina.com/images/000.jpg	480.8 KiB
www.comprooroalatina.com/images/comproorolatina/topbanner.jpg	435.1 KiB
www.comprooroalatina.com/images/005.jpg	426.9 KiB
www.comprooroalatina.com/images/002.jpg	365.5 KiB
www.comprooroalatina.com/include/javascript/scripts.js	169.8 KiB
www.comprooroalatina.com/js/jquery-1.6.js	89.5 KiB
www.comprooroalatina.com/js/Swis721_Cn_BT_400.font.js	37.1 KiB
www.comprooroalatina.com/js/Swis721_Cn_BT_700.font.js	36.0 KiB
www.comprooroalatina.com/images/seguicisufacebook.png	28.2 KiB

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
body#page1 > div.body1 > img `body#page1 > div.body1 > img`	www.comprooroalatina.com/images/comproorolatina/topbanner.jpg
div.rslides_container > ul#slider > li#centered-btns1_s0 > img `div.rslides_container > ul#slider > li#centered-btns1_s0 > img`	www.comprooroalatina.com/images/000.jpg
center > p > a > img `center > p > a > img`	www.comprooroalatina.com/images/seguicisufacebook.png
div.cookiediv2 > p > a > img `div.cookiediv2 > p > a > img`	www.comprooroalatina.com/images/accettatuttiicookie.png
div.cookiediv2 > p > a > img `div.cookiediv2 > p > a > img`	www.comprooroalatina.com/images/personalizzacookie.png
h2 > div > div > img `h2 > div > div > img`	www.comprooroalatina.com/images/arrow_right.png
h2 > div > div > img `h2 > div > div > img`	www.comprooroalatina.com/images/arrow_right.png
h2 > div > div > img `h2 > div > div > img`	www.comprooroalatina.com/images/arrow_right.png
h2 > div > div > img `h2 > div > div > img`	www.comprooroalatina.com/images/arrow_right.png
h2 > div > div > img `h2 > div > div > img`	www.comprooroalatina.com/images/arrow_right.png

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 207 ms

URL	Time Spent
comprooroalatina.com/	207 ms
www.comprooroalatina.com/	0.0 ms

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
html.cufon-active `html.cufon-active`	1.000

●Time to Interactive 1.9 s

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●JavaScript execution time 0.0 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 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 50 ms

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

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
Quotazione Oro in Tempo Reale `center > p > font > b`
Quotazione Argento in Tempo Reale `center > p > font > b`
Informativa estesa sui cookies e sulla Policy & Privacy del sito `footer > font > a > b`
Modifica Preferenze Cookie `footer > font > a > b`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.cookiediv2 > p > a > img `div.cookiediv2 > p > a > img`
div.cookiediv2 > p > a > img `div.cookiediv2 > p > a > img`
div.cookiediv2 > p > a > img `div.cookiediv2 > p > a > img`
body#page1 > div.body1 > img `body#page1 > div.body1 > img`
h2 > div > div > img `h2 > div > div > img`
h2 > div > div > img `h2 > div > div > img`
h2 > div > div > img `h2 > div > div > img`
h2 > div > div > img `h2 > div > div > img`
h2 > div > div > img `h2 > div > div > img`
center > p > a > img `center > p > a > img`

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form > article#content2 > div.col-1-3 > input#quantita `form > article#content2 > div.col-1-3 > input#quantita`
form > article#content2 > div.col-1-3 > input#quantita_argento `form > article#content2 > div.col-1-3 > input#quantita_argento`

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
center > div.cookiediv2 > p > a `center > div.cookiediv2 > p > a`
center > div.cookiediv2 > p > a `center > div.cookiediv2 > p > a`
center > div.cookiediv2 > p > a `center > div.cookiediv2 > p > a`
center > form > center > a `center > form > center > a`
center > form > center > a `center > form > center > a`
section.col-full > center > p > a `section.col-full > center > p > a`

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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-hidden="true"]` is not present on the document `<body>`

●Select elements have associated label elements.

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

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

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

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` 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 use only permitted ARIA attributes

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

○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

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

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

○Buttons have an accessible name

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

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

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
div#cookiepreferenze > p > a > img `div#cookiepreferenze > p > a > img`	www.comprooroalatina.com/images/salvaechiudi.png	110 x 30 (3.67)	150 x 30 (5.00)

General

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
www.comprooroalatina.com/images/themes.gif	`Failed to load resource: the server responded with a status of 404 (Not Found)`

●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

●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

●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

●Page has valid source maps

○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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.cookiediv2 > p > a > img `div.cookiediv2 > p > a > img`
div.cookiediv2 > p > a > img `div.cookiediv2 > p > a > img`
div.cookiediv2 > p > a > img `div.cookiediv2 > p > a > img`
body#page1 > div.body1 > img `body#page1 > div.body1 > img`
h2 > div > div > img `h2 > div > div > img`
h2 > div > div > img `h2 > div > div > img`
h2 > div > div > img `h2 > div > div > img`
h2 > div > div > img `h2 > div > div > img`
h2 > div > div > img `h2 > div > div > img`
center > p > a > img `center > p > a > img`

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 have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid