trocafone.com.br website review

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.

Google CDN costs a phone 1.1 s of main-thread work and 1.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

vtexassets.com costs a phone 1.1 s of main-thread work and 1,003 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

Google Tag Manager costs a phone 674 ms of main-thread work and 533 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 95 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 540 ms faster on a phone.

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

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

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

2 images could be 153 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

Real visitors wait 448 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-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

Your homepage downloads 5.6 MB in 204 requests on a phone: scripts 3.8 MB (86), other files 1.1 MB (77) and HTML 237 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 15 pages on trocafone.com.br and 7 external pages.

Your homepage links to https://www.trocafone.com.br/148, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.trocafone.com.br/smartphones/smartphones/apple, https://www.trocafone.com.br/smartphones/smartphones/samsung, https://www.trocafone.com.br/smartphones/smartphones/motorola, https://www.trocafone.com.br/informatica, https://www.trocafone.com.br/informatica/notebooks-e-computadores and https://www.trocafone.com.br/tablets and 2 others have no <title>, so Google invents the link text in results.

https://www.trocafone.com.br/smartphones/smartphones/apple, https://www.trocafone.com.br/smartphones/smartphones/samsung, https://www.trocafone.com.br/smartphones/smartphones/motorola, https://www.trocafone.com.br/informatica, https://www.trocafone.com.br/informatica/notebooks-e-computadores and https://www.trocafone.com.br/tablets and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.trocafone.com.br/smartphones/smartphones/apple, https://www.trocafone.com.br/smartphones/smartphones/samsung, https://www.trocafone.com.br/smartphones/smartphones/motorola, https://www.trocafone.com.br/informatica, https://www.trocafone.com.br/informatica/notebooks-e-computadores and https://www.trocafone.com.br/tablets and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.trocafone.com.br/smartphones/smartphones/motorola, https://www.trocafone.com.br/informatica, https://www.trocafone.com.br/tablets, https://www.trocafone.com.br/smartphones/acessorios-para-smartphones and https://www.trocafone.com.br/Smartphones/Outlet took over 3 s to send their HTML from our server.

We fetched 12 pages linked from your homepage 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=97234736&Ver=2&mid=c5d03f94-3f6f-4ef0-93f7-5a7f3ea74745&bo=1&sid=20fceb00d15711f1a0d1e5ed88271f67&vid=20fd4f50d15711f1a67895eebd1158f5&vids=1&msclkid=N&pi=918639831&lg.

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

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

Chrome logged issues while loading the page (“Cookie”).

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.

The homepage has only about 50 words of visible text; thin pages give Google and first-time buyers little to go on.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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 Meta Pixel and 5 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 33 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 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.