Website review, no card needed
gamaitaly.com.br website review
Visit site (opens in a new tab)Reviewed 31 October 202655 issues · 96 checks
This review found 55 issues worth fixing on gamaitaly.com.br, 22 of them high impact, across 96 checks. The most urgent: document request latency. 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 344 ms |
| May 16, 2026 | 343 ms |
| May 23, 2026 | 336 ms |
| May 30, 2026 | 325 ms |
| Jun 6, 2026 | 326 ms |
| Jun 13, 2026 | 325 ms |
| Jun 20, 2026 | 328 ms |
| Jun 27, 2026 | 326 ms |
| Jul 4, 2026 | 323 ms |
| Jul 11, 2026 | 320 ms |
| Jul 18, 2026 | 309 ms |
| Jul 25, 2026 | 311 ms |
| Aug 1, 2026 | 311 ms |
| Aug 8, 2026 | 326 ms |
| Aug 15, 2026 | 344 ms |
| Aug 22, 2026 | 360 ms |
| Aug 29, 2026 | 369 ms |
| Sep 5, 2026 | 366 ms |
| Sep 12, 2026 | 365 ms |
| Sep 19, 2026 | 360 ms |
| Sep 26, 2026 | 367 ms |
| Oct 3, 2026 | 377 ms |
| Oct 10, 2026 | 395 ms |
| Oct 17, 2026 | 406 ms |
| Oct 24, 2026 | 403 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.4 s
2.8 s
4.2 s
5.7 s
7.1 s
8.5 s
9.9 s
11.3 s
Speed
Document request latency
1.4 sThe HTML itself could arrive about 1.4 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
1.4 sReduce initial server response time. Google estimates savings of 1.4 s on a phone.
Render-blocking requests
1.4 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
vtexassets.com adds 1.2 s
1.2 svtexassets.com costs a phone 1.2 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.
Mobile performance score: 27
27/100Your mobile performance score is 27. 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, 5.0 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 webtrafficsource.com and others), adding 5.1 MB and 3.8 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Google CDN adds 761 ms
761 msGoogle CDN costs a phone 761 ms of main-thread work and 2.7 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.
Use efficient cache lifetimes
300 ms · 485 KiB39 files are served with short cache lifetimes, so returning visitors download them again (485 KiB).
webtrafficsource.com adds 679 ms
679 mswebtrafficsource.com costs a phone 679 ms of main-thread work and 17 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 602 ms. During a long task the page ignores taps.
Google Tag Manager adds 417 ms
417 msGoogle Tag Manager costs a phone 417 ms of main-thread work and 392 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.
Server response: 1.6 s
1.6 sYour server takes 1.6 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Legacy JavaScript
200 ms · 67 KiBPolyfills for old browsers add 67 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
150 ms · 57 KiBAbout 57 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
191 KiB4 images could be 191 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
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 INP: 547 ms
547 msReal visitors wait 547 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 9.6 s
9.6 sYour largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 29.2 s
29.2 sThe page becomes fully interactive after 29.2 s. Good is under 3.8 s.
First Contentful Paint: 6.2 s
6.2 sThe first text or image appears after 6.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 2.6 s
2.6 sScripts block taps and scrolling for 2.6 s in total while the page loads. Good is under 200 ms.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 344 ms to 403 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 202 requests
5.2 MBYour homepage downloads 5.2 MB in 202 requests on a phone: scripts 2.9 MB (85), HTML 866 KiB (4) and other files 723 KiB (56). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
104 KiB2 images are downloaded at several times the size a phone draws them, for example 784029b0-2fc1-4f42-abf9-aef736fbf148___d8f41faacae5297ca5c37 at 1,920 px wide, shown at 390 px. Resized copies would save about 104 KiB.
4 images below the first screen load straight away
4 images further down the page (298 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 175.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
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. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Corporation, ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
68 internal links, 7 external
The homepage links to 68 pages on gamaitaly.com.br and 7 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Descubra a Gama Italy, sua loja de beleza e cuidados pessoais, com produtos inovadores que garantem resultados profissi…”.
One H1 headline
Your main headline reads: “GA.MA ITALY”.
Title: 60 characters
Your title is a healthy 60 characters: “Loja Oficial GA.MA Italy® - Produtos para cabelo e barbearia”.
Canonical URL set
The canonical URL is https://www.gamaitaly.com.br/.
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.gamaitaly.com.br/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.gamaitaly.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 contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (594 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.gamaitaly.com.br/iq and https://www.gamaitaly.com.br/506 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://www.gamaitaly.com.br/institucional/assistencia-tecnica and https://www.gamaitaly.com.br/institucional/fale-conosco all use the title “GAMA Italy - Beleza e Cuidado Pessoal”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://www.gamaitaly.com.br/iq, https://www.gamaitaly.com.br/506, https://www.gamaitaly.com.br/institucional/assistencia-tecnica and https://www.gamaitaly.com.br/institucional/fale-conosco use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.gamaitaly.com.br/prancha-de-cabelo, whose canonical is https://www.gamaitaly.com.br/cabelo/prancha-de-cabelo. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.gamaitaly.com.br/institucional/assistencia-tecnica and https://www.gamaitaly.com.br/institucional/fale-conosco have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://www.gamaitaly.com.br/escovas, https://www.gamaitaly.com.br/prancha-de-cabelo, https://www.gamaitaly.com.br/modeladores, https://www.gamaitaly.com.br/maquinas-de-corte, https://www.gamaitaly.com.br/barba-e-rosto and https://www.gamaitaly.com.br/acessorios and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.
3 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
6 broken images
6 images failed to load on a phone, for example https://www.gamaitaly.com.br/.
15 small tap targets
15 of 57 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.
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 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 364 words of copy
The homepage carries about 364 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 4 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Hotjar and TikTok Pixel.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 4 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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
56 other companies contacted
Loading the homepage contacts 56 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 gamaitaly.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
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 55 issues on gamaitaly.com.br, including 25 speed issues, 3 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.