Website review, no card needed

acnezil.com.br logo

acnezil.com.br website review

Visit site (opens in a new tab)Reviewed 31 October 202642 issues · 83 checks

This review found 42 issues worth fixing on acnezil.com.br, 13 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. 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
2.4 s2.0 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.1 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
171 ms143 msMay 9Oct 24167 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026153 ms
May 16, 2026146 ms
May 23, 2026147 ms
May 30, 2026157 ms
Jun 6, 2026157 ms
Jun 13, 2026162 ms
Jun 20, 2026162 ms
Jun 27, 2026152 ms
Jul 4, 2026158 ms
Jul 18, 2026162 ms
Jul 25, 2026162 ms
Aug 1, 2026163 ms
Aug 8, 2026161 ms
Aug 15, 2026161 ms
Aug 22, 2026161 ms
Aug 29, 2026160 ms
Sep 5, 2026161 ms
Sep 12, 2026163 ms
Sep 19, 2026163 ms
Sep 26, 2026167 ms
Oct 3, 2026161 ms
Oct 10, 2026158 ms
Oct 17, 2026168 ms
Oct 24, 2026167 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 acnezil.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. acnezil.com.br at 0.4 s0.4 s
  2. acnezil.com.br at 0.8 s0.8 s
  3. acnezil.com.br at 1.1 s1.1 s
  4. acnezil.com.br at 1.5 s1.5 s
  5. acnezil.com.br at 1.9 s1.9 s
  6. acnezil.com.br at 2.3 s2.3 s
  7. acnezil.com.br at 2.6 s2.6 s
  8. acnezil.com.br at 3.0 s3.0 s

Speed

8 to fix80
  • Mobile performance score: 80

    80/100

    Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Shopify and others), adding 1.3 MB and 834 ms of main-thread time.

  • Improve image delivery

    650 ms · 135 KiB

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

  • Reduce unused JavaScript

    603 KiB

    About 603 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    600 ms

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

  • Google Tag Manager adds 499 ms

    499 ms

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

  • Main-thread work: 2.1 s

    A phone's processor spends 2.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Shopify adds 105 ms

    105 ms

    Shopify costs a phone 105 ms of main-thread work and 313 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.

  • 10 long tasks on the main thread

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

  • Use efficient cache lifetimes

    132 KiB

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

  • Reduce unused CSS

    90 ms · 30 KiB

    About 30 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 90 ms faster on a phone.

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 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.

1 checks passed
  • Server response: 63 ms

    63 ms

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

Core Web Vitals

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

  • Time to Interactive: 14.7 s

    14.7 s

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

  • 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: 1.1 s

    1.1 s

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

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

  • Speed Index: 4.6 s

    4.6 s

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

  • Total Blocking Time: 369 ms

    369 ms

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

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

    +12%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 170 ms

    170 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

1 to fix85
  • Page weight: 2.8 MB in 223 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 223 requests on a phone: scripts 1.5 MB (90), other files 792 KiB (104) and images 382 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (117 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.

  • About 0.8 g of CO₂ per visit

    0.80 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 95.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • 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

10 to fixGoogle 8485
  • 5 buttons without a name

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

  • ARIA commands must have an accessible name (2 elements)

    ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo 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.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 15 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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9268
  • 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.

  • Title is short (7 characters)

    Your title is only 7 characters: “Acnezil”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 21 internal links, 1 external

    The homepage links to 21 pages on acnezil.com.br and 1 external page.

4 checks passed
  • Canonical URL set

    The canonical URL is https://acnezil.com.br/.

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

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.

  • llms.txt published

    The site publishes https://acnezil.com.br/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://acnezil.com.br/.grid-cols-2%20%7B%20%20%20grid-template-columns:%20repeat(3,%20minmax(0,%201fr));%20%20%20display:%20flex;%20%7D%20.lg/:basis-2//4%20%7B%20%20%20flex-basis:%20100%;%20%7D, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 6 pages without a meta description

    https://acnezil.com.br/pages/quem-somos, https://acnezil.com.br/pages/rotina-e-resultado, https://acnezil.com.br/pages/conheca-os-produtos, https://acnezil.com.br/blogs/news, https://acnezil.com.br/pages/quiz and https://acnezil.com.br/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://acnezil.com.br/pages/quem-somos, https://acnezil.com.br/pages/rotina-e-resultado, https://acnezil.com.br/pages/conheca-os-produtos, https://acnezil.com.br/pages/quiz and https://acnezil.com.br/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://acnezil.com.br/pages/rotina-e-resultado, https://acnezil.com.br/pages/quiz and https://acnezil.com.br/collections/all 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 internal pages checked

    We fetched 8 pages linked from your homepage 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 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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 400 ()”.

2 checks passed
  • Tap targets are thumb-sized

    8 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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 21 words

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

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

2 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Amplitude.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 15 cookies set on arrival

    15

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 acnezil.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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager | Amplitude
Hosting
Imperva

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on acnezil.com.br, including 15 speed issues, 5 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