Website review, no card needed
usebob.com.br website review
Visit site (opens in a new tab)Reviewed 6 November 202636 issues · 84 checks
This review found 36 issues worth fixing on usebob.com.br, 10 of them high impact, across 84 checks. The most urgent: 1 linked page is broken. 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
82B- #30,995 of 109,350 reviewed websitesbeats 66%
- #20,633 of 61,859 online storesbeats 60%
- #19,953 of 56,401 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 151 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 155 ms |
| Jun 6, 2026 | 158 ms |
| Jun 13, 2026 | 161 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 164 ms |
| Jul 4, 2026 | 166 ms |
| Jul 11, 2026 | 169 ms |
| Jul 18, 2026 | 169 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 159 ms |
| Aug 22, 2026 | 164 ms |
| Aug 29, 2026 | 175 ms |
| Sep 5, 2026 | 193 ms |
| Sep 12, 2026 | 204 ms |
| Sep 19, 2026 | 192 ms |
| Sep 26, 2026 | 181 ms |
| Oct 3, 2026 | 166 ms |
| Oct 10, 2026 | 155 ms |
| Oct 17, 2026 | 160 ms |
| Oct 24, 2026 | 161 ms |
| Oct 31, 2026 | 160 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.9 s
1.7 s
2.6 s
3.4 s
4.3 s
5.2 s
6.0 s
6.9 s
Speed
3,615 HTML elements
The page has 3,615 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, YouTube and Insider and others), adding 2.0 MB and 1.0 s of main-thread time.
Reduce unused JavaScript
150 ms · 1,002 KiBAbout 1,002 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 436 ms
436 msGoogle Tag Manager costs a phone 436 ms of main-thread work and 543 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.
Improve image delivery
350 ms · 126 KiB6 images could be 126 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
YouTube adds 352 ms
352 msYouTube costs a phone 352 ms of main-thread work and 991 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.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
350 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 290 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 168 KiBAbout 168 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.
Use efficient cache lifetimes
150 ms · 138 KiB9 files are served with short cache lifetimes, so returning visitors download them again (138 KiB).
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: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 728 ms
728 msScripts block taps and scrolling for 728 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 151 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 552 ms
552 msReal visitors wait 552 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.7 MB in 283 requests
3.7 MBYour homepage downloads 3.7 MB in 283 requests on a phone: scripts 2.0 MB (61), other files 705 KiB (111) and images 626 KiB (95). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BANNER_HOME_01_mobile_kits25off_1000x1214.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).
About 1.1 g of CO₂ per visit
1.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 126.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
61 text elements with low contrast
61 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (24 elements)
All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.
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.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (12 elements).
1 checks passed
46 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: 46 passed and 6 failed. 5 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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
274 internal links, 8 external
The homepage links to 274 pages on usebob.com.br and 8 external pages.
7 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Oi, eu sou a Bars Over Bottles, mas pode me chamar de B.O.B. Vem conhecer meus cosméticos em barra e junte-se a mim nes…”.
Title: 51 characters
Your title is a healthy 51 characters: “B.O.B: Produtos em Barra Para Cabelo, Rosto e Corpo”.
Canonical URL set
The canonical URL is https://www.usebob.com.br/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.usebob.com.br/sitemap.xml.
AI search readiness
Parts of the site are closed to 1 AI crawler
Your robots.txt lets ChatGPT search (OAI-SearchBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.
No llms.txt
There is no https://www.usebob.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
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 (2,526 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.usebob.com.br/collections/corpo-1, which answers with an error. Visitors hit a dead end and search engines drop it.
1 linked page hidden from search
https://www.usebob.com.br/products/desodorante-refil-bob is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 115 found) and read each the way a search engine does.
5 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 4 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
29 small tap targets
29 of 111 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
59 distorted images
59 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
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 2,026 words of copy
The homepage carries about 2,026 words of visible text.
2 checks passed
4 short forms
4 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.
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 usebob.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Insider · Tolstoy · Simple Social Login · rechargecdn.com · amazonaws.com · minhamais.com.br · magefan.top
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Sao Paulo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on usebob.com.br, including 14 speed issues, 1 SEO issue 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.