Website review, no card needed
mixcosmeticos.com.br website review
Visit site (opens in a new tab)Reviewed 21 October 202645 issues · 87 checks
This review found 45 issues worth fixing on mixcosmeticos.com.br, 18 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 154 ms |
| May 9, 2026 | 150 ms |
| May 16, 2026 | 153 ms |
| May 23, 2026 | 148 ms |
| May 30, 2026 | 157 ms |
| Jun 6, 2026 | 169 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 166 ms |
| Jun 27, 2026 | 163 ms |
| Jul 4, 2026 | 164 ms |
| Jul 11, 2026 | 164 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 147 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 159 ms |
| Aug 22, 2026 | 176 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 176 ms |
| Sep 12, 2026 | 166 ms |
| Sep 19, 2026 | 164 ms |
| Sep 26, 2026 | 156 ms |
| Oct 3, 2026 | 147 ms |
| Oct 10, 2026 | 174 ms |
| Oct 17, 2026 | 148 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.6 s
1.3 s
1.9 s
2.5 s
3.1 s
3.8 s
4.4 s
5.0 s
Speed
Reduce unused JavaScript
2.3 s · 366 KiBAbout 366 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Render-blocking requests
1.8 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 41
41/100Your mobile performance score is 41 (desktop: 52). 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 (Google Tag Manager, Tray Commerce and Facebook and others), adding 1.6 MB and 894 ms of main-thread time.
Reduce unused CSS
760 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 760 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 186 KiB7 files are served with short cache lifetimes, so returning visitors download them again (186 KiB).
Google Tag Manager adds 434 ms
434 msGoogle Tag Manager costs a phone 434 ms of main-thread work and 596 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.
Tray Commerce adds 346 ms
346 msTray Commerce costs a phone 346 ms of main-thread work and 812 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.
1,573 HTML elements
The page has 1,573 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 6 KiB6 KiB could be saved by minifying JavaScript.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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.
Improve image delivery
4 KiB1 image could be 4 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 874 ms of it running JavaScript. That is comfortably low.
Server response: 62 ms
62 msYour server sent the HTML in 62 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: 12.2 s
12.2 sYour largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Full Banner 3”.
Time to Interactive: 12.9 s
12.9 sThe page becomes fully interactive after 12.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.503
0.503The layout shifts by 0.503 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 853 ms
853 msReal visitors wait 853 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
37 images without width and height
37 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 154 ms to 148 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 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 INP: 141 ms
141 msReal visitors wait 141 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 197 ms
197 msScripts block the page for only 197 ms while loading. Good is under 200 ms.
Images and page weight
About 0.5 g of CO₂ per visit
0.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 58.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.7 MB in 121 requests
1.7 MBYour homepage downloads 1.7 MB in 121 requests on a phone: scripts 1.1 MB (34), images 460 KiB (49) and stylesheets 96 KiB (7). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
6 form fields without a label
6 form fields have 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. (1 element).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 9 failed. 1 more 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 (14 characters)
Your title is only 14 characters: “Mix Cosm�ticos”. Between 30 and 65 characters leaves room to say what you do and for whom.
Canonical points to another host
Your canonical URL points to mixperfumaria.com.br, not mixcosmeticos.com.br, so Google may credit that host instead.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (235 characters)
Your meta description is 235 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
41 internal links, 314 external
The homepage links to 41 pages on mixcosmeticos.com.br and 314 external pages.
3 checks passed
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.mixperfumaria.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.
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 (789 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.mixcosmeticos.com.br/llms.txt (2 KiB, 17 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.mixcosmeticos.com.br/loja/central_anteriores.php has no <title>, so Google invents the link text in results.
2 linked pages hidden from search
https://www.mixcosmeticos.com.br/loja/busca.php and https://www.mixcosmeticos.com.br/central-do-cliente are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
10 pages without a meta description
https://www.mixcosmeticos.com.br/loja/busca.php, https://www.mixcosmeticos.com.br/central-do-cliente, https://www.mixcosmeticos.com.br/loja/central_anteriores.php, https://www.mixcosmeticos.com.br/como-comprar, https://www.mixcosmeticos.com.br/seguranca and https://www.mixcosmeticos.com.br/politica-de-entrega and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.mixcosmeticos.com.br/contato, https://www.mixcosmeticos.com.br/empresa and https://www.mixcosmeticos.com.br/noticias use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://www.mixcosmeticos.com.br/central-do-cliente, https://www.mixcosmeticos.com.br/loja/central_anteriores.php, https://www.mixcosmeticos.com.br/empresa, https://www.mixcosmeticos.com.br/como-comprar, https://www.mixcosmeticos.com.br/seguranca and https://www.mixcosmeticos.com.br/politica-de-entrega and 6 others 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 16 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.
Titles are unique
Every page we checked has its own title.
Best practices
38 small tap targets
38 of 72 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 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 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 283 words of copy
The homepage carries about 283 words of visible text.
3 checks passed
6 short forms
6 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 4 email links.
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.
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.
16 other companies contacted
Loading the homepage contacts 16 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 mixcosmeticos.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
- jQuery
- 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 45 issues on mixcosmeticos.com.br, including 17 speed issues, 6 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.