buffetti.it website review

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

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

Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.

About 530 KiB of JavaScript is downloaded but never used on this page.

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

8 third-party services load with your homepage (Klaviyo, Shopify and iubenda and others), adding 1.0 MB and 252 ms of main-thread time.

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

Klaviyo costs a phone 108 ms of main-thread work and 328 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 costs a phone 47 ms of main-thread work and 414 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.

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

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

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

48 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

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

5 KiB JavaScript is shipped twice across bundles.

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

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.

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

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

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

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

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

The layout shifts by 0.165 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 14.6 MB in 343 requests on a phone: media 11.1 MB (1), scripts 1.4 MB (86) and other files 1.3 MB (184). Under 2 MB keeps phones on slow connections fast.

f89fa36219638a9a5edebae33abe994fe9f49a87.png 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).

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 18 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 7 elements on the page fail this check, rated minor by axe-core.

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

Your title is 68 characters, so Google will cut it off around 60: “▷ Buffetti: Forniture per Ufficio, Cancelleria e Servizi per Imprese”.

Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: sameAs is an empty list”.

Your <h1> is empty.

The homepage links to 463 pages on buffetti.it and 11 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/blogs/notizie has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

1 link to other sites is dead, for example https://negozi.buffetti.it/ (500).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

The homepage has only about 195 words of visible text; thin pages give Google and first-time buyers little to go on.

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

The page uses urgency cues (a countdown or limited-time wording).

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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 10 cookies (measured from a US location before any click).

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