Website review, no card needed
yinsbrasil.com.br website review
Visit site (opens in a new tab)Reviewed 19 October 202649 issues · 91 checks
This review found 49 issues worth fixing on yinsbrasil.com.br, 27 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
71C- #101,756 of 126,442 reviewed websitesbeats 17%
- #61,709 of 70,471 online storesbeats 10%
- #2,139 of 2,971 WooCommerce storesbeats 23%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.7 s |
| May 2, 2026 | 2.7 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 107 ms |
| May 2, 2026 | 108 ms |
| May 9, 2026 | 107 ms |
| May 16, 2026 | 105 ms |
| May 23, 2026 | 102 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 106 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 105 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 107 ms |
| Sep 26, 2026 | 106 ms |
| Oct 3, 2026 | 106 ms |
| Oct 10, 2026 | 104 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
2.0 s
3.9 s
5.9 s
7.8 s
9.8 s
11.7 s
13.7 s
15.6 s
Speed
Render-blocking requests
4.6 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.6 s.
Reduce unused JavaScript
1.3 s · 932 KiBAbout 932 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 26). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8,233 HTML elements
The page has 8,233 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 820 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Document request latency
750 ms · 680 KiBThe HTML itself could arrive about 750 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Improve image delivery
50 ms · 1.3 MB15 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.
Reduce initial server response time
727 msReduce initial server response time. Google estimates savings of 727 ms on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 846 KiB and 618 ms of main-thread time.
Google Tag Manager adds 364 ms
364 msGoogle Tag Manager costs a phone 364 ms of main-thread work and 444 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
314 KiBAbout 314 KiB of CSS is downloaded but never applied on this page.
Server response: 827 ms
827 msYour server takes 827 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Minify JavaScript
190 ms · 116 KiB116 KiB could be saved by minifying JavaScript.
Legacy JavaScript
100 ms · 104 KiBPolyfills for old browsers add 104 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Use efficient cache lifetimes
202 KiB4 files are served with short cache lifetimes, so returning visitors download them again (202 KiB).
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.
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 LCP: 4.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.1 s
4.1 sReal visitors see the first content after 4.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.3 s
3.3 sReal visitors wait 3.3 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 9.6 s
9.6 sThe first text or image appears after 9.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 24.1 s
24.1 sVisually, the page fills in at 24.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 28.8 s
28.8 sThe page becomes fully interactive after 28.8 s. Good is under 3.8 s.
Total Blocking Time: 456 ms
456 msScripts block taps and scrolling for 456 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 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-10-10, real Chrome visitors' tap response (inp) went from 107 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (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: 5.6 MB in 128 requests
5.6 MBYour homepage downloads 5.6 MB in 128 requests on a phone: scripts 2.0 MB (68), images 1.8 MB (28) and HTML 1,015 KiB (1). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
YP7335_DISPLAY_F.png weighs 656 KiB. On a phone connection a single image that size takes seconds.
6 images far larger than shown
800 KiB6 images are downloaded at several times the size a phone draws them, for example YP7335_DISPLAY_F.png at 1,520 px wide, shown at 350 px. Resized copies would save about 800 KiB.
10 images in older formats
10 images (1.5 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.
1 image below the first screen load straight away
1 image further down the page (235 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 189.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (2 elements)
Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
22 text elements with low contrast
22 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.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (71 elements)
All page content should be contained by landmarks: 71 elements on the page fail this check, rated moderate by axe-core.
38 links without text
38 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (19 characters)
Your title is only 19 characters: “Home - Yin's Brasil”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (369 characters)
Your meta description is 369 characters; Google truncates after about 160, so the end of your pitch is cut.
76 internal links, 303 external
The homepage links to 76 pages on yinsbrasil.com.br and 303 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Yin's Brasil”.
Canonical URL set
The canonical URL is https://yinsbrasil.com.br/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://yinsbrasil.com.br/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://yinsbrasil.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 (25,195 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://yinsbrasil.com.br/produtos, which answers with an error. Visitors hit a dead end and search engines drop it.
4 pages without a meta description
https://yinsbrasil.com.br/onde-comprar, https://yinsbrasil.com.br/produto/todos/carteira-feminina-camila-em-poliuretano-ys39117-2, https://yinsbrasil.com.br/produto/todos/carteira-feminina-clarice-em-poliuretano-ys39116 and https://yinsbrasil.com.br/produto/chris-helena/carteira-feminina-chris-helena/carteira-feminina-gaby-em-poliuretano-ys39110 have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://yinsbrasil.com.br/prime-health has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://yinsbrasil.com.br/onde-comprar, https://yinsbrasil.com.br/catalogos and https://yinsbrasil.com.br/contato 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.
8 pages slow to respond
https://yinsbrasil.com.br/prime-health, https://yinsbrasil.com.br/duvidas-frequentes, https://yinsbrasil.com.br/onde-comprar, https://yinsbrasil.com.br/catalogos, https://yinsbrasil.com.br/blog and https://yinsbrasil.com.br/contato and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
4 checks passed
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 10 pages that loaded have a <title>.
Best practices
300 small tap targets
300 of 347 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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: 19 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
About 25,220 words of copy
The homepage carries about 25,220 words of visible text.
4 checks passed
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 21 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
11 other companies contacted
Loading the homepage contacts 11 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 yinsbrasil.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
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on yinsbrasil.com.br, including 24 speed issues, 2 SEO issues and 3 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.