Website review, no card needed
anacapri.com.br website review
Visit site (opens in a new tab)Reviewed 31 October 202644 issues · 88 checks
This review found 44 issues worth fixing on anacapri.com.br, 19 of them high impact, across 88 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
57FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 328 ms |
| May 16, 2026 | 327 ms |
| May 23, 2026 | 327 ms |
| May 30, 2026 | 328 ms |
| Jun 6, 2026 | 336 ms |
| Jun 13, 2026 | 341 ms |
| Jun 20, 2026 | 344 ms |
| Jun 27, 2026 | 345 ms |
| Jul 4, 2026 | 348 ms |
| Jul 11, 2026 | 350 ms |
| Jul 18, 2026 | 346 ms |
| Jul 25, 2026 | 347 ms |
| Aug 1, 2026 | 352 ms |
| Aug 8, 2026 | 361 ms |
| Aug 15, 2026 | 375 ms |
| Aug 22, 2026 | 386 ms |
| Aug 29, 2026 | 383 ms |
| Sep 5, 2026 | 373 ms |
| Sep 12, 2026 | 386 ms |
| Sep 19, 2026 | 416 ms |
| Sep 26, 2026 | 452 ms |
| Oct 3, 2026 | 495 ms |
| Oct 10, 2026 | 511 ms |
| Oct 17, 2026 | 504 ms |
| Oct 24, 2026 | 497 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.9 s
2.8 s
3.7 s
4.7 s
5.6 s
6.5 s
7.5 s
Speed
Reduce unused JavaScript
2.1 s · 1,013 KiBAbout 1,013 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Google Tag Manager adds 1.3 s
1.3 sGoogle Tag Manager costs a phone 1.3 s of main-thread work and 926 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.3 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.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 (Google Tag Manager, TikTok and Clarity and others), adding 1.4 MB and 1.6 s of main-thread time.
Improve image delivery
750 ms · 926 KiB31 images could be 926 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 549 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
150 ms · 322 KiB62 files are served with short cache lifetimes, so returning visitors download them again (322 KiB).
Reduce unused CSS
300 ms · 56 KiBAbout 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Legacy JavaScript
150 ms · 66 KiBPolyfills for old browsers add 66 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 39 ms
39 msYour server sent the HTML in 39 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: 704 ms
704 msReal visitors wait 704 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.56
0.56For real visitors the layout shifts by 0.56 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 12.4 s
12.4 sYour largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bannermob1”.
Time to Interactive: 24.6 s
24.6 sThe page becomes fully interactive after 24.6 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 53% slower for real visitors
+53%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 328 ms to 497 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.161
0.161The layout shifts by 0.161 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 690 ms
690 msReal visitors wait 690 ms for your server to start answering (75th percentile). Good is under 800 ms.
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: 6.9 MB in 247 requests
6.9 MBYour homepage downloads 6.9 MB in 247 requests on a phone: media 2.8 MB (2), scripts 2.5 MB (100) and images 1.2 MB (61). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
MOBILE-5-.gif 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).
1 image in older formats
1 image (303 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.
1 image below the first screen load straight away
1 image further down the page (30 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.0 g of CO₂ per visit
1.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.95 g of CO₂e: 234.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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
Every image has alt text
All 44 images in the HTML carry an alt attribute.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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.
66 internal links, 16 external
The homepage links to 66 pages on anacapri.com.br and 16 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Tênis, sandálias, sapatilhas e bolsas femininas que descomplicam a rotina. Ganhe 10% OFF na 1ª compra com ANACAPRIPRIME…”.
Title: 55 characters
Your title is a healthy 55 characters: “ANACAPRI | Tênis, Sandálias, Bolsas e Sapatos Femininos”.
Canonical URL set
The canonical URL is https://www.anacapri.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.anacapri.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.
Parts of the site are closed to 1 AI crawler
Your robots.txt lets ChatGPT (ChatGPT-User) 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.anacapri.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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (415 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://www.anacapri.com.br/app, https://www.anacapri.com.br/cashback and https://www.anacapri.com.br/store-finder have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.anacapri.com.br/cashback and https://www.anacapri.com.br/c/sapatos/tenis/essenciais have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://www.anacapri.com.br/tenis-ale-lona-double-preto/p/3027700010005U, https://www.anacapri.com.br/bolsa-tiracolo-media-texturizada-preta/p/5001605060019U, https://www.anacapri.com.br/app, https://www.anacapri.com.br/store-finder and https://www.anacapri.com.br/c/sapatos/tenis/essenciais have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
5 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 broken images
4 images failed to load on a phone, for example https://cqbkhv.anacapri.com.br/g/uids?pld=Ck5CSY0Lr80QNUtNrM-0_TBaDfi4G-9lpFBaOntQK-ydnbrPi8ItRciytljxHHWCMPDwrQefCcz4bsO54kb-L7teWfFkxGMH9FArzQ5G51sRQoZcUx34XrHblreMEekSoE8Q0ey5h5ZGAvYYWhjuB34MLEJIqJ.
30 small tap targets
30 of 62 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.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Minified React error #425; visit https://reactjs.org/docs/error-decoder.html?invariant=425 for the full…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Requests the notification permission on page load
Requests the notification permission on page load.
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.
Thin social proof
Social proof on the homepage: 44 trust badges. 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 448 words of copy
The homepage carries about 448 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
27 cookies set on arrival
27Opening the homepage sets 27 cookies, 2 of them by other companies (measured from a US location before any click).
55 other companies contacted
Loading the homepage contacts 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 anacapri.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
- Next.js
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on anacapri.com.br, including 21 speed issues, 2 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.