2bmsrl.com website review

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

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

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

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

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

iubenda costs a phone 367 ms of main-thread work and 135 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.

1 file is served with short cache lifetimes, so returning visitors download them again (17 KiB).

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

4 third-party services load with your homepage (iubenda, Google Tag Manager and Google Fonts and others), adding 395 KiB and 477 ms of main-thread time.

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

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

5 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.3 MB in 202 requests on a phone: images 3.4 MB (14), scripts 706 KiB (156) and stylesheets 151 KiB (14). Under 2 MB keeps phones on slow connections fast.

chiusura_estiva_.png weighs 1.8 MB. On a phone connection a single image that size takes seconds.

9 images (2.6 MB) 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.

5 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example Screenshot_2026-11-04_084708_edited.png at 1,288 px wide, shown at 300 px. Resized copies would save about 203 KiB.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Produzione di diluenti, solventi, sgrassanti e ve…” and “Produzione di diluenti, solventi, sgrassanti e ve…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

The homepage links to 31 pages on 2bmsrl.com and 4 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 https://www.2bmsrl.com/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.

https://www.2bmsrl.com/default/linea-industria/diluenti-e-solventi.html, https://www.2bmsrl.com/default/news, https://www.2bmsrl.com/default/contact, https://www.2bmsrl.com/default/catalogsearch/advanced, https://www.2bmsrl.com/default/news/post/sostegno-all%E2%80%99autoproduzione-di-energia-da-fonti-rinnovabili-nelle-pmi and https://www.2bmsrl.com/default/news/category/in-vetrina and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.2bmsrl.com/default/diluenti-solventi-vernici-rivendita/diluenti-e-solventi.html, https://www.2bmsrl.com/default/diluenti-solventi-vernici-rivendita/impregnanti-smalti-legno-ferro-muratuta.html, https://www.2bmsrl.com/default/diluenti-solventi-vernici-rivendita/detergenti-sgrassanti-biologici.html, https://www.2bmsrl.com/default/linea-industria.html, https://www.2bmsrl.com/default/2bm-diluenti-solventi and https://www.2bmsrl.com/default/produzione-diluenti-solventi-tecnologia and 1 other took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

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

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

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

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

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