lattebusche.com website review

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

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

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

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

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, YouTube and Google CDN and others), adding 3.3 MB and 1.7 s of main-thread time.

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

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

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

YouTube costs a phone 382 ms of main-thread work and 981 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 116 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.

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

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

gr-cdn.com costs a phone 106 ms of main-thread work and 461 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.

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

Polyfills for old browsers add 9 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.

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

4 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Lattebusche - latte, formaggi, yogurt e gelati delle Dolomi…”. Most of its time is resource load delay (2.8 s).

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

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

15 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 211 ms to 208 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 4.1 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.5 MB in 242 requests on a phone: scripts 3.4 MB (69), images 2.0 MB (103) and other files 363 KiB (21). Under 2 MB keeps phones on slow connections fast.

10 images (737 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 are downloaded at several times the size a phone draws them, for example BANNER_Siti-web.png at 2,830 px wide, shown at 198 px. Resized copies would save about 146 KiB.

6 images further down the page (420 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.85 g of CO₂e: 221.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 dropdowns have no label.

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

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

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

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

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

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

Your title is 71 characters, so Google will cut it off around 60: “Lattebusche - Latte, formaggi, yogurt e gelati delle Dolomiti Bellunesi”.

There are 5 <h1> headlines (“Lattebusche è 100% latte italiano, locale, di cas…”, “I nostri prodotti” and “Di Lattebusche potete fidarvi: 100% latte italian…”). One clear main headline is easier for people and search engines.

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

8 links have no real href, so search engines can't follow them.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 154 pages on lattebusche.com and 104 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.

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.

/categoria-prodotto/latte-e-latticini, /prodotto/latte-intero-biologico-di-montagna, /categoria-prodotto/latte-e-latticini/latte-fresco and /categoria-prodotto/latte-e-latticini/latte-uht took over 3 s to send their HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.7.2/css/all.css?ver=3.12.2' from origin 'https://w…”.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

2 links from your homepage to your own site are broken, for example https://www.lattebusche.com/?post_type=product&p=12226 (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

4 links go through two or more redirects, for example https://www.facebook.com/sharer.php?u=https%3A%2F%2Fwww.facebook.com%2F553393826835057%2Fposts%2F1543779011129862&t=Foto+dal+post+di+Lattebusche+Alta+Qualit%C3%A0.

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.

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

lattebusche.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

lattebusche.com 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.

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

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 885 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 Meta Pixel (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 24 cookies, 1 of them by other companies (measured from a US location before any click).

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