Website review, no card needed
montecarlo.com.br website review
Visit site (opens in a new tab)Reviewed 27 October 202621 issues · 76 checks
This review found 21 issues worth fixing on montecarlo.com.br, 4 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 264 ms |
| May 16, 2026 | 264 ms |
| May 23, 2026 | 269 ms |
| May 30, 2026 | 276 ms |
| Jun 6, 2026 | 279 ms |
| Jun 13, 2026 | 290 ms |
| Jun 20, 2026 | 295 ms |
| Jun 27, 2026 | 297 ms |
| Jul 4, 2026 | 298 ms |
| Jul 11, 2026 | 294 ms |
| Jul 18, 2026 | 288 ms |
| Jul 25, 2026 | 290 ms |
| Aug 1, 2026 | 292 ms |
| Aug 8, 2026 | 296 ms |
| Aug 15, 2026 | 297 ms |
| Aug 22, 2026 | 292 ms |
| Aug 29, 2026 | 287 ms |
| Sep 5, 2026 | 280 ms |
| Sep 12, 2026 | 300 ms |
| Sep 19, 2026 | 350 ms |
| Sep 26, 2026 | 391 ms |
| Oct 3, 2026 | 427 ms |
| Oct 10, 2026 | 444 ms |
| Oct 17, 2026 | 438 ms |
| Oct 24, 2026 | 437 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.7 s
1.4 s
2.2 s
2.9 s
3.6 s
4.3 s
5.1 s
5.8 s
Speed
Render-blocking requests
350 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.
Reduce unused JavaScript
335 KiBAbout 335 KiB of JavaScript is downloaded but never used on this page.
1,515 HTML elements
The page has 1,515 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
decocms.com adds 0 ms
0 msdecocms.com costs a phone 0 ms of main-thread work and 672 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.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, lilstts.com and decocms.com and others), adding 864 KiB and 170 ms of main-thread time.
Improve image delivery
222 KiB11 images could be 222 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 130 ms. During a long task the page ignores taps.
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.
Use efficient cache lifetimes
2 KiB3 files are served with short cache lifetimes, so returning visitors download them again (2 KiB).
3 checks passed
Mobile performance score: 97
97/100Your mobile performance score is 97 (desktop: 95). That is in Google's “good” band (90 and up).
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 458 ms of it running JavaScript. That is comfortably low.
Server response: 16 ms
16 msYour server sent the HTML in 16 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.
Real-user INP: 324 ms
324 msReal visitors wait 324 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 66% slower for real visitors
+66%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 264 ms to 437 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 4.5 s
4.5 sThe page becomes fully interactive after 4.5 s. Good is under 3.8 s.
9 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 572 ms
572 msReal visitors wait 572 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.1 s
3.1 sVisually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “Banner sobre o lançamento do aplicativo Monte Carlo”.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 90 ms
90 msScripts block the page for only 90 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
An image on the first screen is lazy-loaded
image 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 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.5 MB in 43 requests
1.5 MBYour homepage downloads 1.5 MB in 43 requests on a phone: scripts 711 KiB (10), images 676 KiB (23) and HTML 48 KiB (1). That is a lean page.
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
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail 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. (10 elements).
2 checks passed
Every image has alt text
All 37 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
143 internal links, 8 external
The homepage links to 143 pages on montecarlo.com.br and 8 external pages.
7 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Encontre na Monte Carlo anéis de diamante, pulseiras ouro 18k e relógios exclusivos. Garanta peças sofisticadas em cond…”.
One H1 headline
Your main headline reads: “Joias em Ouro 18k, Prata 925 e Relógios | Monte Carlo”.
Title: 53 characters
Your title is a healthy 53 characters: “Joias em Ouro 18k, Prata 925 e Relógios | Monte Carlo”.
Canonical URL set
The canonical URL is https://www.montecarlo.com.br/.
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.montecarlo.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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.
Text is in the HTML
Your server sends the page's text in the HTML (782 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.montecarlo.com.br/llms.txt (6 KiB, 60 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without an H1
https://www.montecarlo.com.br/nossas-lojas and https://www.montecarlo.com.br/joias-natan 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 100 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.
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 15 pages that loaded have a <title>.
Best practices
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
35 of 36 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.
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 452 words of copy
The homepage carries about 452 words of visible text.
2 checks passed
2 short forms
2 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
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.
7 other companies contacted
Loading the homepage contacts 7 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 montecarlo.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
- Tailwind CSS
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on montecarlo.com.br, including 9 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.