Website review, no card needed
imigrantesbebidas.com.br website review
Visit site (opens in a new tab)Reviewed 21 October 202645 issues · 91 checks
This review found 45 issues worth fixing on imigrantesbebidas.com.br, 17 of them high impact, across 91 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 182 ms |
| May 9, 2026 | 183 ms |
| May 16, 2026 | 184 ms |
| May 23, 2026 | 184 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 187 ms |
| Jun 13, 2026 | 189 ms |
| Jun 20, 2026 | 190 ms |
| Jun 27, 2026 | 189 ms |
| Jul 4, 2026 | 190 ms |
| Jul 11, 2026 | 190 ms |
| Jul 18, 2026 | 188 ms |
| Jul 25, 2026 | 187 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 195 ms |
| Aug 22, 2026 | 197 ms |
| Aug 29, 2026 | 199 ms |
| Sep 5, 2026 | 197 ms |
| Sep 12, 2026 | 196 ms |
| Sep 19, 2026 | 197 ms |
| Sep 26, 2026 | 199 ms |
| Oct 3, 2026 | 200 ms |
| Oct 10, 2026 | 201 ms |
| Oct 17, 2026 | 197 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.1 s · 311 KiBAbout 311 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 93). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,746 HTML elements
The page has 6,746 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 Tag Manager, Cloudflare CDN and moengage.com and others), adding 790 KiB and 504 ms of main-thread time.
Improve image delivery
474 KiB9 images could be 474 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 350 ms
350 msGoogle Tag Manager costs a phone 350 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.
Reduce unused CSS
300 ms · 18 KiBAbout 18 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 818 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 202 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
150 ms · 16 KiB3 files are served with short cache lifetimes, so returning visitors download them again (16 KiB).
Duplicated JavaScript
150 ms · 15 KiB15 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 93 but mobile only 43. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 317 ms
317 msYour server sent the HTML in 317 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.
Cumulative Layout Shift: 1.142
1.142The layout shifts by 1.142 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 8.8 s
8.8 sYour largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Quarta Breja”.
Time to Interactive: 9.0 s
9.0 sThe page becomes fully interactive after 9.0 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
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: 222 ms
222 msReal visitors wait 222 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.17
0.17For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 182 ms to 197 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Total Blocking Time: 125 ms
125 msScripts block the page for only 125 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
260814-banner-cronofertas-m.20260814170210.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).
4 images in older formats
4 images (405 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 0.5 g of CO₂ per visit
0.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.8 MB in 77 requests
1.8 MBYour homepage downloads 1.8 MB in 77 requests on a phone: images 827 KiB (25), scripts 809 KiB (27) and HTML 91 KiB (1). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
<svg> elements with an img or image role must have alternative text (126 elements)
<svg> elements with an img or image role must have alternative text: 126 elements on the page fail this check, rated serious by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Frames without titles
6 frames have no title, so screen-reader users cannot tell what they contain.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
289 form fields without a label
289 form fields have no label, so screen readers announce an empty box and autofill guesses.
All page content should be contained by landmarks (67 elements)
All page content should be contained by landmarks: 67 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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 172 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is long (90 characters)
Your title is 90 characters, so Google will cut it off around 60: “Imigrantes Bebidas | Tudo para beber. Vinho, vodka, whisky, cacha�a, cerveja, refrigerante”.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
633 internal links, 27 external
The homepage links to 633 pages on imigrantesbebidas.com.br and 27 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Imigrantes Bebidas | Tudo para beber. Vinho, vodka, whisky, cacha�a, cerveja, refrigerante”.
Canonical URL set
The canonical URL is https://www.imigrantesbebidas.com.br/bebida/vitrine.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.imigrantesbebidas.com.br/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.imigrantesbebidas.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (3,547 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.imigrantesbebidas.com.br/promocoes has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.imigrantesbebidas.com.br/recorrencia and https://www.imigrantesbebidas.com.br/carrinho use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.imigrantesbebidas.com.br/carrinho and https://www.imigrantesbebidas.com.br/cachaca have 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 184 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
2 checks passed
Tap targets are thumb-sized
205 of 216 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 1,025 words of copy
The homepage carries about 1,025 words of visible text.
4 checks passed
145 short forms
145 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 12 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (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.
13 other companies contacted
Loading the homepage contacts 13 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 imigrantesbebidas.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on imigrantesbebidas.com.br, including 20 speed issues, 4 SEO issues and 4 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.