Website review, no card needed

lojasguaibim.com.br logo

lojasguaibim.com.br website review

Visit site (opens in a new tab)Reviewed 30 October 202651 issues · 92 checks

This review found 51 issues worth fixing on lojasguaibim.com.br, 19 of them high impact, across 92 checks. The most urgent: vtexassets.com adds 1.3 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.7 s4.3 sMay 9Oct 244.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.5 s
May 16, 20264.5 s
May 23, 20264.5 s
May 30, 20264.4 s
Jun 6, 20264.4 s
Jun 13, 20264.4 s
Jun 20, 20264.4 s
Jun 27, 20264.5 s
Jul 4, 20264.5 s
Jul 11, 20264.5 s
Jul 18, 20264.5 s
Jul 25, 20264.5 s
Aug 1, 20264.5 s
Aug 8, 20264.5 s
Aug 15, 20264.6 s
Aug 22, 20264.5 s
Aug 29, 20264.5 s
Sep 5, 20264.5 s
Sep 12, 20264.5 s
Sep 19, 20264.5 s
Sep 26, 20264.5 s
Oct 3, 20264.5 s
Oct 10, 20264.6 s
Oct 17, 20264.6 s
Oct 24, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
467 ms426 msMay 9Oct 24452 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026451 ms
May 16, 2026445 ms
May 23, 2026446 ms
May 30, 2026448 ms
Jun 6, 2026458 ms
Jun 13, 2026462 ms
Jun 20, 2026460 ms
Jun 27, 2026459 ms
Jul 4, 2026454 ms
Jul 11, 2026457 ms
Jul 18, 2026455 ms
Jul 25, 2026455 ms
Aug 1, 2026454 ms
Aug 8, 2026452 ms
Aug 15, 2026459 ms
Aug 22, 2026459 ms
Aug 29, 2026458 ms
Sep 5, 2026454 ms
Sep 12, 2026440 ms
Sep 19, 2026435 ms
Sep 26, 2026431 ms
Oct 3, 2026432 ms
Oct 10, 2026444 ms
Oct 17, 2026452 ms
Oct 24, 2026452 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

Full-page screenshot of lojasguaibim.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lojasguaibim.com.br at 0.9 s0.9 s
  2. lojasguaibim.com.br at 1.7 s1.7 s
  3. lojasguaibim.com.br at 2.6 s2.6 s
  4. lojasguaibim.com.br at 3.4 s3.4 s
  5. lojasguaibim.com.br at 4.3 s4.3 s
  6. lojasguaibim.com.br at 5.1 s5.1 s
  7. lojasguaibim.com.br at 6.0 s6.0 s
  8. lojasguaibim.com.br at 6.8 s6.8 s

Speed

15 to fix42
  • vtexassets.com adds 1.3 s

    1.3 s

    vtexassets.com costs a phone 1.3 s of main-thread work and 934 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.

  • Render-blocking requests

    1.2 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

  • Reduce initial server response time

    1.2 s

    Reduce initial server response time. Google estimates savings of 1.2 s on a phone.

  • Document request latency

    1.1 s

    The HTML itself could arrive about 1.1 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 8.3 s

    A phone's processor spends 8.3 s on main-thread work while loading, 4.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 Tag Manager and Google CDN and others), adding 4.1 MB and 3.4 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 1.5 MB

    About 1.5 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.

  • Use efficient cache lifetimes

    500 ms · 534 KiB

    21 files are served with short cache lifetimes, so returning visitors download them again (534 KiB).

  • Google CDN adds 512 ms

    512 ms

    Google CDN costs a phone 512 ms of main-thread work and 2.0 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 Tag Manager adds 663 ms

    663 ms

    Google Tag Manager costs a phone 663 ms of main-thread work and 548 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 390 ms

    390 ms

    Facebook costs a phone 390 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 398 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    300 ms · 49 KiB

    Polyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Server response: 1.3 s

    1.3 s

    Your server takes 1.3 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Reduce unused CSS

    150 ms · 119 KiB

    About 119 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

    80 KiB

    2 images could be 80 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

Core Web Vitals

12 to fix0
  • 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 FCP: 3.1 s

    3.1 s

    Real visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.

  • Time to Interactive: 20.3 s

    20.3 s

    The page becomes fully interactive after 20.3 s. Good is under 3.8 s.

  • Total Blocking Time: 1.8 s

    1.8 s

    Scripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 7.7 s

    7.7 s

    Visually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 4.9 s

    4.9 s

    Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Real-user LCP: 3.2 s

    3.2 s

    Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 420 ms

    420 ms

    Real visitors wait 420 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.21

    0.21

    For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.8 s

    2.8 s

    The first text or image appears after 2.8 s on a phone. Good is under 1.8 s.

  • 16 images without width and height

    16 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +1%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 451 ms to 452 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.5 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 checks passed
  • Cumulative Layout Shift: 0.062

    0.062

    The layout barely moves while loading (CLS 0.062, good is under 0.1).

Images and page weight

2 to fix75
  • Page weight: 3.2 MB in 150 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 150 requests on a phone: scripts 2.3 MB (69), other files 404 KiB (41) and HTML 199 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    74 KiB

    1 image is downloaded at several times the size a phone draws it, for example ab1746b7-931f-43d1-b50e-9fe9ce32386c___3df4308415fdaee175249 at 7,549 px wide, shown at 53 px. Resized copies would save about 74 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (74 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.92 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 109.9 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

8 to fixGoogle 8289
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 14 tap targets too small

    14 tap targets are too small or too close together to hit reliably with a finger.

  • 6 text elements with low contrast

    6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Orphan list items

    Some list items are not inside a list.

  • 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has 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.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10082
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 1 problem

    Structured data found (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.

  • 35 internal links, 8 external

    The homepage links to 35 pages on lojasguaibim.com.br and 8 external pages.

5 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Encontre ofertas incríveis em geladeiras, fogões, móveis, eletrônicos e muito mais na Lojas Guaibim. Entrega rápida em …”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Lojas Guaibim - A maior loja de eletromóveis da Bahia!”.

  • Canonical URL set

    The canonical URL is https://www.lojasguaibim.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.lojasguaibim.com.br/sitemap.xml.

AI search readiness

1 to fix88
  • 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.lojasguaibim.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 (249 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages share a title

    https://www.lojasguaibim.com.br/institucional/nossas-lojas, https://www.lojasguaibim.com.br/institucional/quem-somos and https://www.lojasguaibim.com.br/institucional/politicas-de-privacidade all use the title “Lojas Guaibim | Eletrodomésticos, Móveis e Eletrônicos com Ofertas Im…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://www.lojasguaibim.com.br/institucional/regras-das-campanhas, https://www.lojasguaibim.com.br/institucional/nossas-lojas, https://www.lojasguaibim.com.br/institucional/quem-somos, https://www.lojasguaibim.com.br/institucional/politicas-de-privacidade and https://www.lojasguaibim.com.br/institucional/como-comprar use the same meta description. A description written for each page earns more clicks.

  • 4 pages slow to respond

    https://www.lojasguaibim.com.br/celulares-e-telefonia, https://www.lojasguaibim.com.br/geladeira-lg-inverter-frost-free-inverse-451l-gc-b569nllm-inox/p, https://www.lojasguaibim.com.br/tanquinho-lavadora-semiautomatica-colormaq-20kg-lcs-20-br-branco/p and https://www.lojasguaibim.com.br/institucional/quem-somos took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.

6 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9687
  • 32 small tap targets

    32 of 58 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: jQuery is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 226 words

    The homepage has only about 226 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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.

3 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Mixpanel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 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.

  • 36 other companies contacted

    Loading the homepage contacts 36 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 lojasguaibim.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

Framework
React
Analytics
Google Tag Manager | Mixpanel
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on lojasguaibim.com.br, including 27 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25