Lighthouse Mobile

· 0 checks — Mobile 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
img.pbol.it/pbit2021/img/logo_pb_100.gif	0.0 ms	196.3 KiB
/c76babb4-dc97-48b8-9b12-80b8b7deba04-web.js	900.0 s	156.6 KiB
img.pbol.it/pbit2021/img/centenario.png	0.0 ms	105.0 KiB
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	91.6 KiB
www.iolam.it/js/prebid.js	86400.0 s	115.4 KiB
www.paginebianche.it/repos_js/53687615487_20260626.js	172801.0 s	109.7 KiB
img.pbol.it/pbit2021/img/paginebianche-hero.png	0.0 ms	31.6 KiB
cdn.qwtag.com/97f2a049-4d4f-435b-9e27-4b01d746801e/qw.js	1800.0 s	27.3 KiB
i.plug.it/iplug/js/lib/iol/analytics/engine/IOL.Analytics.Tracking.min.js	1200.0 s	17.5 KiB
www.iolam.it/js/iam2.0.js?ns=paginebianche/web/home/1.5	86400.0 s	35.6 KiB
www.paginebianche.it/layout/font/JTURjIg1_i6t8kCHKm45_dJE3gnD_g.woff2	172801.0 s	20.1 KiB
www.paginebianche.it/layout/font/JTURjIg1_i6t8kCHKm45_c5H3gnD_g.woff2	172801.0 s	20.0 KiB
www.paginebianche.it/layout/font/JTURjIg1_i6t8kCHKm45_ZpC3gnD_g.woff2	172801.0 s	19.9 KiB
www.paginebianche.it/layout/font/JTUSjIg1_i6t8kCHKm459Wlhyw.woff2	172801.0 s	19.9 KiB
www.paginebianche.it/layout/font/JTURjIg1_i6t8kCHKm45_bZF3gnD_g.woff2	172801.0 s	19.8 KiB
i.plug.it/cmp/iub_conf_paginebianche.js	1200.0 s	3.9 KiB
i.plug.it/cmp/qciol.min.js	1200.0 s	2.8 KiB
i5.plug.it/cmp/V2.7/css/iub_conf_paginebianche.css	1200.0 s	2.4 KiB
cs.iubenda.com/cookie-solution/confs/js/23988380.js	3600.0 s	1.6 KiB
www.paginebianche.it/layout/registra-azienda.css	172801.0 s	3.9 KiB
/iplug/js/lib/iol/analytics/data/www-paginebianche-it/tra...	1200.0 s	1.2 KiB
img.pbol.it/pbit2021/img/social_x.svg	0.0 ms	785 B
www.paginebianche.it/pwa.js	172801.0 s	822 B
www.paginebianche.it/scripts/gtm.js	400000.0 s	861 B

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:0.825 source:map[column:58 line:130 type:source-location url:https://www.paginebianche.it/ 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:30.978 source:map[type:text value:[unattributed]]] map[reflowTime:0.825 source:map[column:8557 line:2 type:source-location url:https://i.plug.it/iplug/js/lib/iol/analytics/engine/IOL.Analytics.Tracking.min.js urlProvider:network]]]

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.navbar-pg__inner > div.d-flex > a > img `div.navbar-pg__inner > div.d-flex > a > img`	img.pbol.it/pbit2021/img/logo_pb_100.gif	195.7 KiB	185.1 KiB
Centenario Elenco telefonico italiano `div.row > div.col-md-6 > div.img-container > img`	img.pbol.it/pbit2021/img/centenario.png	104.5 KiB	85.6 KiB
Schermata telefono `div.addcompany-hp__row > div.addcompany-hp__col-right > div.addcompany-hp__image-wrap > img.addcompany-hp__image`	img.pbol.it/pbit2021/img/paginebianche-hero.png	31.2 KiB	26.7 KiB
Cittadini stranieri `article.box-guide__panel-itm > a.box-guide__panel-art > div.slider-img > img.swiper-lazy`	img.pbol.it/pbit2021/img/guide/Cittadini_Stranieri_1.jpg	16.5 KiB	9.9 KiB
Imprese `article.box-guide__panel-itm > a.box-guide__panel-art > div.slider-img > img.swiper-lazy`	img.pbol.it/pbit2021/img/guide/Imprese_2.jpg	14.9 KiB	8.4 KiB
Casa ed edilizia `article.box-guide__panel-itm > a.box-guide__panel-art > div.slider-img > img.swiper-lazy`	img.pbol.it/pbit2021/img/guide/CasaEdilizia.jpg	14.4 KiB	7.9 KiB
Smaltimento rifiuti `article.box-guide__panel-itm > a.box-guide__panel-art > div.slider-img > img.swiper-lazy`	img.pbol.it/pbit2021/img/guide/Smaltimento_rifiuti_1.jpg	13.0 KiB	6.5 KiB
Patente e circolazione `article.box-guide__panel-itm > a.box-guide__panel-art > div.slider-img > img.swiper-lazy`	img.pbol.it/pbit2021/img/guide/PatenteCircolazione.jpg	12.4 KiB	5.9 KiB
Disabilità `article.box-guide__panel-itm > a.box-guide__panel-art > div.slider-img > img.swiper-lazy`	img.pbol.it/pbit2021/img/guide/Disabilita.jpg	11.1 KiB	4.6 KiB

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

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
www.paginebianche.it/pwa.js	822 B
www.paginebianche.it/layout/registra-azienda.css	3.9 KiB

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

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: 1.5 s

URL	Time Spent
paginebianche.it/	779 ms
www.paginebianche.it/	765 ms
www.paginebianche.it/	0.0 ms

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

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: 5.3 s 917.4 KiB

URL	Transfer Size	Est Savings
/fd67ed16f9df/7792880e4562/d234d5526be5/challenge.js	571.5 KiB	317.7 KiB
/pagead/managed/js/gpt/m202606300101/pubads_impl.js?cb=31...	192.0 KiB	145.1 KiB
www.iolam.it/js/prebid.js	115.1 KiB	90.2 KiB
www.googletagmanager.com/gtag/js?id=G-M0YCJF293R&cx=c&gtm=4e6781	153.6 KiB	63.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-TZNGP3R	142.9 KiB	60.3 KiB
www.paginebianche.it/repos_js/53687615487_20260626.js	109.2 KiB	58.7 KiB
c.amazon-adsystem.com/aax2/apstag.js	91.2 KiB	58.6 KiB
cdn.iubenda.com/cookie_solution/iubenda_cs/1.102.0/core-it.js	111.9 KiB	55.8 KiB
/c76babb4-dc97-48b8-9b12-80b8b7deba04-web.js	156.0 KiB	40.1 KiB
www.iolam.it/js/iam2.0.js?ns=paginebianche/web/home/1.5	35.2 KiB	27.4 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/fd67ed16f9df/7792880e4562/d234d5526be5/challenge.js	822 ms	592 ms	151 ms
Unattributable	738 ms	158 ms	0.0 ms
www.paginebianche.it/	563 ms	86 ms	5.1 ms
cdn.iubenda.com/cookie_solution/iubenda_cs/1.102.0/core-it.js	417 ms	265 ms	56 ms
www.paginebianche.it/repos_js/53687615487_20260626.js	368 ms	255 ms	43 ms
www.googletagmanager.com/gtag/js?id=G-M0YCJF293R&cx=c&gtm=4e6781	357 ms	304 ms	50 ms
www.googletagmanager.com/gtm.js?id=GTM-TZNGP3R	279 ms	222 ms	52 ms
/c76babb4-dc97-48b8-9b12-80b8b7deba04-web.js	240 ms	145 ms	65 ms
/pagead/managed/js/gpt/m202606300101/pubads_impl.js?cb=31...	198 ms	143 ms	53 ms
www.iolam.it/js/prebid.js	176 ms	138 ms	37 ms
c.amazon-adsystem.com/aax2/apstag.js	110 ms	79 ms	26 ms
cdn.qwtag.com/97f2a049-4d4f-435b-9e27-4b01d746801e/qw.js	93 ms	71 ms	21 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	83 ms	73 ms	9.1 ms
www.iolam.it/js/iam2.0.js?ns=paginebianche/web/home/1.5	66 ms	47 ms	14 ms

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	2.7 s
Other	750 ms
Script Parsing & Compilation	601 ms
Style & Layout	325 ms
Parse HTML & CSS	218 ms
Rendering	43 ms
Garbage Collection	33 ms

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

URL	Transfer Size	Est Savings
@charset "UTF-8";/! Bootstrap v5.0.2 (https://getbootstrap.com/) * Copyright 2011-2021 The Boo…	48.0 KiB	42.3 KiB
	11.7 KiB	10.7 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
Schermata telefono `div.addcompany-hp__row > div.addcompany-hp__col-right > div.addcompany-hp__image-wrap > img.addcompany-hp__image`	img.pbol.it/pbit2021/img/paginebianche-hero.png
Centenario Elenco telefonico italiano `div.row > div.col-md-6 > div.img-container > img`	img.pbol.it/pbit2021/img/centenario.png
div.navbar-pg__inner > div.d-flex > a > img `div.navbar-pg__inner > div.d-flex > a > img`	img.pbol.it/pbit2021/img/logo_pb_100.gif

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,602 KiB

●User Timing marks and measures 8 user timings

●Avoid long main-thread tasks 20 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 250 ms

●Server Backend Latencies 210 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#extendedSearch > div#searchBar > form.hsearch__submit-form > button#searchSubmit `div#extendedSearch > div#searchBar > form.hsearch__submit-form > button#searchSubmit`

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.navbar-pg__inner > div.d-flex > a > img `div.navbar-pg__inner > div.d-flex > a > img`

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#searchBar > div#searchAziende > div.hsearch__input-group > a.hsearch__input-btn `div#searchBar > div#searchAziende > div.hsearch__input-group > a.hsearch__input-btn`
div#searchBar > div#searchAziende > div.hsearch__input-group > a.hsearch__input-btn `div#searchBar > div#searchAziende > div.hsearch__input-group > a.hsearch__input-btn`

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.

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
REGISTRA AZIENDA `div.navbar-pg__inner > nav.navbar-pg__nav > a.navbar-pg__nav-item > span`
ACCEDI `div#mybar > div#accessLinks > a.navbar-pg__nav-item > span`

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
EMERGENZE `main.main-page-container > div.pgcontainer > div.box-numeri > h4.text-center`

These are opportunities to improve keyboard navigation in your application.

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

●Form elements have associated labels

●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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

○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

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.paginebianche.it/manifest.json	`Manifest: Line: 1, column: 1, Syntax error.`
www.paginebianche.it/manifest.json	`Manifest: Line: 1, column: 1, Syntax error.`

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
div#header > div.navbar-pg__inner > div.d-flex > a.navbar-pg__btn-menu `div#header > div.navbar-pg__inner > div.d-flex > a.navbar-pg__btn-menu`
ACCEDI `nav.navbar-pg__nav > div#mybar > div#accessLinks > a.navbar-pg__nav-item`
`div#header > div.navbar-pg__row > div.navbar-pg__heading > a#anchorSearchBar`
body.page--homepage > div#sideMenu > div.sidemenu__header > a.p-10 `body.page--homepage > div#sideMenu > div.sidemenu__header > a.p-10`
Abbigliamento e accessori `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Casa e Giardino `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Cibo e bevande `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Edilizia `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Informatica e dispositivi elettronici `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Professionisti `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Pubblica utilità `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Servizi `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Sport, Hobby e Divertimento `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Viaggi, Veicoli e Trasporti `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Salute e Benessere `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
Tutti i Brand `nav.sidemenu__nav > div.multilevel_mobileMenu > div#openLevel > a.sidemenu__nav-item`
`div.dialog__wrapper > div.dialog__wrapper-inner > div.dialog__header > a.p-16`
`body.page--homepage > div#dialog_Search > a.dialog__overlay`
Aziende / Enti `div.hp-header > div.hp-header__content > div.search-type > a.search-type__btn`
Privati `div.hp-header > div.hp-header__content > div.search-type > a.search-type__btn`
div#extendedSearch > div#searchBar > div.hsearch__dropdown > a#searchTypeDropdown `div#extendedSearch > div#searchBar > div.hsearch__dropdown > a#searchTypeDropdown`
div#searchBar > div#searchAziende > div.hsearch__input-group > a.hsearch__input-btn `div#searchBar > div#searchAziende > div.hsearch__input-group > a.hsearch__input-btn`
div#searchBar > div#searchAziende > div.hsearch__input-group > a.hsearch__input-btn `div#searchBar > div#searchAziende > div.hsearch__input-group > a.hsearch__input-btn`
`div#searchBar > div#searchPrivati > div.hsearch__input-group > a.hsearch__input-btn`
`div#searchBar > div#searchPrivati > div.hsearch__input-group > a.hsearch__input-btn`

To appear in search results, crawlers need access to your app.

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.navbar-pg__inner > div.d-flex > a > img `div.navbar-pg__inner > div.d-flex > 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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`