Website review, no card needed

baxter.it logo

baxter.it website review

Visit site (opens in a new tab)Reviewed 23 October 202627 issues · 97 checks

This review found 27 issues worth fixing on baxter.it, 10 of them high impact, across 97 checks. The most urgent: use efficient cache lifetimes. 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
6.0 s2.8 sMay 2Oct 174.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20265.6 s
May 9, 20265.4 s
May 16, 20265.2 s
May 23, 20265.0 s
May 30, 20264.8 s
Jun 6, 20264.7 s
Jun 13, 20264.5 s
Jun 20, 20264.6 s
Jun 27, 20264.9 s
Jul 4, 20265.3 s
Jul 11, 20265.0 s
Jul 18, 20264.4 s
Jul 25, 20263.4 s
Aug 1, 20263.1 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.4 s
Sep 12, 20263.6 s
Sep 19, 20264.2 s
Sep 26, 20264.1 s
Oct 3, 20264.2 s
Oct 10, 20264.2 s
Oct 17, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
259 ms87 msMay 2Oct 17153 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026239 ms
May 9, 2026223 ms
May 16, 2026206 ms
May 23, 2026190 ms
May 30, 2026173 ms
Jun 6, 2026154 ms
Jun 13, 2026132 ms
Jun 20, 2026125 ms
Jun 27, 2026129 ms
Jul 4, 2026120 ms
Jul 11, 2026112 ms
Jul 18, 2026114 ms
Jul 25, 2026107 ms
Aug 1, 2026111 ms
Aug 8, 2026113 ms
Aug 15, 2026112 ms
Aug 22, 2026123 ms
Aug 29, 2026134 ms
Sep 5, 2026138 ms
Sep 12, 2026138 ms
Sep 19, 2026143 ms
Sep 26, 2026143 ms
Oct 3, 2026147 ms
Oct 10, 2026150 ms
Oct 17, 2026153 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 baxter.it (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. baxter.it at 0.5 s0.5 s
  2. baxter.it at 0.9 s0.9 s
  3. baxter.it at 1.4 s1.4 s
  4. baxter.it at 1.8 s1.8 s
  5. baxter.it at 2.3 s2.3 s
  6. baxter.it at 2.7 s2.7 s
  7. baxter.it at 3.2 s3.2 s
  8. baxter.it at 3.6 s3.6 s

baxter.it does not allow embedding, so this is Google's rendering of the page.

Speed

5 to fix52
  • Use efficient cache lifetimes

    2.4 s · 889 KiB

    115 files are served with short cache lifetimes, so returning visitors download them again (889 KiB).

  • Reduce unused JavaScript

    1.5 s · 284 KiB

    About 284 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.

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    550 ms

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

  • Reduce unused CSS

    300 ms · 56 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Cookiebot, Azure Web Services and showefy.com and others), adding 549 KiB and 92 ms of main-thread time.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.

  • Font display

    100 ms

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

  • Improve image delivery

    94 KiB

    7 images could be 94 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 2.0 s

    A phone's processor spends 2.0 s on main-thread work while loading, 906 ms of it running JavaScript. That is comfortably low.

  • Server response: 110 ms

    110 ms

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

Core Web Vitals

8 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: 9.4 s

    9.4 s

    Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Utilizziamo i cookie per personalizzare contenuti ed annunc…”.

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Time to Interactive: 10.4 s

    10.4 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Total Blocking Time: 310 ms

    310 ms

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

  • 10 images without width and height

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

7 checks passed
  • Real-user INP: 130 ms

    130 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 792 ms

    792 ms

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

  • Tap response (INP) got 34% faster for real visitors

    -34%

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

  • Largest content (LCP) got 26% faster for real visitors

    -26%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

100
  • 1 image below the first screen load straight away

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

  • About 0.4 g of CO₂ per visit

    0.44 g

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

3 checks passed
  • Page weight: 1.6 MB in 142 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 142 requests on a phone: scripts 903 KiB (78), images 382 KiB (11) and fonts 179 KiB (3). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fix96
  • 4 text elements with low contrast

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

SEO

2 to fixGoogle 10093
  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("/logo.jpg")”.

  • No social preview image

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 26 internal links, 0 external

    The homepage links to 26 pages on baxter.it and 0 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Baxter was born from a passion for leather. Handcrafted to obtain unique and irreproducible sofas, armchairs, beds, cha…”.

  • One H1 headline

    Your main headline reads: “Baxter | Made in Italy”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Baxter | Sofas and designer furniture made in Italy”.

  • Canonical URL set

    The canonical URL is https://www.baxter.it/en.

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

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    27%

    A phone browser shows 259 words, but the HTML your server sends has only 69. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No llms.txt

    There is no /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.

  • Opted out of AI training for 1 crawler

    robots.txt blocks 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.

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, logo, description and contact details; url and sameAs (social profiles) would complete it.

Other pages

2 to fix90
  • 7 links to non-canonical URLs

    Your homepage links to 7 pages by a URL that isn't their canonical one, for example /en/categories/divani-e-poltrone, whose canonical is /en/categories/sofas-and-armchairs. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    /en/art-of-materials and /en/baxter-signature-projects have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    /en/categories/letti, /en/categories/set-letto, /en/categories/tappeti, /en/categories/illuminazione, /en/categories/collectible and /en/moods/mood-book-2026/botanique-mood have 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.

  • 5 pages slow to respond

    /en/categories/divani-e-poltrone, /en/categories/letti, /en/categories/sedie, /en/categories/tavoli-e-tavolini and /en/categories/complementi took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 9687
  • 17 small tap targets

    17 of 51 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • 2 redirects before the homepage

    Opening https://baxter.it goes through 2 redirects before the homepage loads.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

8 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (baxter.it).

  • Valid certificate (75 days left)

    The certificate from Let's Encrypt · YE1 verifies for baxter.it and is valid for another 75 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://baxter.it redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 26 links work

    All 26 links checked from your homepage (26 internal, 0 external) answered without errors.

Domain and trust

  • No CAA record

    baxter.it has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Content and conversion

5 to fix50
  • 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 social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 259 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Download” and “Contact us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Email authentication

1 to fix75
  • SPF does not block other senders (no all)

    Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 redirect=baxter.it.hosted.spf-report.com”.

  • Email authentication score: 75/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

2 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • DKIM signing found

    A DKIM key is published (selector “selector1”, “selector2” and “s1”), so receivers can verify mail really came from you.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

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

1 checks passed
  • Consent tool: Cookiebot

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

Upkeep, stack and company

Stack

Framework
Nuxt
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This free review found 27 issues on baxter.it, including 13 speed issues, 2 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