Website review, no card needed
lojasrede.com.br website review
Visit site (opens in a new tab)Reviewed 26 October 202651 issues · 92 checks
This review found 51 issues worth fixing on lojasrede.com.br, 21 of them high impact, across 92 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.9 s |
| May 16, 2026 | 4.9 s |
| May 23, 2026 | 4.9 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 4.8 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 5.1 s |
| Jul 18, 2026 | 5.2 s |
| Jul 25, 2026 | 5.3 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.3 s |
| Aug 15, 2026 | 5.3 s |
| Aug 22, 2026 | 5.3 s |
| Aug 29, 2026 | 5.4 s |
| Sep 5, 2026 | 5.4 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 5.4 s |
| Sep 26, 2026 | 5.5 s |
| Oct 3, 2026 | 5.6 s |
| Oct 10, 2026 | 5.8 s |
| Oct 17, 2026 | 5.8 s |
| Oct 24, 2026 | 5.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 742 ms |
| May 16, 2026 | 767 ms |
| May 23, 2026 | 776 ms |
| May 30, 2026 | 786 ms |
| Jun 6, 2026 | 763 ms |
| Jun 13, 2026 | 747 ms |
| Jun 20, 2026 | 729 ms |
| Jun 27, 2026 | 705 ms |
| Jul 4, 2026 | 716 ms |
| Jul 11, 2026 | 695 ms |
| Jul 18, 2026 | 657 ms |
| Jul 25, 2026 | 626 ms |
| Aug 1, 2026 | 584 ms |
| Aug 8, 2026 | 547 ms |
| Aug 15, 2026 | 516 ms |
| Aug 22, 2026 | 489 ms |
| Aug 29, 2026 | 472 ms |
| Sep 5, 2026 | 456 ms |
| Sep 12, 2026 | 453 ms |
| Sep 19, 2026 | 448 ms |
| Sep 26, 2026 | 444 ms |
| Oct 3, 2026 | 437 ms |
| Oct 10, 2026 | 430 ms |
| Oct 17, 2026 | 423 ms |
| Oct 24, 2026 | 420 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.1 s
2.2 s
3.4 s
4.5 s
5.6 s
6.7 s
7.8 s
9.0 s
Speed
Reduce unused JavaScript
5.5 s · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.5 s faster on a phone.
Render-blocking requests
2.3 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
vtexassets.com adds 1.5 s
1.5 svtexassets.com costs a phone 1.5 s of main-thread work and 4.5 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.
Use efficient cache lifetimes
1.3 s · 361 KiB43 files are served with short cache lifetimes, so returning visitors download them again (361 KiB).
Reduce unused CSS
1.2 s · 256 KiBAbout 256 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 40
40/100Your mobile performance score is 40 (desktop: 49). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.2 s
A phone's processor spends 9.2 s on main-thread work while loading, 5.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,066 HTML elements
The page has 6,066 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 (vtexassets.com, Google Tag Manager and Google CDN and others), adding 6.3 MB and 3.1 s of main-thread time.
Google Tag Manager adds 718 ms
718 msGoogle Tag Manager costs a phone 718 ms of main-thread work and 674 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.
Legacy JavaScript
450 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 469 ms. During a long task the page ignores taps.
Google CDN adds 386 ms
386 msGoogle CDN costs a phone 386 ms of main-thread work and 737 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
228 KiB10 images could be 228 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
8 KiB8 KiB could be saved by minifying JavaScript.
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: 52 ms
52 msYour server sent the HTML in 52 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.
First Contentful Paint: 10.0 s
10.0 sThe first text or image appears after 10.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 24.2 s
24.2 sYour largest element takes 24.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tinturas Imedia”.
Time to Interactive: 32.2 s
32.2 sThe page becomes fully interactive after 32.2 s. Good is under 3.8 s.
Speed Index: 15.4 s
15.4 sVisually, the page fills in at 15.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 623 ms
623 msScripts block taps and scrolling for 623 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 454 ms
454 msReal visitors wait 454 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.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.9 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Tap response (INP) got 44% faster for real visitors
-44%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 742 ms to 420 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 317 requests
5.0 MBYour homepage downloads 5.0 MB in 317 requests on a phone: scripts 2.7 MB (68), images 937 KiB (65) and other files 868 KiB (174). Under 2 MB keeps phones on slow connections fast.
16 images below the first screen load straight away
16 images further down the page (686 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
50 KiB1 image is downloaded at several times the size a phone draws it, for example 336136-768-768 at 768 px wide, shown at 136 px. Resized copies would save about 50 KiB.
1 image in older formats
1 image (72 KiB) is 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 1.4 g of CO₂ per visit
1.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
25 text elements with low contrast
25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 form fields without a label
2 form fields have 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. (6 elements).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 4 problems
Structured data found (Organization and WebSite) but with 4 problems, 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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
154 internal links, 11 external
The homepage links to 154 pages on lojasrede.com.br and 11 external pages.
6 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “A lojas REDE está desde 1998 incentivando as pessoas a buscarem sua autoestima com produtos de alta qualidade das melho…”.
One H1 headline
Your main headline reads: “A maior REDE de cosméticos do Brasil”.
Title: 49 characters
Your title is a healthy 49 characters: “A maior REDE de cosméticos do Brasil | Lojas Rede”.
Canonical URL set
The canonical URL is https://www.lojasrede.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.lojasrede.com.br/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
60%The HTML your server sends has 594 of the 996 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Other pages
4 pages without a title
https://www.lojasrede.com.br/cabelos, https://www.lojasrede.com.br/cuidados-pessoais, https://www.lojasrede.com.br/ofertas and https://www.lojasrede.com.br/cabelos/acessorios have no <title>, so Google invents the link text in results.
4 pages without a meta description
https://www.lojasrede.com.br/cabelos, https://www.lojasrede.com.br/cuidados-pessoais, https://www.lojasrede.com.br/ofertas and https://www.lojasrede.com.br/cabelos/acessorios have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.lojasrede.com.br/institucional/politica-de-privacidade and https://www.lojasrede.com.br/agendamento-online use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://www.lojasrede.com.br/institucional/politica-de-privacidade, https://www.lojasrede.com.br/agendamento-online, https://www.lojasrede.com.br/cabelos, https://www.lojasrede.com.br/cuidados-pessoais, https://www.lojasrede.com.br/ofertas and https://www.lojasrede.com.br/cabelos/acessorios have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.lojasrede.com.br/cabelos, https://www.lojasrede.com.br/cuidados-pessoais, https://www.lojasrede.com.br/conveniencia, https://www.lojasrede.com.br/cupons and https://www.lojasrede.com.br/cabelos/acessorios took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 119 found) and read each the way a search engine does.
4 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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://zcwcep.lojasrede.com.br/g/uids?pld=W-Xo0jzTMED3YUzfHSFYcRzn-Nqgex-ma7HrL4OYNteh5-85LicM0EXJMiZjqtwOM-NRQH1z9cvwBwuz1TAvLM3r47UQFcX1_00XMajzagbpgoOcGJnqM6KAjwvgC0deqlrwncWbL0J3I_KXv7hnD_EU8AdHW.
24 small tap targets
24 of 52 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Unexpected token '}'”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 996 words of copy
The homepage carries about 996 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 2 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 (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.
39 other companies contacted
Loading the homepage contacts 39 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 lojasrede.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
- Hosting
- CloudFront
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 lojasrede.com.br, including 24 speed issues, 2 SEO issues and 5 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.