tbox.com.br website review

17 images could be 632 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Facebook and others), adding 4.6 MB and 1.7 s of main-thread time.

vtexassets.com costs a phone 767 ms of main-thread work and 3.5 MB 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 541 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.

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

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

The HTML itself could arrive about 700 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 689 ms on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 600 ms.

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

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

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

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

Your server takes 789 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

nizza.com costs a phone 0 ms of main-thread work and 354 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.

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

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 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.83 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 205 ms to 305 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 4.9 MB in 126 requests on a phone: fonts 1.4 MB (5), scripts 1.4 MB (40) and images 1.3 MB (44). Under 2 MB keeps phones on slow connections fast.

32305485-ebfb-4e6c-94a7-504a628268aa___3b6fe4f65dcf7868324be 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).

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

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

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

3 elements hidden from screen readers can still receive keyboard focus.

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

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

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.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 8 characters: “Tool Box”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found ((untyped), ItemList and WebSite) but with 5 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

No Open Graph image (also missing: 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 56 pages on tbox.com.br and 1 external page.

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.tbox.com.br/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.

Your homepage links to https://www.tbox.com.br/1056 and https://www.tbox.com.br/161, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.tbox.com.br/gift-list-home has no <title>, so Google invents the link text in results.

https://www.tbox.com.br/fale-conosco, https://www.tbox.com.br/nossas-lojas, https://www.tbox.com.br/gift-list-home, https://www.tbox.com.br/maquina-de-cortar-pao-zassenhaus-pure-branca-562047/p, https://www.tbox.com.br/aparelho-de-jantar-18-pecas-escorial-white-vista-alegre-381577/p and https://www.tbox.com.br/aparelho-de-jantar-18-pecas-the-meaning-vista-alegre-381567/p and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tbox.com.br/fale-conosco, https://www.tbox.com.br/nossas-lojas and https://www.tbox.com.br/gift-list-home have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tbox.com.br/nossas-lojas 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.

https://www.tbox.com.br/zassenhaus took over 3 s to send its HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

2 images are displayed at the wrong aspect ratio, so they look 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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 491 words of visible text.

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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 13 cookies (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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.