palazzoli.com website review

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

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

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

About 241 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

5 third-party services load with your homepage (Google CDN, iubenda and Google Tag Manager and others), adding 1.0 MB and 681 ms of main-thread time.

Google CDN costs a phone 459 ms of main-thread work and 733 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.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

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

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

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

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

0.png weighs 719 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example 0.png at 779 px wide, shown at 109 px. Resized copies would save about 648 KiB.

Your homepage downloads 3.6 MB in 54 requests on a phone: images 1.5 MB (23), scripts 1.1 MB (15) and fonts 424 KiB (5). Under 2 MB keeps phones on slow connections fast.

4 images (904 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.

2 images further down the page (83 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

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

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 85 pages on palazzoli.com and 7 external pages.

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.

https://www.palazzoli.com/en/products/electrical-systems and https://www.palazzoli.com/en/products/lighting all use the title “Products | Palazzoli”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.palazzoli.com/en/products/electrical-systems, https://www.palazzoli.com/en/composer/catalogue-general-2023, https://www.palazzoli.com/en/products/lighting, https://www.palazzoli.com/en/composer/catalogue-lighting-2025 and https://www.palazzoli.com/en/service/student have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.palazzoli.com/en/references/section/electrical-systems and https://www.palazzoli.com/en/references/section/lighting use the same meta description. A description written for each page earns more clicks.

https://www.palazzoli.com/en/products/electrical-systems, https://www.palazzoli.com/en/composer/catalogue-general-2023, https://www.palazzoli.com/en/news/electrical-systems, https://www.palazzoli.com/en/products/lighting, https://www.palazzoli.com/en/composer/catalogue-lighting-2025 and https://www.palazzoli.com/en/news/lighting and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.palazzoli.com/en/products/electrical-systems, https://www.palazzoli.com/en/products/lighting and https://www.palazzoli.com/en/service/student 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.

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

1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://fonts.googleapis.com/css2?family=Blinker:wght@300;400;600;700&display=swap' violates the followi…”.

Large scripts ship without source maps.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 278 words of visible text.

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

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

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