Website review, no card needed

iapcosmeticos.com.br logo

iapcosmeticos.com.br website review

Visit site (opens in a new tab)Reviewed 31 October 202646 issues · 91 checks

This review found 46 issues worth fixing on iapcosmeticos.com.br, 18 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.3 s4.0 sMay 9Oct 244.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.3 s
May 16, 20264.3 s
May 23, 20264.3 s
May 30, 20264.2 s
Jun 6, 20264.1 s
Jun 13, 20264.0 s
Jun 20, 20264.0 s
Jun 27, 20264.1 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20264.1 s
Jul 25, 20264.1 s
Aug 1, 20264.1 s
Aug 8, 20264.2 s
Aug 15, 20264.2 s
Aug 22, 20264.2 s
Aug 29, 20264.2 s
Sep 5, 20264.2 s
Sep 12, 20264.1 s
Sep 19, 20264.1 s
Sep 26, 20264.1 s
Oct 3, 20264.2 s
Oct 10, 20264.2 s
Oct 17, 20264.2 s
Oct 24, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
342 ms263 msMay 9Oct 24314 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026272 ms
May 16, 2026278 ms
May 23, 2026295 ms
May 30, 2026306 ms
Jun 6, 2026319 ms
Jun 13, 2026326 ms
Jun 20, 2026326 ms
Jun 27, 2026333 ms
Jul 4, 2026330 ms
Jul 11, 2026325 ms
Jul 18, 2026317 ms
Jul 25, 2026309 ms
Aug 1, 2026306 ms
Aug 8, 2026305 ms
Aug 15, 2026311 ms
Aug 22, 2026308 ms
Aug 29, 2026308 ms
Sep 5, 2026307 ms
Sep 12, 2026306 ms
Sep 19, 2026313 ms
Sep 26, 2026314 ms
Oct 3, 2026317 ms
Oct 10, 2026315 ms
Oct 17, 2026314 ms
Oct 24, 2026314 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

Full-page screenshot of iapcosmeticos.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. iapcosmeticos.com.br at 1.1 s1.1 s
  2. iapcosmeticos.com.br at 2.3 s2.3 s
  3. iapcosmeticos.com.br at 3.4 s3.4 s
  4. iapcosmeticos.com.br at 4.5 s4.5 s
  5. iapcosmeticos.com.br at 5.6 s5.6 s
  6. iapcosmeticos.com.br at 6.8 s6.8 s
  7. iapcosmeticos.com.br at 7.9 s7.9 s
  8. iapcosmeticos.com.br at 9.0 s9.0 s

Speed

12 to fix33
  • Reduce unused JavaScript

    1.8 s · 678 KiB

    About 678 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Use efficient cache lifetimes

    1.9 s · 459 KiB

    32 files are served with short cache lifetimes, so returning visitors download them again (459 KiB).

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.5 s

    A phone's processor spends 6.5 s on main-thread work while loading, 3.3 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 (vtexassets.com, Google Tag Manager and performa.ai and others), adding 3.1 MB and 2.5 s of main-thread time.

  • Improve image delivery

    950 ms · 239 KiB

    5 images could be 239 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

  • vtexassets.com adds 779 ms

    779 ms

    vtexassets.com costs a phone 779 ms of main-thread work and 1.5 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.

  • Render-blocking requests

    850 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

  • Google Tag Manager adds 664 ms

    664 ms

    Google Tag Manager costs a phone 664 ms of main-thread work and 532 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

    300 ms · 92 KiB

    About 92 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.

  • performa.ai adds 270 ms

    270 ms

    performa.ai costs a phone 270 ms of main-thread work and 597 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.

  • 19 long tasks on the main thread

    19 long tasks block the main thread while loading, the longest for 263 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    150 ms · 131 KiB

    Polyfills for old browsers add 131 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    6 KiB

    6 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: 25 ms

    25 ms

    Your server sent the HTML in 25 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • 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: 14.8 s

    14.8 s

    Your largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 24.5 s

    24.5 s

    The page becomes fully interactive after 24.5 s. Good is under 3.8 s.

  • Speed Index: 11.7 s

    11.7 s

    Visually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 4.4 s

    4.4 s

    The first text or image appears after 4.4 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 1.3 s

    1.3 s

    Scripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.

  • Real-user INP: 306 ms

    306 ms

    Real visitors wait 306 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.4 s

    2.4 s

    Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.0 s

    1.0 s

    Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 9 images without width and height

    9 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 272 ms to 314 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.3 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

    Real visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix83
  • Page weight: 3.4 MB in 209 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 209 requests on a phone: scripts 2.0 MB (78), images 871 KiB (48) and fonts 285 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    https://t41847.vtexassets.com/assets/vtex.file-manager-graph 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).

  • 2 images in older formats

    2 images (398 KiB) 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 below the first screen load straight away

    2 images further down the page (168 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.97 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.8 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

9 to fixGoogle 7586
  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 18 buttons without a name

    18 buttons have no accessible name, so screen readers announce just “button”.

  • Invalid ARIA attributes

    16 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (29 elements)

    All page content should be contained by landmarks: 29 elements on the page fail this check, rated moderate by axe-core.

  • 8 links without text

    8 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 (2 elements).

  • 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 checks passed
  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8593
  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 93 internal links, 11 external

    The homepage links to 93 pages on iapcosmeticos.com.br and 11 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Encontre tudo para sua beleza na IAP Cosméticos! Os melhores produtos para cabelo, maquiagem, unhas e pele. Qualidade g…”.

  • One H1 headline

    Your main headline reads: “IAP! Cosméticos: Onde a Sua Beleza Encontra os Melhores Preços”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “IAP Cosméticos | Ofertas Incríveis em Produtos de Beleza”.

  • Canonical URL set

    The canonical URL is https://www.iapcosmeticos.com.br/.

  • 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.casaparente.com.br/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.iapcosmeticos.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 (493 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages share a title

    https://www.iapcosmeticos.com.br/cabelo, https://www.iapcosmeticos.com.br/cabelo/shampoo and https://www.iapcosmeticos.com.br/cabelo/condicionador all use the title “Produtos para Cabelo: Melhores Marcas - Iap Cosméticos”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://www.iapcosmeticos.com.br/cabelo, https://www.iapcosmeticos.com.br/cabelo/shampoo and https://www.iapcosmeticos.com.br/cabelo/condicionador use the same meta description. A description written for each page earns more clicks.

  • 6 pages slow to respond

    https://www.iapcosmeticos.com.br/cabelo, https://www.iapcosmeticos.com.br/cabelo/tratamento, https://www.iapcosmeticos.com.br/cabelo/transformacao, https://www.iapcosmeticos.com.br/cabelo/escova-e-pente, https://www.iapcosmeticos.com.br/cabelo/acessorios and https://www.iapcosmeticos.com.br/corporal took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 79 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 to fixGoogle 6970
  • 2 broken images

    2 images failed to load on a phone, for example https://www.iapcosmeticos.com.br/.

  • 6 small tap targets

    6 of 29 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 405 words of copy

    The homepage carries about 405 words of visible text.

3 checks passed
  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel, Hotjar and TikTok Pixel.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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.

  • 30 cookies set on arrival

    30

    Opening the homepage sets 30 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.

  • 54 other companies contacted

    Loading the homepage contacts 54 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 iapcosmeticos.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
React
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 46 issues on iapcosmeticos.com.br, including 22 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25