Website review, no card needed

ikesaki.com.br logo

ikesaki.com.br website review

Visit site (opens in a new tab)Reviewed 3 November 202660 issues · 95 checks

This review found 60 issues worth fixing on ikesaki.com.br, 27 of them high impact, across 95 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.5 s3.7 sMay 16Oct 314.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.4 s
May 23, 20264.3 s
May 30, 20264.3 s
Jun 6, 20264.2 s
Jun 13, 20264.1 s
Jun 20, 20264.0 s
Jun 27, 20263.9 s
Jul 4, 20263.8 s
Jul 11, 20263.8 s
Jul 18, 20263.8 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20264.0 s
Aug 15, 20264.1 s
Aug 22, 20264.1 s
Aug 29, 20264.1 s
Sep 5, 20264.1 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20264.0 s
Oct 10, 20264.0 s
Oct 17, 20264.1 s
Oct 24, 20264.0 s
Oct 31, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
911 ms668 msMay 16Oct 31879 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026741 ms
May 23, 2026723 ms
May 30, 2026714 ms
Jun 6, 2026710 ms
Jun 13, 2026719 ms
Jun 20, 2026717 ms
Jun 27, 2026709 ms
Jul 4, 2026707 ms
Jul 11, 2026696 ms
Jul 18, 2026701 ms
Jul 25, 2026708 ms
Aug 1, 2026718 ms
Aug 8, 2026735 ms
Aug 15, 2026753 ms
Aug 22, 2026773 ms
Aug 29, 2026789 ms
Sep 5, 2026794 ms
Sep 12, 2026778 ms
Sep 19, 2026788 ms
Sep 26, 2026801 ms
Oct 3, 2026818 ms
Oct 10, 2026865 ms
Oct 17, 2026883 ms
Oct 24, 2026878 ms
Oct 31, 2026879 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 ikesaki.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ikesaki.com.br at 1.3 s1.3 s
  2. ikesaki.com.br at 2.6 s2.6 s
  3. ikesaki.com.br at 3.9 s3.9 s
  4. ikesaki.com.br at 5.3 s5.3 s
  5. ikesaki.com.br at 6.6 s6.6 s
  6. ikesaki.com.br at 7.9 s7.9 s
  7. ikesaki.com.br at 9.2 s9.2 s
  8. ikesaki.com.br at 10.5 s10.5 s

Speed

14 to fix2
  • Reduce unused JavaScript

    12.0 s · 2.4 MB

    About 2.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.0 s faster on a phone.

  • Use efficient cache lifetimes

    3.3 s · 674 KiB

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

  • Google Tag Manager adds 1.3 s

    1.3 s

    Google Tag Manager costs a phone 1.3 s of main-thread work and 1.3 MB 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.

  • Reduce unused CSS

    1.1 s · 212 KiB

    About 212 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Render-blocking requests

    1.0 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

  • Mobile performance score: 2

    2/100

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

  • Main-thread work: 9.9 s

    A phone's processor spends 9.9 s on main-thread work while loading, 5.9 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, Google CDN and vtexassets.com and others), adding 7.9 MB and 4.3 s of main-thread time.

  • vtexassets.com adds 842 ms

    842 ms

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

  • Google CDN adds 861 ms

    861 ms

    Google CDN costs a phone 861 ms of main-thread work and 1.4 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.

  • YouTube adds 480 ms

    480 ms

    YouTube costs a phone 480 ms of main-thread work and 979 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.

  • Duplicated JavaScript

    450 ms · 57 KiB

    57 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 450 ms faster on a phone.

  • Facebook adds 409 ms

    409 ms

    Facebook costs a phone 409 ms of main-thread work and 375 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    50 ms · 31 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

14 to fix0
  • 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: 5.6 s

    5.6 s

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

  • Real-user INP: 719 ms

    719 ms

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

  • Real-user CLS: 1.12

    1.12

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

  • First Contentful Paint: 9.3 s

    9.3 s

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

  • Largest Contentful Paint: 37.4 s

    37.4 s

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

  • Speed Index: 17.0 s

    17.0 s

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

  • Time to Interactive: 43.0 s

    43.0 s

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

  • Cumulative Layout Shift: 0.909

    0.909

    The layout shifts by 0.909 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 2.8 s

    2.8 s

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

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

    +20%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 897 ms

    897 ms

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

  • 6 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

Images and page weight

3 to fix53
  • Page weight: 7.4 MB in 246 requests

    7.4 MB

    Your homepage downloads 7.4 MB in 246 requests on a phone: scripts 5.5 MB (102), other files 1.1 MB (85) and HTML 278 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    13907d05-ba5b-48e0-8ce7-ea3f040205b3___ab6a201d7faa733535865 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).

  • 7 images far larger than shown

    273 KiB

    7 images are downloaded at several times the size a phone draws them, for example 20216d79-e017-4858-941e-366f4dae09d8___52815c28273974b29dee7 at 1,210 px wide, shown at 390 px. Resized copies would save about 273 KiB.

  • About 2.1 g of CO₂ per visit

    2.09 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.09 g of CO₂e: 251.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 use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

10 to fixGoogle 8387
  • 2 buttons without a name

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

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

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

    All page content should be contained by landmarks: 4 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.

  • 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 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.

  • 8 links without text

    8 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.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 39 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: 39 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9273
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 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 (also missing: og:description), 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.

  • 110 internal links, 3 external

    The homepage links to 110 pages on ikesaki.com.br and 3 external pages.

4 checks passed
  • Title: 40 characters

    Your title is a healthy 40 characters: “Ikesaki - Perfumaria Online e Cosméticos”.

  • Canonical URL set

    The canonical URL is https://www.ikesaki.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.ikesaki.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.ikesaki.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 (212 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix75
  • 2 linked pages hidden from search

    https://www.ikesaki.com.br/2958 and https://www.ikesaki.com.br/colora%C3%A7%C3%A3o are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share a title

    /, https://www.ikesaki.com.br/nossas-lojas, https://www.ikesaki.com.br/televendas and https://www.ikesaki.com.br/sobre-nos all use the title “Ikesaki - Perfumaria Online e Cosméticos”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://www.ikesaki.com.br/2958, https://www.ikesaki.com.br/nossas-lojas, https://www.ikesaki.com.br/televendas, https://www.ikesaki.com.br/atacado, https://www.ikesaki.com.br/clube-ikesaki and https://www.ikesaki.com.br/sobre-nos and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://www.ikesaki.com.br/nossas-lojas, https://www.ikesaki.com.br/televendas, https://www.ikesaki.com.br/atacado, https://www.ikesaki.com.br/clube-ikesaki, https://www.ikesaki.com.br/cabelos/shampoo and https://www.ikesaki.com.br/cabelos/condicionador and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.ikesaki.com.br/maquiagem/rosto has 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.

  • 3 pages slow to respond

    https://www.ikesaki.com.br/clube-ikesaki, https://www.ikesaki.com.br/colora%C3%A7%C3%A3o and https://www.ikesaki.com.br/cabelos/acessorios took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5423570&tm=gtm002&Ver=2&mid=4081098f-7d2f-4c12-85e2-662849a792fa&bo=1&sid=59bef290d73c11f1a0a5511640d70533&vid=59bf1460d73c11f19b39c9054b0b4120&vids=1&msclkid=N&gtm_ta.

  • 63 small tap targets

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

  • 6 third-party cookies

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

  • 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

5 to fix33
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 196 words

    The homepage has only about 196 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 4 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.

  • 29 cookies set on arrival

    29

    Opening the homepage sets 29 cookies, 1 of them by other companies (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.

  • 49 other companies contacted

    Loading the homepage contacts 49 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 ikesaki.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
Hosting
Locaweb Servicos de Internet S/A

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 60 issues on ikesaki.com.br, including 28 speed issues, 4 SEO issues and 5 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