samsonite.com.br website review

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

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

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

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

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

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

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

Insider costs a phone 665 ms of main-thread work and 548 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.

Facebook costs a phone 399 ms of main-thread work and 281 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.

enviou.com.br costs a phone 366 ms of main-thread work and 55 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.

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

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

Polyfills for old browsers add 69 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

About 12 KiB of CSS is downloaded but never applied on this page.

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.

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.

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

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

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

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

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

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

Your homepage downloads 6.4 MB in 298 requests on a phone: images 3.8 MB (71), scripts 2.0 MB (82) and other files 304 KiB (132). Under 2 MB keeps phones on slow connections fast.

assets/4e9ccb447bcd4b15bc7a36c3b260e4f0/ce6f2bdb677b4c7bba69 weighs 625 KiB. On a phone connection a single image that size takes seconds.

assets/4e9ccb447bcd4b15bc7a36c3b260e4f0/44e3ab9079414364926a 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).

7 images are downloaded at several times the size a phone draws them, for example assets/4e9ccb447bcd4b15bc7a36c3b260e4f0/e883ef5b857d487daecf at 1,537 px wide, shown at 48 px. Resized copies would save about 470 KiB.

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

2 images (220 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 1.83 g of CO₂e: 219.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

17 buttons have no accessible name, so screen readers announce just “button”.

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

3 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: 9 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

Your title is 83 characters, so Google will cut it off around 60: “Samsonite Oficial | Malas, mochilas, bolsas e acessórios premium | Samsonite Brasil”.

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

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

The homepage links to 105 pages on samsonite.com.br and 15 external pages.

/ and https://samsonite.com.br/compare all use the title “Samsonite Oficial | Malas, mochilas, bolsas e acessórios premium | Sa…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://samsonite.com.br/pages/fretes-e-entregas, https://samsonite.com.br/pages/fale-conosco, https://samsonite.com.br/pages/central-de-ajuda, https://samsonite.com.br/pages/trocas-e-devolucoes, https://samsonite.com.br/pages/satisfacao-garantida and https://samsonite.com.br/pages/seja-um-franqueado and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://samsonite.com.br/pages/fale-conosco, https://samsonite.com.br/pages/central-de-ajuda, https://samsonite.com.br/pages/trocas-e-devolucoes, https://samsonite.com.br/pages/sustentabilidade, https://samsonite.com.br/pages/seja-um-franqueado and https://samsonite.com.br/pages/imprensa and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://samsonite.com.br/pages/sorteios has 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 69 found) and read each the way a search engine does.

3 images failed to load on a phone, for example https://samsonite.com.br/.

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

6 errors were logged to the browser console while the page loaded, for example “dataLayer is not defined <anonymous>:1:24”.

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.

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 26 cookies, 2 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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