Website review, no card needed
avvocato.it website review
Visit site (opens in a new tab)Reviewed 24 October 202634 issues · 82 checks
This review found 34 issues worth fixing on avvocato.it, 18 of them high impact, across 82 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
62D- #121,167 of 126,357 reviewed websitesbeats 3%
- #69,264 of 70,445 online storesbeats 1%
- #2,849 of 2,971 WooCommerce storesbeats 3%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.1 s |
| May 9, 2026 | 4.0 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.8 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 5.2 s |
| Aug 15, 2026 | 5.2 s |
| Aug 22, 2026 | 5.3 s |
| Aug 29, 2026 | 5.5 s |
| Sep 5, 2026 | 5.5 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 5.4 s |
| Sep 26, 2026 | 5.3 s |
| Oct 3, 2026 | 5.3 s |
| Oct 10, 2026 | 5.4 s |
| Oct 17, 2026 | 5.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 99 ms |
| May 9, 2026 | 99 ms |
| May 16, 2026 | 101 ms |
| May 23, 2026 | 101 ms |
| May 30, 2026 | 102 ms |
| Jun 6, 2026 | 101 ms |
| Jun 13, 2026 | 100 ms |
| Jun 20, 2026 | 102 ms |
| Jun 27, 2026 | 102 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 106 ms |
| Aug 29, 2026 | 110 ms |
| Sep 5, 2026 | 111 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 110 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 98 ms |
| Oct 10, 2026 | 98 ms |
| Oct 17, 2026 | 100 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.4 s
2.9 s
4.3 s
5.7 s
7.2 s
8.6 s
10.0 s
11.4 s
Speed
Render-blocking requests
4.8 s51 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Use efficient cache lifetimes
3.0 s · 962 KiB116 files are served with short cache lifetimes, so returning visitors download them again (962 KiB).
Reduce unused JavaScript
1.5 s · 216 KiBAbout 216 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Reduce unused CSS
1.1 s · 168 KiBAbout 168 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 35
35/100Your mobile performance score is 35 (desktop: 78). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 980 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
LiveChat adds 84 ms
84 msLiveChat costs a phone 84 ms of main-thread work and 369 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, LiveChat and Google Fonts and others), adding 691 KiB and 275 ms of main-thread time.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 78 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.66
0.66For real visitors the layout shifts by 0.66 (75th percentile). Good is under 0.1.
Real-user FCP: 4.7 s
4.7 sReal visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 12.0 s
12.0 sYour largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Noi e terze parti selezionate utilizziamo cookie o tecnolog…”. Most of its time is element render delay (10.2 s).
Speed Index: 17.8 s
17.8 sVisually, the page fills in at 17.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Time to Interactive: 12.7 s
12.7 sThe page becomes fully interactive after 12.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.389
0.389The layout shifts by 0.389 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) got 37% slower for real visitors
+37%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.1 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 99 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 100 ms
100 msReal visitors wait 100 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 174 ms
174 msScripts block the page for only 174 ms while loading. Good is under 200 ms.
Images and page weight
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 54.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 142 requests
1.6 MBYour homepage downloads 1.6 MB in 142 requests on a phone: scripts 887 KiB (78), fonts 339 KiB (9) and stylesheets 288 KiB (45). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h2 → h4, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
SEO
Title is short (23 characters)
Your title is only 23 characters: “Home - EN | Avvocato.it”. Between 30 and 65 characters leaves room to say what you do and for whom.
9 H1 headlines
There are 9 <h1> headlines (“Action, passion, and unwavering commitment to add…”, “We provide you with legal expertise and personali…” and “With a flexible, results-oriented approach, we wo…”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
103 internal links, 5 external
The homepage links to 103 pages on avvocato.it and 5 external pages.
6 checks passed
Meta description: 120 characters
Your meta description is 120 characters: “The lawyer for you! Legal advice and in-depth insights. Action, passion, and constant commitment to people’s real needs.”.
Canonical URL set
The canonical URL is https://www.avvocato.it/en/.
Structured data in place
Structured data found: Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.avvocato.it/sitemap_index.xml.
AI search readiness
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (807 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.avvocato.it/llms.txt (5 KiB, 41 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.avvocato.it/en and / all use the title “Home - EN | Avvocato.it”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.avvocato.it/settori-diritto-consulenza-assistenza and https://www.avvocato.it/settori-economici-consulenza-assistenza use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.avvocato.it/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
10 pages slow to respond
/, https://www.avvocato.it/settori-diritto-consulenza-assistenza, https://www.avvocato.it/settori-economici-consulenza-assistenza, https://www.avvocato.it/consulenza-assistenza-legale, https://www.avvocato.it/consulenza-imprese and https://www.avvocato.it/consulenza-persone and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
5 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Every page has a meta description
All 11 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
25 small tap targets
25 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “grecaptcha is not defined”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 918 words of copy
The homepage carries about 918 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 4 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at avvocato.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on avvocato.it, including 19 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.