tumibrasil.com website review

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

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

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

20 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

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

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

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

Facebook costs a phone 267 ms of main-thread work and 252 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 1,671 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.0 MB in 215 requests on a phone: images 4.1 MB (83), scripts 1.5 MB (53) and fonts 172 KiB (3). Under 2 MB keeps phones on slow connections fast.

assets/27f9d32f201b4265a2dc7bd7dfd6c175/31dfd4469fea4d7592a8 weighs 627 KiB. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example assets/a6fa4c6b68ab49528eb13c3071bae304/01a475740d0d4aaf9253 at 2,080 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

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

1 image (82 KiB) is 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.71 g of CO₂e: 204.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

All page content should be contained by landmarks: 11 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.

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

Headings should not be empty: 1 element on the page fails 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 → h4), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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 118 pages on tumibrasil.com and 9 external pages.

There is no https://tumibrasil.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.

/ and https://tumibrasil.com/compare all use the title “TUMI BRASIL | Malas, mochilas, bolsas e mais | Tumi Brasil”. Search engines can't tell which page to show for a search, so each competes with the others.

https://tumibrasil.com/collections/voyageur, https://tumibrasil.com/collections/harrison, https://tumibrasil.com/collections/voyageur-alpha-bravo, https://tumibrasil.com/collections/malas-de-viagem-tumi, https://tumibrasil.com/collections/acessorios and https://tumibrasil.com/collections/arrive and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://tumibrasil.com/collections/voyageur, https://tumibrasil.com/collections/harrison, https://tumibrasil.com/collections/voyageur-alpha-bravo, https://tumibrasil.com/collections/malas-de-viagem-tumi, https://tumibrasil.com/collections/mochilas and https://tumibrasil.com/collections/bolsas and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://view.cybbaview.com/impression.php?shopid=2473&placement=direct&domain=tumibrasil.com&dpath=tumibrasil.com%2F&country=US&platform=CybbaSolutions.

21 of 54 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 “Failed to execute 'appendChild' on 'Node': Unexpected token '<' https://tumibrasil.com/_next/static/chunks/5042-f462a86…”.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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 16 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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.