Website review, no card needed
chatuba.com.br website review
Visit site (opens in a new tab)Reviewed 31 October 202660 issues · 78 checks
This review found 60 issues worth fixing on chatuba.com.br, 23 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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
41FClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
9.1 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.1 s faster on a phone.
Improve image delivery
1.2 s · 404 KiB10 images could be 404 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.
Use efficient cache lifetimes
1.2 s · 290 KiB21 files are served with short cache lifetimes, so returning visitors download them again (290 KiB).
Document request latency
1.1 sThe HTML itself could arrive about 1.1 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
1.1 sReduce initial server response time. Google estimates savings of 1.1 s on a phone.
Mobile performance score: 23
23/100Your mobile performance score is 23. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (vtexassets.com, Google CDN and Google Tag Manager and others), adding 4.6 MB and 2.9 s of main-thread time.
vtexassets.com adds 921 ms
921 msvtexassets.com costs a phone 921 ms of main-thread work and 2.1 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.
Google CDN adds 834 ms
834 msGoogle CDN costs a phone 834 ms of main-thread work and 1.4 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.
Reduce unused CSS
750 ms · 105 KiBAbout 105 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Avoid multiple page redirects
765 msThe page goes through 1 redirect before it starts loading, costing about 765 ms. Link and advertise the final URL directly.
Google Tag Manager adds 540 ms
540 msGoogle Tag Manager costs a phone 540 ms of main-thread work and 542 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 adds 269 ms
269 msFacebook costs a phone 269 ms of main-thread work and 224 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 on the main thread
20 long tasks block the main thread while loading, the longest for 284 ms. During a long task the page ignores taps.
1,564 HTML elements
The page has 1,564 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 1.2 s
1.2 sYour server takes 1.2 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Legacy JavaScript
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
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 CLS: 0.27
0.27For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 28.9 s
28.9 sYour largest element takes 28.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “banner”.
Speed Index: 17.3 s
17.3 sVisually, the page fills in at 17.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 29.2 s
29.2 sThe page becomes fully interactive after 29.2 s. Good is under 3.8 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 397 ms
397 msReal visitors wait 397 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 989 ms
989 msReal visitors wait 989 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.236
0.236The layout shifts by 0.236 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Images and page weight
Page weight: 5.2 MB in 204 requests
5.2 MBYour homepage downloads 5.2 MB in 204 requests on a phone: scripts 3.0 MB (66), other files 754 KiB (47) and images 741 KiB (74). Under 2 MB keeps phones on slow connections fast.
About 1.5 g of CO₂ per visit
1.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.48 g of CO₂e: 177.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Documents must have <title> element to aid in navigation (1 element)
Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
43 tap targets too small
43 tap targets are too small or too close together to hit reliably with a finger.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
1 checks passed
4 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 4 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://chatuba.com.br/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at chatuba.com.br/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://chatuba.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.
1 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
No character set
No character set is declared, so some characters can render as gibberish.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 0 words
The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 chatuba.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
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 60 issues on chatuba.com.br, including 30 speed issues, 11 SEO issues and 6 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.