Website review, no card needed

gabetti.it logo

gabetti.it website review

Visit site (opens in a new tab)Reviewed 31 October 202649 issues · 90 checks

This review found 49 issues worth fixing on gabetti.it, 18 of them high impact, across 90 checks. The most urgent: page weight: 44.8 MB in 169 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.6 s2.6 sMay 9Oct 243.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.7 s
May 16, 20262.8 s
May 23, 20262.9 s
May 30, 20263.2 s
Jun 6, 20263.4 s
Jun 13, 20263.5 s
Jun 20, 20263.4 s
Jun 27, 20263.1 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20263.2 s
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.3 s
Aug 22, 20263.2 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Oct 24, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
246 ms219 msMay 9Oct 24234 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026229 ms
May 16, 2026224 ms
May 23, 2026222 ms
May 30, 2026224 ms
Jun 6, 2026227 ms
Jun 13, 2026227 ms
Jun 20, 2026230 ms
Jun 27, 2026233 ms
Jul 4, 2026235 ms
Jul 11, 2026235 ms
Jul 18, 2026237 ms
Jul 25, 2026236 ms
Aug 1, 2026236 ms
Aug 8, 2026239 ms
Aug 15, 2026240 ms
Aug 22, 2026241 ms
Aug 29, 2026243 ms
Sep 5, 2026242 ms
Sep 12, 2026243 ms
Sep 19, 2026242 ms
Sep 26, 2026240 ms
Oct 3, 2026238 ms
Oct 10, 2026235 ms
Oct 17, 2026234 ms
Oct 24, 2026234 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

Full-page screenshot of gabetti.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gabetti.it at 1.4 s1.4 s
  2. gabetti.it at 2.8 s2.8 s
  3. gabetti.it at 4.2 s4.2 s
  4. gabetti.it at 5.6 s5.6 s
  5. gabetti.it at 7.0 s7.0 s
  6. gabetti.it at 8.4 s8.4 s
  7. gabetti.it at 9.7 s9.7 s
  8. gabetti.it at 11.1 s11.1 s

Speed

16 to fix36
  • Reduce unused JavaScript

    3.1 s · 767 KiB

    About 767 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • ekonsilio.io adds 1.5 s

    1.5 s

    ekonsilio.io costs a phone 1.5 s of main-thread work and 370 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 11.1 s

    A phone's processor spends 11.1 s on main-thread work while loading, 6.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    100 ms · 41.5 MB

    69 files are served with short cache lifetimes, so returning visitors download them again (41.5 MB).

  • Improve image delivery

    41.5 MB

    63 images could be 41.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (ekonsilio.io, iubenda and Google Maps and others), adding 42.7 MB and 2.4 s of main-thread time.

  • gabettigroup.com adds 0 ms

    0 ms

    gabettigroup.com costs a phone 0 ms of main-thread work and 41.4 MB 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.8 s. During a long task the page ignores taps.

  • Reduce unused CSS

    670 ms · 164 KiB

    About 164 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 670 ms faster on a phone.

  • Render-blocking requests

    750 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Legacy JavaScript

    350 ms · 35 KiB

    Polyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • iubenda adds 289 ms

    289 ms

    iubenda costs a phone 289 ms of main-thread work and 112 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.

  • Google Maps adds 229 ms

    229 ms

    Google Maps costs a phone 229 ms of main-thread work and 357 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.

  • userway.org adds 186 ms

    186 ms

    userway.org costs a phone 186 ms of main-thread work and 401 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.

  • 1,650 HTML elements

    The page has 1,650 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Minify CSS

    70 ms · 23 KiB

    23 KiB could be saved by minifying CSS.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 99 ms

    99 ms

    Your server sent the HTML in 99 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • 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.

  • Largest Contentful Paint: 23.0 s

    23.0 s

    Your largest element takes 23.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Questo sito utilizza cookies al fine di migliorarne la frui…”. Most of its time is element render delay (10.5 s).

  • Time to Interactive: 24.6 s

    24.6 s

    The page becomes fully interactive after 24.6 s. Good is under 3.8 s.

  • Total Blocking Time: 3.0 s

    3.0 s

    Scripts block taps and scrolling for 3.0 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 10.8 s

    10.8 s

    Visually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 2.7 s

    2.7 s

    Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 294 ms

    294 ms

    Real visitors wait 294 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.3 s

    2.3 s

    Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 229 ms to 234 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user CLS: 0.08

    0.08

    For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.018

    0.018

    The layout barely moves while loading (CLS 0.018, good is under 0.1).

Images and page weight

4 to fix25
  • Page weight: 44.8 MB in 169 requests

    44.8 MB

    Your homepage downloads 44.8 MB in 169 requests on a phone: images 42.4 MB (70), scripts 1.8 MB (61) and other files 293 KiB (31). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    1.8 MB

    3 images are downloaded at several times the size a phone draws them, for example be621407-c934-4839-a3e6-9bf9a4cc78b5.webp at 1,080 px wide, shown at 164 px. Resized copies would save about 1.8 MB.

  • 2 images in older formats

    2 images (897 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image below the first screen load straight away

    1 image further down the page (56 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 12.7 g of CO₂ per visit

    12.70 g

    By the Sustainable Web Design model, a visit to your homepage emits about 12.70 g of CO₂e: 1524.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

8 to fixGoogle 7989
  • 8 buttons without a name

    8 buttons have no accessible name, so screen readers announce just “button”.

  • ARIA attributes must conform to valid values (2 elements)

    ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

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

  • All page content should be contained by landmarks (30 elements)

    All page content should be contained by landmarks: 30 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (6 elements).

2 checks passed
  • Every image has alt text

    All 184 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10088
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (““Casa” inizia con la G!” and ““Casa” inizia con la G!”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 250 internal links, 7 external

    The homepage links to 250 pages on gabetti.it and 7 external pages.

5 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Affidati ai consulenti Gabetti per la ricerca di case e immobili commerciali in vendita. Da oltre 60 anni Gabetti è lea…”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Annunci immobiliari di case e locali commerciali”.

  • Canonical URL set

    The canonical URL is https://www.gabetti.it/.

  • 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.gabetti.it/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.gabetti.it/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,265 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.gabetti.it/news, whose canonical is https://www.gabetti.it/news?category=immobiliare. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page with very little text

    https://www.gabetti.it/vendita has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    18 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix30
  • 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.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 886 words of copy

    The homepage carries about 886 words of visible text.

Privacy and tracking

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 gabetti.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Next.js
Hosting
Fastweb

Company

Founded
1950
Headquarters
Milan

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on gabetti.it, including 26 speed issues, 3 SEO issues and 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25