Website review, no card needed
tramontina.com.br website review
Visit site (opens in a new tab)Reviewed 26 October 202659 issues · 97 checks
This review found 59 issues worth fixing on tramontina.com.br, 29 of them high impact, across 97 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
49F- #125,939 of 126,118 reviewed websitesbeats 0%
- #70,351 of 70,364 online storesbeats 0%
- #291 of 292 Salesforce Commerce Cloud storesbeats 0%
Closest competitors among Salesforce Commerce Cloud stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.4 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 453 ms |
| May 16, 2026 | 466 ms |
| May 23, 2026 | 478 ms |
| May 30, 2026 | 481 ms |
| Jun 6, 2026 | 474 ms |
| Jun 13, 2026 | 462 ms |
| Jun 20, 2026 | 453 ms |
| Jun 27, 2026 | 444 ms |
| Jul 4, 2026 | 444 ms |
| Jul 11, 2026 | 449 ms |
| Jul 18, 2026 | 446 ms |
| Jul 25, 2026 | 454 ms |
| Aug 1, 2026 | 471 ms |
| Aug 8, 2026 | 489 ms |
| Aug 15, 2026 | 525 ms |
| Aug 22, 2026 | 548 ms |
| Aug 29, 2026 | 562 ms |
| Sep 5, 2026 | 576 ms |
| Sep 12, 2026 | 551 ms |
| Sep 19, 2026 | 525 ms |
| Sep 26, 2026 | 514 ms |
| Oct 3, 2026 | 517 ms |
| Oct 10, 2026 | 532 ms |
| Oct 17, 2026 | 554 ms |
| Oct 24, 2026 | 596 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
2.0 s
4.0 s
5.9 s
7.9 s
9.9 s
11.9 s
13.9 s
15.9 s
Speed
Use efficient cache lifetimes
1.8 s · 1.0 MB71 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Main-thread work: 27.9 s
A phone's processor spends 27.9 s on main-thread work while loading, 17.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
23,012 HTML elements
The page has 23,012 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 1.9 s
1.9 sGoogle Tag Manager costs a phone 1.9 s of main-thread work and 1.3 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.
Render-blocking requests
1.6 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Google CDN adds 1.2 s
1.2 sGoogle CDN costs a phone 1.2 s of main-thread work and 1.9 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.
Facebook adds 1.2 s
1.2 sFacebook costs a phone 1.2 s of main-thread work and 317 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.
Mobile performance score: 3
3/100Your mobile performance score is 3 (desktop: 48). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 4.1 MB and 5.9 s of main-thread time.
Reduce unused JavaScript
850 ms · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 850 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.
Improve image delivery
640 KiB11 images could be 640 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
VWO adds 388 ms
388 msVWO costs a phone 388 ms of main-thread work and 172 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.
Other Google APIs/SDKs adds 385 ms
385 msOther Google APIs/SDKs costs a phone 385 ms of main-thread work and 178 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.
Reduce unused CSS
141 KiBAbout 141 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 48 but mobile only 3. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 37 ms
37 msYour server sent the HTML in 37 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user LCP: 6.0 s
6.0 sReal visitors wait 6.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 796 ms
796 msReal visitors wait 796 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.89
0.89For real visitors the layout shifts by 0.89 (75th percentile). Good is under 0.1.
Real-user FCP: 4.1 s
4.1 sReal visitors see the first content after 4.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.4 s
3.4 sReal visitors wait 3.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 9.7 s
9.7 sYour largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Aquece T Friday - Descontos quentíssimos!”. Most of its time is resource load delay (4.7 s).
Total Blocking Time: 8.8 s
8.8 sScripts block taps and scrolling for 8.8 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 45.6 s
45.6 sThe page becomes fully interactive after 45.6 s. Good is under 3.8 s.
Speed Index: 13.6 s
13.6 sVisually, the page fills in at 13.6 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.875
0.875The layout shifts by 0.875 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 453 ms to 596 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 7.9 MB in 279 requests
7.9 MBYour homepage downloads 7.9 MB in 279 requests on a phone: scripts 5.0 MB (77), images 1.5 MB (73) and other files 770 KiB (99). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
MOBILE-BANNER_AMPEZZO.jpg 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).
5 images in older formats
5 images (522 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.
2 images far larger than shown
178 KiB2 images are downloaded at several times the size a phone draws them, for example flag-campeos-venda-2.svg at 150 px wide, shown at 16 px. Resized copies would save about 178 KiB.
5 images below the first screen load straight away
5 images further down the page (305 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.2 g of CO₂ per visit
2.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.25 g of CO₂e: 269.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
12 form fields without a label
12 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 2 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: url points at a different host (https://www.tramontinastore.com/)”.
11 links with vague text
11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
2,534 internal links, 12 external
The homepage links to 2,534 pages on tramontina.com.br and 12 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Aproveite a Black Friday Tramontina para comprar panelas, utensílios, ferramentas, eletros, móveis e outros produtos co…”.
Title: 53 characters
Your title is a healthy 53 characters: “Black Friday Tramontina | Até 70% OFF na Loja Oficial”.
Canonical URL set
The canonical URL is https://www.tramontina.com.br/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.tramontina.com.br/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.tramontina.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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (6,232 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.tramontina.com.br/aquece-t-friday.html declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
https://www.tramontina.com.br/ambientes/cozinha/panelas and https://www.tramontina.com.br/panelas.html all use the title “Black Friday Tramontina: Ofertas em Panelas”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.tramontina.com.br/ambientes/cozinha/panelas and https://www.tramontina.com.br/panelas.html use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.tramontina.com.br/on/demandware.store/Sites-Tramontina-BR-Site/pt_BR/Stores-Find, https://www.tramontina.com.br/colecoes/design-collection, https://www.tramontina.com.br/respeito-pelo-seu-churrasco, https://www.tramontina.com.br/colecoes/master, https://www.tramontina.com.br/aquece-t-friday.html and https://www.tramontina.com.br/ambientes/cozinha/panelas and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.tramontina.com.br/aquece-t-friday.html took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 broken images
4 images failed to load on a phone, for example https://www.tramontina.com.br/.
50 small tap targets
50 of 119 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://api.reclameaqui.com.br/embed-raverified/hash/NDA5OnRyYW1vbnRpbmE=' from origin 'ht…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 12-field form
Your longest form asks for 12 fields (9 required). Every extra field lowers completion.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 2,142 words of copy
The homepage carries about 2,142 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar 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.
47 cookies set on arrival
47Opening the homepage sets 47 cookies, 3 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
60 other companies contacted
Loading the homepage contacts 60 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at tramontina.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 59 issues on tramontina.com.br, including 28 speed issues, 4 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.