brics.it website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, ZenDesk and Google Tag Manager and others), adding 1.5 MB and 1.3 s of main-thread time.

Shopify costs a phone 552 ms of main-thread work and 585 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.

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

ZenDesk costs a phone 273 ms of main-thread work and 396 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.

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

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

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

22 KiB could be saved by minifying JavaScript.

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

Desktop scores 59 but mobile only 24. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 169 ms to 187 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.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.6 MB in 303 requests on a phone: media 3.7 MB (1), images 2.0 MB (33) and scripts 1.7 MB (122). Under 2 MB keeps phones on slow connections fast.

5 images (203 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.

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

1 dropdown has no label.

Elements must only use permitted ARIA attributes: 91 elements on the page fail this check, rated serious by axe-core.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

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

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

The homepage links to 487 pages on brics.it and 9 external pages.

/pages/privacy-policy, /products/trolley-carry-on-volterra-trama-boe58117, /pages/store-locator, /pages/contact, /collections/new-arrivals and /collections/new-arrivals-luggage and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

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

/pages/privacy-policy, /products/trolley-carry-on-volterra-trama-boe58117, /pages/contact, /collections/new-arrivals, /collections/designed-to-move-with-ease and /collections/expandable-luggage and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=49000384&tm=gtm002&Ver=2&mid=555bb549-4a9c-4701-9b4f-f3c364736986&bo=3&sid=dc2e4de0cdce11f1afb19dc91aa2a680&vid=dc2e8360cdce11f1ace9397e940bb6b2&vids=0&msclkid=N&pi=91.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 537 words of visible text.

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

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

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