Website review, no card needed

baxi.it logo

baxi.it website review

Visit site (opens in a new tab)Reviewed 28 October 202641 issues · 86 checks

This review found 41 issues worth fixing on baxi.it, 18 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
2.3 s1.9 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
211 ms160 msMay 9Oct 24205 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026166 ms
May 16, 2026168 ms
May 23, 2026167 ms
May 30, 2026167 ms
Jun 6, 2026169 ms
Jun 13, 2026172 ms
Jun 20, 2026174 ms
Jun 27, 2026177 ms
Jul 4, 2026178 ms
Jul 11, 2026178 ms
Jul 18, 2026177 ms
Jul 25, 2026173 ms
Aug 1, 2026170 ms
Aug 8, 2026171 ms
Aug 15, 2026177 ms
Aug 22, 2026181 ms
Aug 29, 2026187 ms
Sep 5, 2026196 ms
Sep 12, 2026197 ms
Sep 19, 2026202 ms
Sep 26, 2026203 ms
Oct 3, 2026201 ms
Oct 10, 2026200 ms
Oct 17, 2026203 ms
Oct 24, 2026205 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 baxi.it (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. baxi.it at 0.6 s0.6 s
  2. baxi.it at 1.2 s1.2 s
  3. baxi.it at 1.8 s1.8 s
  4. baxi.it at 2.4 s2.4 s
  5. baxi.it at 3.0 s3.0 s
  6. baxi.it at 3.5 s3.5 s
  7. baxi.it at 4.1 s4.1 s
  8. baxi.it at 4.7 s4.7 s

Speed

14 to fix39
  • Improve image delivery

    33.1 s · 17.5 MB

    8 images could be 17.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 33.1 s faster on a phone.

  • Use efficient cache lifetimes

    25.9 s · 13.1 MB

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

  • Reduce unused JavaScript

    5.6 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.6 s faster on a phone.

  • Render-blocking requests

    1.7 s

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 4.9 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 19.7 MB and 860 ms of main-thread time.

  • sitecorecloud.io adds 0 ms

    0 ms

    sitecorecloud.io costs a phone 0 ms of main-thread work and 18.8 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.

  • 15 long tasks on the main thread

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

  • Reduce unused CSS

    480 ms · 226 KiB

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

  • Google Tag Manager adds 352 ms

    352 ms

    Google Tag Manager costs a phone 352 ms of main-thread work and 301 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.

  • Facebook adds 348 ms

    348 ms

    Facebook costs a phone 348 ms of main-thread work and 278 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.

  • Legacy JavaScript

    300 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 300 ms faster on a phone.

  • 2,117 HTML elements

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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

1 checks passed
  • Server response: 18 ms

    18 ms

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

Core Web Vitals

10 to fix67
  • 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: 50.3 s

    50.3 s

    Your largest element takes 50.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 50.3 s

    50.3 s

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

  • Total Blocking Time: 2.8 s

    2.8 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • Real-user INP: 228 ms

    228 ms

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

  • Tap response (INP) got 22% slower for real visitors

    +22%

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 21.3 MB in 77 requests

    21.3 MB

    Your homepage downloads 21.3 MB in 77 requests on a phone: images 18.8 MB (20), scripts 2.0 MB (23) and other files 271 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 17.0 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    14.1 MB

    12 images are downloaded at several times the size a phone draws them, for example Baxi_Ambientata_CSIINAlyaWH_grande.png at 3,296 px wide, shown at 390 px. Resized copies would save about 14.1 MB.

  • 16 images in older formats

    16 images (18.8 MB) 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.

  • 7 images below the first screen load straight away

    7 images further down the page (11.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.0 g of CO₂ per visit

    6.04 g

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

Accessibility

3 to fixGoogle 8695
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), 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. (1 element).

2 checks passed
  • Every image has alt text

    All 16 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8590
  • Title is short (11 characters)

    Your title is only 11 characters: “Baxi | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 236 internal links, 20 external

    The homepage links to 236 pages on baxi.it and 20 external pages.

7 checks passed
  • Meta description: 113 characters

    Your meta description is 113 characters: “Caldaie, pompe di calore e sistemi di raffrescamento per privati e professionisti. Scopri le novità firmate Baxi.”.

  • One H1 headline

    Your main headline reads: “Soluzioni tecnologicamente avanzate e facili da usare”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage.

  • 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.baxi.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.baxi.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,487 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix70
  • 1 page without a title

    https://www.baxi.it/professionista/area-riservata has no <title>, so Google invents the link text in results.

  • 2 pages without a meta description

    https://www.baxi.it/incentivi-fiscali/Finanziamento-Tasso-Zero-2026 and https://www.baxi.it/professionista/area-riservata have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.baxi.it/prodotti/pompe-di-calore/aria-acqua-monoblocco-inverter/Auriga-P, whose canonical is https://www.baxi.it/prodotti/pompe-di-calore/aria-acqua-monoblocco-inverter/auriga-p. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.baxi.it/prodotti/pompe-di-calore/aria-acqua-monoblocco-inverter/Auriga-P, https://www.baxi.it/news and https://www.baxi.it/professionista/area-riservata have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.baxi.it/promo-estensione-garanzia-clima, https://www.baxi.it/installatori/vicino-a-te, https://www.baxi.it/prodotti/pompe-di-calore/aria-acqua-monoblocco-inverter/Auriga-P, https://www.baxi.it/incentivi-fiscali/Finanziamento-Tasso-Zero-2026, https://www.baxi.it/news and https://www.baxi.it/professionista/area-riservata took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9293
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://7s-d309b5b93ece4e188e0aa4e9c7906f0f.ecs.us-west-1.on.aws/events?cee=no' violates the following C…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 903 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more and customize”.

  • 1 call to action

    The homepage has 1 call to action, for example “Baxi Shop”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

  • 9 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Safenames

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on baxi.it, including 24 speed issues, 2 SEO issues and 1 conversion gap. 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