Website review, no card needed

lazzoni.com logo

lazzoni.com website review

Visit site (opens in a new tab)Reviewed 17 November 202647 issues · 90 checks

This review found 47 issues worth fixing on lazzoni.com, 16 of them high impact, across 90 checks. The most urgent: page weight: 94.3 MB in 462 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
1.6 s1.1 sMay 30Nov 141.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.3 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.4 s
Nov 14, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
257 ms126 msMay 30Nov 14205 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026141 ms
Jun 6, 2026146 ms
Jun 13, 2026152 ms
Jun 20, 2026156 ms
Jun 27, 2026165 ms
Jul 4, 2026168 ms
Jul 11, 2026171 ms
Jul 18, 2026171 ms
Jul 25, 2026175 ms
Aug 1, 2026180 ms
Aug 8, 2026179 ms
Aug 15, 2026188 ms
Aug 22, 2026196 ms
Aug 29, 2026211 ms
Sep 5, 2026219 ms
Sep 12, 2026220 ms
Sep 19, 2026222 ms
Sep 26, 2026217 ms
Oct 3, 2026222 ms
Oct 10, 2026231 ms
Oct 17, 2026232 ms
Oct 24, 2026242 ms
Oct 31, 2026237 ms
Nov 7, 2026224 ms
Nov 14, 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 lazzoni.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lazzoni.com at 3.8 s3.8 s
  2. lazzoni.com at 7.6 s7.6 s
  3. lazzoni.com at 11.5 s11.5 s
  4. lazzoni.com at 15.3 s15.3 s
  5. lazzoni.com at 19.1 s19.1 s
  6. lazzoni.com at 22.9 s22.9 s
  7. lazzoni.com at 26.8 s26.8 s
  8. lazzoni.com at 30.6 s30.6 s

Speed

15 to fix37
  • Reduce unused JavaScript

    3.8 s · 912 KiB

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

  • Main-thread work: 15.3 s

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

  • Mobile performance score: 37

    37/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and Facebook and others), adding 2.4 MB and 2.0 s of main-thread time.

  • Google Tag Manager adds 958 ms

    958 ms

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

  • Use efficient cache lifetimes

    700 ms · 380 KiB

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

  • Improve image delivery

    300 ms · 401 KiB

    12 images could be 401 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 106 KiB

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

  • Clarity adds 350 ms

    350 ms

    Clarity costs a phone 350 ms of main-thread work and 32 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.

  • Render-blocking requests

    300 ms

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

  • 16 long tasks on the main thread

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

  • Facebook adds 256 ms

    256 ms

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

  • 2,076 HTML elements

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

  • Klaviyo adds 136 ms

    136 ms

    Klaviyo costs a phone 136 ms of main-thread work and 332 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.

  • Shopify adds 81 ms

    81 ms

    Shopify costs a phone 81 ms of main-thread work and 321 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

    200 ms · 30 KiB

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

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

  • 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: 15 ms

    15 ms

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

Core Web Vitals

9 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: 18.5 s

    18.5 s

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

  • Speed Index: 21.7 s

    21.7 s

    Visually, the page fills in at 21.7 s (Speed Index). Good is under 3.4 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: 944 ms

    944 ms

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 236 ms

    236 ms

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

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

    +49%

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

  • Largest content (LCP) got 16% slower for real visitors

    +16%

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

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 528 ms

    528 ms

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

  • Cumulative Layout Shift: 0.064

    0.064

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

Images and page weight

2 to fix64
  • Page weight: 94.3 MB in 462 requests

    94.3 MB

    Your homepage downloads 94.3 MB in 462 requests on a phone: media 88.6 MB (7), scripts 2.5 MB (119) and other files 1.6 MB (253). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    slider-mobile.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 26.7 g of CO₂ per visit

    26.73 g

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

2 checks passed
  • 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

9 to fixGoogle 8388
  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 18 images without alt text

    18 images have no alt text, which hurts accessibility and image search.

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

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 17 links without text

    17 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. (2 elements).

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

1 to fixGoogle 9297
  • No social preview image

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

  • 121 internal links, 11 external

    The homepage links to 121 pages on lazzoni.com and 11 external pages.

7 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Custom closets and modern furniture, made to order and built to last. Explore modular sofas, wardrobes and full-home de…”.

  • One H1 headline

    Your main headline reads: “A Closet Worth Doing Once.”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “LAZZONI Furniture: World's Best Premium Closets”.

  • Canonical URL set

    The canonical URL is https://lazzoni.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://lazzoni.com/sitemap.xml.

AI search readiness

100
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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://lazzoni.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix76
  • 2 pages share a title

    https://lazzoni.com/pages/custom-built-closets and https://lazzoni.com/pages/closets-design all use the title “Custom Closet Systems Made in Europe | LAZZONI Furniture”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://lazzoni.com/pages/wishlist has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://lazzoni.com/pages/custom-built-closets and https://lazzoni.com/pages/closets-design use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://lazzoni.com/pages/closets-design, whose canonical is https://lazzoni.com/pages/custom-built-closets. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://lazzoni.com/pages/book-a-design-appointment has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 55 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.

  • 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

4 to fixGoogle 9270
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=148020534&tm=gtm002&Ver=2&mid=32e9cd43-800f-4c39-96e4-b7cacb5ca308&bo=2&sid=9cd31d20e24111f18a04758cd38c3808&vid=9cd34030e24111f1bc9cfd29718f1e3a&vids=1&msclkid=N&pi=9.

  • 6 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 365 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call Us” and “GET A QUOTE”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Call Us212-242-0606”, “Book now” and “Shop by Room”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 4 mores (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.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 1 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.

  • 47 other companies contacted

    Loading the homepage contacts 47 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 lazzoni.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Intelligems A B Testing · Sc Easy 404 Ai Redirects · Lookfy Gallery · Microsoft Clarity · Klaviyo Email Marketing Sms · Avada Seo Suite · Gdpr Backpack · omegacommerce.com · cloudfront.net · robinpro.gallery · nfcube.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on lazzoni.com, including 24 speed issues, 1 SEO issue 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