Website review, no card needed
casadasaliancas.com.br website review
Visit site (opens in a new tab)Reviewed 18 November 202655 issues · 91 checks
This review found 55 issues worth fixing on casadasaliancas.com.br, 21 of them high impact, across 91 checks. The most urgent: render-blocking requests. 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
57FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.6 s |
| Oct 31, 2026 | 3.6 s |
| Nov 7, 2026 | 3.5 s |
| Nov 14, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 316 ms |
| Jun 6, 2026 | 316 ms |
| Jun 13, 2026 | 321 ms |
| Jun 20, 2026 | 328 ms |
| Jun 27, 2026 | 331 ms |
| Jul 4, 2026 | 336 ms |
| Jul 11, 2026 | 337 ms |
| Jul 18, 2026 | 330 ms |
| Jul 25, 2026 | 331 ms |
| Aug 1, 2026 | 332 ms |
| Aug 8, 2026 | 337 ms |
| Aug 15, 2026 | 339 ms |
| Aug 22, 2026 | 337 ms |
| Aug 29, 2026 | 333 ms |
| Sep 5, 2026 | 330 ms |
| Sep 12, 2026 | 328 ms |
| Sep 19, 2026 | 330 ms |
| Sep 26, 2026 | 337 ms |
| Oct 3, 2026 | 340 ms |
| Oct 10, 2026 | 347 ms |
| Oct 17, 2026 | 349 ms |
| Oct 24, 2026 | 337 ms |
| Oct 31, 2026 | 329 ms |
| Nov 7, 2026 | 323 ms |
| Nov 14, 2026 | 320 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.0 s
2.1 s
3.1 s
4.1 s
5.2 s
6.2 s
7.2 s
8.2 s
Speed
Render-blocking requests
3.1 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Reduce unused JavaScript
1.4 s · 761 KiBAbout 761 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Reduce initial server response time
1.5 sReduce initial server response time. Google estimates savings of 1.5 s on a phone.
Document request latency
1.5 sThe HTML itself could arrive about 1.5 s sooner: redirects, a slow server response or missing compression delay everything after it.
Mobile performance score: 22
22/100Your mobile performance score is 22. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Facebook and others), adding 3.2 MB and 1.6 s of main-thread time.
Use efficient cache lifetimes
750 ms · 514 KiB24 files are served with short cache lifetimes, so returning visitors download them again (514 KiB).
vtexassets.com adds 472 ms
472 msvtexassets.com costs a phone 472 ms of main-thread work and 1.5 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.
Improve image delivery
450 ms · 111 KiB4 images could be 111 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 445 ms
445 msGoogle Tag Manager costs a phone 445 ms of main-thread work and 516 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 340 ms
340 msFacebook costs a phone 340 ms of main-thread work and 307 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
300 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 266 ms. During a long task the page ignores taps.
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.
Cloudflare CDN adds 48 ms
48 msCloudflare CDN costs a phone 48 ms of main-thread work and 494 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
150 ms · 24 KiBAbout 24 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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 CLS: 0.45
0.45For real visitors the layout shifts by 0.45 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 13.3 s
13.3 sYour largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Relógio Exclusivo Casa das Alianças”.
Time to Interactive: 23.7 s
23.7 sThe page becomes fully interactive after 23.7 s. Good is under 3.8 s.
First Contentful Paint: 5.6 s
5.6 sThe first text or image appears after 5.6 s on a phone. Good is under 1.8 s.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.413
0.413The layout shifts by 0.413 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 209 ms
209 msReal visitors wait 209 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 598 ms
598 msScripts block taps and scrolling for 598 ms in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 316 ms to 320 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, 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 LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 778 ms
778 msReal visitors wait 778 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 3.6 MB in 174 requests
3.6 MBYour homepage downloads 3.6 MB in 174 requests on a phone: scripts 2.2 MB (59), HTML 486 KiB (3) and images 412 KiB (27). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
4e651371-d4d8-4975-895e-4e86c0a273c4___4df5290ea37ea2a41fa09 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.0 g of CO₂ per visit
1.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 124.1 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
26 tap targets too small
26 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.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
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 (8 elements)
All page content should be contained by landmarks: 8 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.
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.
1 checks passed
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (17 characters)
Your title is only 17 characters: “Casa das Alianças”. Between 30 and 65 characters leaves room to say what you do and for whom.
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 (also missing: og:description), 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.
27 internal links, 0 external
The homepage links to 27 pages on casadasaliancas.com.br and 0 external pages.
4 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “Alianças e Joias de Ouro é na Maior e Mais Completa Loja de Joias, Alianças e Relógios do Brasil com Frete Grátis e Ent…”.
Canonical URL set
The canonical URL is https://www.casadasaliancas.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.casadasaliancas.com.br/sitemap.xml.
AI search readiness
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.casadasaliancas.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 (341 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a title
https://www.casadasaliancas.com.br/aliancas/aliancas-de-casamento and https://www.casadasaliancas.com.br/aliancas/aliancas-de-namoro have no <title>, so Google invents the link text in results.
2 pages share a title
/ and https://www.casadasaliancas.com.br/institucional/nossas-lojas all use the title “Casa das Alianças”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.casadasaliancas.com.br/aliancas/aliancas-de-casamento and https://www.casadasaliancas.com.br/aliancas/aliancas-de-namoro have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages share a meta description
https://www.casadasaliancas.com.br/institucional/nossas-lojas, https://www.casadasaliancas.com.br/alianca-de-ouro-18k-tradicional-lisa---as0001/p, https://www.casadasaliancas.com.br/alianca-de-ouro-18k-tradicional-lisa---as0002/p, https://www.casadasaliancas.com.br/alianca-de-ouro-18k-lisa---as0006/p, https://www.casadasaliancas.com.br/alianca-de-ouro-18k-noivado-fosco-e-liso-com-diamantes---as0598/p and https://www.casadasaliancas.com.br/anel-de-noivado and 7 others use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.casadasaliancas.com.br/institucional/nossas-lojas, https://www.casadasaliancas.com.br/aliancas/aliancas-de-casamento and https://www.casadasaliancas.com.br/aliancas/aliancas-de-namoro have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.casadasaliancas.com.br/alianca-de-ouro-18k-tradicional-lisa---as0002/p and https://www.casadasaliancas.com.br/anel-de-noivado took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
37 small tap targets
37 of 59 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
14 distorted images
14 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 365 words of copy
The homepage carries about 365 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Mixpanel and TikTok Pixel.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 3 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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
40 other companies contacted
Loading the homepage contacts 40 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 casadasaliancas.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
- 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 55 issues on casadasaliancas.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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.