Website review, no card needed
anita.com.br website review
Visit site (opens in a new tab)Reviewed 4 November 202647 issues · 87 checks
This review found 47 issues worth fixing on anita.com.br, 20 of them high impact, across 87 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 193 ms |
| May 23, 2026 | 175 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 144 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 175 ms |
| Jul 18, 2026 | 183 ms |
| Jul 25, 2026 | 178 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 164 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 164 ms |
| Aug 29, 2026 | 166 ms |
| Sep 5, 2026 | 169 ms |
| Sep 12, 2026 | 171 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 183 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 189 ms |
| Oct 17, 2026 | 193 ms |
| Oct 24, 2026 | 193 ms |
| Oct 31, 2026 | 186 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.4 s
0.9 s
1.3 s
1.7 s
2.1 s
2.6 s
3.0 s
3.4 s
Speed
Reduce unused JavaScript
3.9 s · 809 KiBAbout 809 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.
Use efficient cache lifetimes
1.5 s · 456 KiB81 files are served with short cache lifetimes, so returning visitors download them again (456 KiB).
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,083 HTML elements
The page has 3,083 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, Facebook and Google Analytics and others), adding 1.9 MB and 1.0 s of main-thread time.
Render-blocking requests
950 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Google Tag Manager adds 787 ms
787 msGoogle Tag Manager costs a phone 787 ms of main-thread work and 1.1 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
498 KiB10 images could be 498 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
300 ms · 113 KiBAbout 113 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
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 306 ms. During a long task the page ignores taps.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
150 ms · 20 KiB20 KiB could be saved by minifying CSS.
Minify JavaScript
30 KiB30 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: 36 ms
36 msYour server sent the HTML in 36 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.
Largest Contentful Paint: 24.4 s
24.4 sYour largest element takes 24.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Luz da Lua”.
Speed Index: 21.4 s
21.4 sVisually, the page fills in at 21.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 25.4 s
25.4 sThe page becomes fully interactive after 25.4 s. Good is under 3.8 s.
First Contentful Paint: 7.1 s
7.1 sThe first text or image appears after 7.1 s on a phone. Good is under 1.8 s.
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: 206 ms
206 msReal visitors wait 206 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
30 images without width and height
30 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 361 ms
361 msScripts block taps and scrolling for 361 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 193 ms to 186 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 239 requests
4.9 MBYour homepage downloads 4.9 MB in 239 requests on a phone: images 2.6 MB (154), scripts 1.6 MB (29) and fonts 418 KiB (8). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (1.2 MB) are 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.
2 images far larger than shown
41 KiB2 images are downloaded at several times the size a phone draws them, for example e716523e-1070-4c69-a39e-ef0f9d44ee41.jpg at 1,254 px wide, shown at 374 px. Resized copies would save about 41 KiB.
3 images below the first screen load straight away
3 images further down the page (253 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 166.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
4 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (4 elements)
Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.
ARIA attributes must conform to valid values (3 elements)
ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.
Hidden but focusable
35 elements hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (9 elements)
Interactive controls must not be nested: 9 elements on the page fail this check, rated serious by axe-core.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (5 elements)
ARIA input fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
59 form fields without a label
59 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 (11 elements)
Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 172 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 13 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
325 internal links, 10 external
The homepage links to 325 pages on anita.com.br and 10 external pages.
7 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Na Anita Shoes você encontra calçados e acessórios com as melhores marcas. Feminino, masculino e infantil. Tudo com até…”.
One H1 headline
Your main headline reads: “Anita Shoes - Calçados e Acessórios com Estilo e Conforto”.
Title: 57 characters
Your title is a healthy 57 characters: “Anita Shoes - Calçados e Acessórios com Estilo e Conforto”.
Canonical URL set
The canonical URL is https://www.anita.com.br/.
Structured data in place
Structured data found: Organization.
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.anita.com.br/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.anita.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,583 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 128 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
29 small tap targets
29 of 143 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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 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 1,080 words of copy
The homepage carries about 1,080 words of visible text.
4 checks passed
2 short forms
2 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 20 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta 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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
23 other companies contacted
Loading the homepage contacts 23 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 anita.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on anita.com.br, including 23 speed issues and 2 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.