Website review, no card needed

angeloni.com.br logo

angeloni.com.br website review

Visit site (opens in a new tab)Reviewed 22 October 202658 issues · 100 checks

This review found 58 issues worth fixing on angeloni.com.br, 22 of them high impact, across 100 checks. The most urgent: vtexassets.com adds 2.0 s. 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
5.5 s4.1 sMay 2Oct 174.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.8 s
May 9, 20264.7 s
May 16, 20264.7 s
May 23, 20264.7 s
May 30, 20264.6 s
Jun 6, 20264.6 s
Jun 13, 20264.6 s
Jun 20, 20264.6 s
Jun 27, 20264.6 s
Jul 4, 20264.6 s
Jul 11, 20264.7 s
Jul 18, 20264.7 s
Jul 25, 20264.8 s
Aug 1, 20264.9 s
Aug 8, 20264.8 s
Aug 15, 20264.8 s
Aug 22, 20264.8 s
Aug 29, 20265.1 s
Sep 5, 20265.3 s
Sep 12, 20265.3 s
Sep 19, 20265.2 s
Sep 26, 20264.9 s
Oct 3, 20264.6 s
Oct 10, 20264.4 s
Oct 17, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
502 ms337 msMay 2Oct 17428 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026367 ms
May 9, 2026364 ms
May 16, 2026357 ms
May 23, 2026356 ms
May 30, 2026358 ms
Jun 6, 2026361 ms
Jun 13, 2026371 ms
Jun 20, 2026383 ms
Jun 27, 2026396 ms
Jul 4, 2026418 ms
Jul 11, 2026422 ms
Jul 18, 2026421 ms
Jul 25, 2026423 ms
Aug 1, 2026423 ms
Aug 8, 2026428 ms
Aug 15, 2026437 ms
Aug 22, 2026449 ms
Aug 29, 2026470 ms
Sep 5, 2026479 ms
Sep 12, 2026483 ms
Sep 19, 2026468 ms
Sep 26, 2026454 ms
Oct 3, 2026444 ms
Oct 10, 2026430 ms
Oct 17, 2026428 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 angeloni.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. angeloni.com.br at 2.2 s2.2 s
  2. angeloni.com.br at 4.4 s4.4 s
  3. angeloni.com.br at 6.6 s6.6 s
  4. angeloni.com.br at 8.8 s8.8 s
  5. angeloni.com.br at 11.0 s11.0 s
  6. angeloni.com.br at 13.2 s13.2 s
  7. angeloni.com.br at 15.4 s15.4 s
  8. angeloni.com.br at 17.6 s17.6 s

Speed

19 to fix23
  • vtexassets.com adds 2.0 s

    2.0 s

    vtexassets.com costs a phone 2.0 s of main-thread work and 2.1 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.

  • Render-blocking requests

    1.9 s

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

  • Document request latency

    1.9 s

    The HTML itself could arrive about 1.9 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    1.8 s

    Reduce initial server response time. Google estimates savings of 1.8 s on a phone.

  • Main-thread work: 16.5 s

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

  • Mobile performance score: 23

    23/100

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

  • 5,204 HTML elements

    The page has 5,204 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Server response: 1.9 s

    1.9 s

    Your server takes 1.9 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Google CDN and others), adding 4.5 MB and 4.6 s of main-thread time.

  • Use efficient cache lifetimes

    500 ms · 1.3 MB

    61 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

  • Reduce unused JavaScript

    1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 843 ms

    843 ms

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

    450 ms · 205 KiB

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

  • Google CDN adds 465 ms

    465 ms

    Google CDN costs a phone 465 ms of main-thread work and 735 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 426 ms. During a long task the page ignores taps.

  • datadoghq-browser-agent.com adds 374 ms

    374 ms

    datadoghq-browser-agent.com costs a phone 374 ms of main-thread work and 69 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.

  • Legacy JavaScript

    300 ms · 73 KiB

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

  • goadopt.io adds 311 ms

    311 ms

    goadopt.io costs a phone 311 ms of main-thread work and 260 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.

  • Improve image delivery

    319 KiB

    16 images could be 319 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

Core Web Vitals

11 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 CLS: 0.48

    0.48

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

  • Largest Contentful Paint: 11.5 s

    11.5 s

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

  • Speed Index: 18.1 s

    18.1 s

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

  • Time to Interactive: 44.8 s

    44.8 s

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

  • First Contentful Paint: 7.2 s

    7.2 s

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

  • Total Blocking Time: 3.0 s

    3.0 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user INP: 486 ms

    486 ms

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • 18 images without width and height

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

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

    +17%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

2 checks passed
  • Real-user TTFB: 695 ms

    695 ms

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

  • Cumulative Layout Shift: 0.095

    0.095

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

Images and page weight

3 to fix60
  • Page weight: 6.9 MB in 407 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 407 requests on a phone: scripts 4.0 MB (105), images 1.0 MB (68) and other files 998 KiB (213). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    9a1b4da4-aa4b-4924-9983-27d033a2147c___1f73166d66970f587d2d6 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).

  • 1 image far larger than shown

    65 KiB

    1 image is downloaded at several times the size a phone draws it, for example selo-privacidade-footer.png at 2,600 px wide, shown at 126 px. Resized copies would save about 65 KiB.

  • 3 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (66 KiB) is 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 2.0 g of CO₂ per visit

    1.97 g

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

Accessibility

10 to fixGoogle 7987
  • 75 tap targets too small

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

  • 41 text elements with low contrast

    41 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 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.

  • 6 links without text

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • 1 form field without a label

    1 form field has 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. (7 elements).

2 checks passed
  • Every image has alt text

    All 69 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 10089
  • Structured data has 1 problem

    Structured data found (ItemList and 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 robots.txt

    There is no robots.txt at angeloni.com.br/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

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

  • 1,161 internal links, 10 external

    The homepage links to 1,161 pages on angeloni.com.br and 10 external pages.

5 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Compre no Angeloni as melhores marcas de Eletrodomésticos, TVs, Smartphones e Notebooks em até 10x. Encontre também pro…”.

  • One H1 headline

    Your main headline reads: “Angeloni: Sua loja de Eletrodomésticos, Eletrônicos, Eletroportáteis, e mais”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Angeloni Eletro: As Melhores Marcas em Oferta”.

  • Canonical URL set

    The canonical URL is https://www.angeloni.com.br/eletro/.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.angeloni.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.angeloni.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,098 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix57
  • 10 linked pages are broken

    Your homepage links to https://www.angeloni.com.br/eletro/cama---banho/cama/cobertores/a-baby/acasa, https://www.angeloni.com.br/eletro/cama---banho/cama/colchas/a-baby/acasa, https://www.angeloni.com.br/eletro/cama---banho/cama/edredons-e-duvets/a-baby/acasa, https://www.angeloni.com.br/eletro/cama---banho/cama/fronhas/a-baby/acasa, https://www.angeloni.com.br/eletro/cama---banho/cama/jogos-de-cama/a-baby/acasa and https://www.angeloni.com.br/eletro/cama---banho/cama/lencois-avulsos/a-baby/acasa and 4 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    https://www.angeloni.com.br/eletro and / all use the title “Angeloni Eletro: As Melhores Marcas em Oferta”. 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.angeloni.com.br/eletro/atendimento and https://www.angeloni.com.br/eletro/a-casa use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.angeloni.com.br/eletro. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    /, https://www.angeloni.com.br/eletro/atendimento and https://www.angeloni.com.br/eletro/a-casa have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    /, https://www.angeloni.com.br/eletro/a-casa and https://www.angeloni.com.br/eletro/cama---banho took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.

3 checks passed
  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 3 broken images

    3 images failed to load on a phone, for example https://www.angeloni.com.br/eletro/.

  • 908 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is 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 “Cannot read properties of undefined (reading 'register')”.

  • 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

1 to fix92
  • 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 2,559 words of copy

    The homepage carries about 2,559 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Pet Shop”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Pet Shop”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 10 testimonial or review blocks and 1 trust badge.

  • Analytics in place

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

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 Meta Pixel 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.

  • 39 cookies set on arrival

    39

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

  • 65 other companies contacted

    Loading the homepage contacts 65 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 angeloni.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

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 58 issues on angeloni.com.br, including 30 speed issues, 3 SEO issues and 1 conversion gap. 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