Website review, no card needed
gimba.com.br website review
Visit site (opens in a new tab)Reviewed 26 October 202659 issues · 95 checks
This review found 59 issues worth fixing on gimba.com.br, 22 of them high impact, across 95 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
56FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.9 s |
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.2 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.5 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.9 s |
| Oct 17, 2026 | 4.8 s |
| Oct 24, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 222 ms |
| May 16, 2026 | 214 ms |
| May 23, 2026 | 203 ms |
| May 30, 2026 | 204 ms |
| Jun 6, 2026 | 206 ms |
| Jun 13, 2026 | 210 ms |
| Jun 20, 2026 | 216 ms |
| Jun 27, 2026 | 220 ms |
| Jul 4, 2026 | 221 ms |
| Jul 11, 2026 | 220 ms |
| Jul 18, 2026 | 217 ms |
| Jul 25, 2026 | 221 ms |
| Aug 1, 2026 | 230 ms |
| Aug 8, 2026 | 248 ms |
| Aug 15, 2026 | 267 ms |
| Aug 22, 2026 | 273 ms |
| Aug 29, 2026 | 277 ms |
| Sep 5, 2026 | 278 ms |
| Sep 12, 2026 | 275 ms |
| Sep 19, 2026 | 275 ms |
| Sep 26, 2026 | 275 ms |
| Oct 3, 2026 | 272 ms |
| Oct 10, 2026 | 273 ms |
| Oct 17, 2026 | 271 ms |
| Oct 24, 2026 | 273 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
1.2 s
2.4 s
3.5 s
4.7 s
5.9 s
7.1 s
8.3 s
9.5 s
Speed
Reduce unused JavaScript
2.4 s · 1.8 MBAbout 1.8 MB 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.
Render-blocking requests
2.3 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Use efficient cache lifetimes
1.4 s · 772 KiB154 files are served with short cache lifetimes, so returning visitors download them again (772 KiB).
Mobile performance score: 34
34/100Your mobile performance score is 34 (desktop: 29). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.8 s
A phone's processor spends 7.8 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,337 HTML elements
The page has 5,337 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.2 MB and 2.0 s of main-thread time.
Google CDN adds 953 ms
953 msGoogle CDN costs a phone 953 ms of main-thread work and 1.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.
Improve image delivery
650 ms · 447 KiB21 images could be 447 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Reduce unused CSS
900 ms · 121 KiBAbout 121 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Minify CSS
600 ms · 16 KiB16 KiB could be saved by minifying CSS.
Google Tag Manager adds 423 ms
423 msGoogle Tag Manager costs a phone 423 ms of main-thread work and 348 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 301 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 49 KiB49 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
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: 6 ms
6 msYour server sent the HTML in 6 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 TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 20.5 s
20.5 sYour largest element takes 20.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Gimba”.
Time to Interactive: 36.1 s
36.1 sThe page becomes fully interactive after 36.1 s. Good is under 3.8 s.
Speed Index: 13.5 s
13.5 sVisually, the page fills in at 13.5 s (Speed Index). Good is under 3.4 s.
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.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 285 ms
285 msReal visitors wait 285 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
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 222 ms to 273 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
34 images without width and height
34 images have no width and height attributes, so the layout jumps as each one loads.
1 checks passed
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 7.0 MB in 250 requests
7.0 MBYour homepage downloads 7.0 MB in 250 requests on a phone: scripts 3.0 MB (54), images 2.0 MB (107) and other files 1.1 MB (44). Under 2 MB keeps phones on slow connections fast.
11 images below the first screen load straight away
11 images further down the page (442 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (220 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.
About 2.0 g of CO₂ per visit
1.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.98 g of CO₂e: 237.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
72 buttons without a name
72 buttons have no accessible name, so screen readers announce just “button”.
50 text elements with low contrast
50 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
48 tap targets too small
48 tap targets are too small or too close together to hit reliably with a finger.
22 images without alt text
22 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (146 elements)
All page content should be contained by landmarks: 146 elements on the page fail this check, rated moderate by axe-core.
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.
40 form fields without a label
40 form fields have no label, so screen readers announce an empty box and autofill guesses.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 11 failed. 3 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.
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.
Meta description is long (215 characters)
Your meta description is 215 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
8 links crawlers can't follow
8 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
956 internal links, 26 external
The homepage links to 956 pages on gimba.com.br and 26 external pages.
3 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “Gimba, sua solução em abastecimento de suprimentos indiretos”.
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.gimba.com.br/sitemap.xml.
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://www.gimba.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (4,155 words), so crawlers that don't run JavaScript still read it.
Other pages
5 linked pages are broken
Your homepage links to https://www.gimba.com.br/natal, https://www.gimba.com.br/natal/cestas-de-natal, https://www.gimba.com.br/alimenticios, https://www.gimba.com.br/alimenticios/acucar and https://www.gimba.com.br/alimenticios/adocantes, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages share a title
/ and https://www.gimba.com.br/cupons all use the title “Gimba, sua solução em abastecimento de suprimentos indiretos”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without an H1
https://www.gimba.com.br/cupons has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 1 page 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 1 page that loaded have a <title>.
Best practices
22 small tap targets
22 of 82 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.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to execute 'insertBefore' on 'Node': Unexpected token ';'”.
11 distorted images
11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 846 words of copy
The homepage carries about 846 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Plásticos Adesivos e Contact”.
3 short forms
3 short forms (4 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, LinkedIn Insight and Cloudflare Web Analytics.
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 LinkedIn Insight 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.
15 cookies set on arrival
15Opening the homepage sets 15 cookies, 1 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.
31 other companies contacted
Loading the homepage contacts 31 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 gimba.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
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 gimba.com.br, including 27 speed issues, 7 SEO issues and 3 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.